Set up Microsoft Azure¶

Prepare an Azure subscription and authenticate the Azure CLI before deploying Exasol Personal.

Prerequisites¶

You need an Azure subscription with sufficient permissions and quota for virtual machines, networking, managed disks, and storage accounts in the target region. This procedure assumes basic familiarity with Microsoft Entra ID and Azure role-based access control (RBAC). See the Azure documentation for background information.

Configure subscription access¶

In the Azure portal:

Open the target subscription and its Access control (IAM) page.
Give the user who will run the Exasol Launcher one of these roles at subscription scope:
the built-in Contributor role;
a custom role based on the broad example; or
a custom role based on the minimal example.

Use only one option. The built-in Contributor role is usually the simplest. When creating a custom role from an example, replace <subscription-id> in the JSON first.

The role must allow the launcher to create and delete resource groups, networks, virtual machines, managed disks, and storage accounts, and to read storage account keys. Conditional access, multi-factor authentication, or organizational approval flows may require additional steps.

Configure your computer¶

Install the Azure CLI.
Sign in:
```
az login
```
If you can access multiple subscriptions, select the one to use:
```
az account set --subscription "<subscription-id-or-name>"
```
Verify the selection:
```
az account show
```

For a new subscription, register these resource providers if Azure reports registration errors:

az provider register --namespace Microsoft.Compute
az provider register --namespace Microsoft.Network
az provider register --namespace Microsoft.Storage
az provider register --namespace Microsoft.Resources

Azure requires an explicit deployment location:

exasol install azure --location westeurope

For more details, see the Azure CLI guides for authentication and subscription selection.