Azure Stack
An Azure Stack resource handler connects Cloud Management Platform (CMP) to an Azure Stack endpoint
2 minute read
Azure Stack is a legacy technology and does not appear in the technology picker. You cannot create a new Azure Stack resource handler. Existing handlers continue to work, and you can still edit their credentials and settings.
Credentials for an existing handler
To review or update the connection, open the handler from Admin > Resource Handlers and select Edit Credentials.
| Field | Description |
|---|---|
| Subscription ID | The ID of the subscription this handler manages. |
| Application ID | The ID of the Active Directory application the handler authenticates as. Azure calls this the Client ID. |
| Authentication Key | The private key 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. |
| Directory ID | The directory the application belongs to. Azure calls this the Tenant ID. |
| Auth Type | How the handler authenticates: Service Principal or Active Directory. Service Principal is the default. |
| Metadata Endpoint | The Azure Stack endpoint the handler connects to. This field is what distinguishes an Azure Stack handler from an Azure one. |
Related
- Azure: the current handler for new connections to Azure subscriptions.
- Azure Local: run Azure services on hardware in your own data center.
- Use password vaults: storing the authentication key in HashiCorp Vault, CyberArk, Keeper, AWS Secrets Manager, or Azure Key Vault.
- Legacy technologies: QEMU-KVM and XenServer, which are also closed to new handlers.