Connect Azure
Give Rowsafe an app registration with access to one resource group so it can create database servers (VMs) there.
To create servers for you in Azure, Rowsafe needs an app registration with access to one resource group. It takes about five minutes.
Create the resource group and the app
Create a resource group
In the Azure portal, open Resource groups, Create. Name it (for example rowsafe), pick a region and create it. Rowsafe works only inside it.
Register the resource providers
Open Subscriptions, your subscription, Resource providers. Make sure Microsoft.Compute and Microsoft.Network say Registered (else select them and click Register).
Register the app
Open Microsoft Entra ID, App registrations, New registration. Name it Rowsafe and click Register. Copy the Application (client) ID and Directory (tenant) ID.
Create a client secret
In the app, open Certificates & secrets, New client secret, pick an expiry and click Add. Copy the secret's Value (not its ID) now: Azure shows it only once.
Give the app the resource group, and only that
In your resource group, open Access control (IAM), Add, Add role assignment. Choose Contributor (or the custom role below), select the Rowsafe app as the member, then Review + assign.
Paste it into Rowsafe
Copy the Subscription ID from the resource group's Overview. In the dashboard, open Settings → Cloud accounts (or Create a server for me) and click Connect a cloud account. Choose Microsoft Azure, paste the tenant ID, client ID, client secret, subscription ID and resource group name, name the account and click Connect.
Rowsafe checks the credentials first, without creating anything, and says what's missing.
What access this gives Rowsafe
Contributor on one resource group: anything inside it, nothing outside. For less, create a custom role (subscription, Access control (IAM), Add, Add custom role, Start from JSON) and assign it on the resource group instead. Replace the two placeholders:
{
"Actions": [
"Microsoft.Resources/subscriptions/resourceGroups/read",
"Microsoft.Compute/virtualMachines/read",
"Microsoft.Compute/virtualMachines/write",
"Microsoft.Compute/virtualMachines/delete",
"Microsoft.Compute/virtualMachines/start/action",
"Microsoft.Compute/virtualMachines/deallocate/action",
"Microsoft.Compute/virtualMachines/vmSizes/read",
"Microsoft.Compute/disks/read",
"Microsoft.Compute/disks/write",
"Microsoft.Compute/disks/delete",
"Microsoft.Network/virtualNetworks/read",
"Microsoft.Network/virtualNetworks/write",
"Microsoft.Network/virtualNetworks/subnets/read",
"Microsoft.Network/virtualNetworks/subnets/write",
"Microsoft.Network/virtualNetworks/subnets/join/action",
"Microsoft.Network/networkSecurityGroups/read",
"Microsoft.Network/networkSecurityGroups/write",
"Microsoft.Network/networkSecurityGroups/delete",
"Microsoft.Network/networkSecurityGroups/join/action",
"Microsoft.Network/publicIPAddresses/read",
"Microsoft.Network/publicIPAddresses/write",
"Microsoft.Network/publicIPAddresses/delete",
"Microsoft.Network/publicIPAddresses/join/action",
"Microsoft.Network/networkInterfaces/read",
"Microsoft.Network/networkInterfaces/write",
"Microsoft.Network/networkInterfaces/delete",
"Microsoft.Network/networkInterfaces/join/action",
"Microsoft.Authorization/permissions/read"
],
"AssignableScopes": [
"/subscriptions/<subscription-id>/resourceGroups/<resource-group>"
],
"Description": "Lets Rowsafe create, resize and delete database servers in one resource group.",
"Name": "Rowsafe servers",
"NotActions": []
}Rowsafe creates, in that resource group and tagged rowsafe=1:
- for each server: a Debian 12 VM with its disk, a network interface, a static public IP and a network security group letting in only your addresses;
- one virtual network per region, shared by your servers there.
Your SSH keys go on the VM (user rowsafe) only if you give them; Rowsafe never adds its own, and password logins are off. Only when someone clicks and confirms. See what Rowsafe does with your cloud account.
Revoke it
- In Azure: delete the app's secret (Certificates & secrets), remove its role assignment, or delete the app.
- In Rowsafe: Settings → Cloud accounts, Remove (once its servers are deleted). Nothing in Azure changes.
After you revoke it, or the secret expires, your servers keep running and stay protected. Resize, firewall changes and deletes then happen in the Azure portal.
Good to know
- Prices are "about": estimates from Azure's pay-as-you-go list prices in one region. Your Azure bill is what counts.
- Deleting a server removes its VM, disk, network interface, public IP and security group. The region's virtual network stays; delete it in the portal if unused.
- If you hit Azure's CPU or public IP limits, ask for more under Subscriptions, Usage + quotas.
- An Azure Policy can block what Rowsafe creates. Rowsafe says so; ask your Azure admin to allow it for the resource group.