Provisioning
Every Azure environment carries a set of Azure-specific parameters that control how Cloud Management Platform (CMP) provisions a server
3 minute read
First, register an application in your Azure portal and grant it access to the subscription. Then create the handler in CMP using that application’s credentials. To manage more than one subscription, see Azure resource handler for multiple cloud subscriptions.
Prepare your Azure portal for CMP integration.
Create an Azure resource handler to connect CMP to your Azure subscription. The wizard presents two dialogs: the first collects the credentials, and the second names the handler and imports its regions.
Go to Admin > Resource Handlers.
Select Add.
Select Azure.
Complete the credentials fields, then select Continue.
| Field | Value |
|---|---|
| Cloud Environment | The Azure cloud this subscription belongs to: Public (Default), Germany, China, or US Gov. Each sovereign cloud has its own regions and endpoints. You can change this later on an existing handler’s credentials form. |
| Subscription ID | The ID of the subscription this handler manages. |
| Application ID | The ID of the Microsoft Entra ID application you registered. Azure calls this the Client ID. |
| Authentication Key | The secret created for that application. Azure displays the value only once, when it is generated. If the password vault feature is enabled, this field offers Locally Stored or Vault Managed. Select Vault Managed to read the key from a configured vault provider. See Use password vaults. |
| Directory ID | The directory the application belongs to. Azure calls this the Tenant ID. |
Complete the settings fields, then select Done. The following fields are specific to Azure:
{{ server.hostname }}-00X. Leave it empty to use the default naming.Contributor on the subscription covers everything CMP does. To grant less than Contributor, either for a read-only setup or as a least-privilege custom role, see Required Azure permissions.
CMP applies a server’s tags to each Azure resource it creates during server provisioning and synchronizes tags across the servers it manages. Depending on the order, the resources tagged at provision time can include the virtual machine, its network interface, the OS disk, any additional disks, an availability set, a resource group, a storage account, and a public IP address.
Tags reach a resource group only when CMP creates it. Selecting an existing resource group on the order form leaves that group’s tags untouched.
The handler’s Tags tab lists the server attributes available to use as tag values. For how tagging works across CMP, see Tags.
Every Azure environment carries a set of Azure-specific parameters that control how Cloud Management Platform (CMP) provisions a server
An Azure load balancer distributes incoming traffic across the servers in a blueprint’s server tier
Resizing changes an Azure server’s VM size in place, from the server’s own page or through the API
Every disk on an Azure server includes a host caching mode and a storage type or a storage account
An Azure server is provisioned from an image that has been imported into its region
Azure VM Guest Patching mode helps with update management by automatically and safely patching virtual machines to maintain security compliance
An Azure resource handler acts as the Microsoft Entra ID application you registered, so that application needs a role on the subscription
A single Microsoft Entra ID application can create an Azure resource handler for every subscription it can access