Connect Azure Stack HCI to Azure

Applies to: Azure Stack HCI, version 20H2

Azure Stack HCI is delivered as an Azure service and needs to register within 30 days of installation per the Azure Online Services Terms. This topic explains how to register your Azure Stack HCI cluster with Azure Arc for monitoring, support, billing, and hybrid services. Upon registration, an Azure Resource Manager resource is created to represent each on-premises Azure Stack HCI cluster, effectively extending the Azure management plane to Azure Stack HCI. Information is periodically synced between the Azure resource and the on-premises cluster(s). Azure Arc registration is a native capability of the Azure Stack HCI operating system, so there is no agent needed to register.


Registering with Azure is required, and your cluster is not fully supported until your registration is active. If you do not register your cluster with Azure upon deployment, or if your cluster is registered but has not connected to Azure for more than 30 days, the system will not allow new virtual machines (VMs) to be created or added. When this occurs, you will see the following error message when attempting to create VMs:

There was a failure configuring the virtual machine role for 'vmname'. Job failed. Error opening "vmname" clustered roles. The service being accessed is licensed for a particular number of connections. No more connections can be made to the service at this time because there are already as many connections as the service can accept.

The solution is to allow outbound connectivity to Azure and make sure your cluster is registered as described in this topic.

Prerequisites for registration

You won't be able to register with Azure until you've created an Azure Stack HCI cluster. In order for the cluster to be supported, the cluster nodes must be physical servers. Virtual machines can be used for testing, but they must support Unified Extensible Firmware Interface (UEFI), meaning you can't use Hyper-V Generation 1 virtual machines.

For the simplest registration experience, have an Azure AD administrator complete the registration using either Windows Admin Center or PowerShell.


In order to register an Azure Stack HCI cluster using Windows Admin Center, you must first register Windows Admin Center with Azure and supply your Azure Active Directory (tenant) ID. Make sure that the computer on which you run Windows Admin Center is joined to the same Azure Active Directory domain in which you'll create the cluster, or a trusted domain.

Internet access

Azure Stack HCI needs to periodically connect to the Azure public cloud. If outbound connectivity is restricted by your external corporate firewall or proxy server, they must be configured to allow outbound access to port 443 (HTTPS) on a limited number of well-known Azure IPs. For information on how to prepare your firewalls and set up a proxy server, see Configure firewalls for Azure Stack HCI.


The registration process tries to contact the PowerShell Gallery to verify that you have the latest version of the necessary PowerShell modules such as Az and AzureAD. Although the PowerShell Gallery is hosted on Azure, it does not currently have a service tag. If you cannot run the above cmdlet from a management machine that has outbound internet access, we recommend downloading the modules and manually transferring them to a cluster node where you will run the Register-AzStackHCI command. Alternatively, you can install the modules in a disconnected scenario.

Azure subscription and permissions

If you don’t already have an Azure account, create one.

You can use an existing subscription of any type:

  • Free account with Azure credits for students or Visual Studio subscribers
  • Pay-as-you-go subscription with credit card
  • Subscription obtained through an Enterprise Agreement (EA)
  • Subscription obtained through the Cloud Solution Provider (CSP) program

The user registering the cluster must have Azure subscription permissions to:

  • Register a resource provider
  • Create/Get/Delete Azure resources and resource groups

If your Azure subscription is through an EA or CSP, the easiest way is to ask your Azure subscription admin to assign a built-in "Owner" or "Contributor" Azure role to your subscription. However, some admins may prefer a more restrictive option. In this case, it's possible to create a custom Azure role specific for Azure Stack HCI registration by following these steps:

  1. Create a json file called customHCIRole.json with following content. Make sure to change to your Azure subscription ID. To get your subscription ID, visit, navigate to Subscriptions, and copy/paste your ID from the list.

      "Name": "Azure Stack HCI registration role”,
      "Id": null,
      "IsCustom": true,
      "Description": "Custom Azure role to allow subscription-level access to register Azure Stack HCI",
      "Actions": [
      "NotActions": [
    "AssignableScopes": [
  2. Create the custom role:

    New-AzRoleDefinition -InputFile <path to customHCIRole.json>
  3. Assign the custom role to the user:

    $user = get-AzAdUser -DisplayName <userdisplayname>
    $role = Get-AzRoleDefinition -Name "Azure Stack HCI registration role"
    New-AzRoleAssignment -ObjectId $user.Id -RoleDefinitionId $role.Id -Scope /subscriptions/<subscriptionid>

Azure Active Directory permissions

You'll also need appropriate Azure Active Directory permissions to complete the registration process. If you don't already have them, ask your Azure AD administrator to grant consent or delegate the permissions to you. See Manage Azure registration for more information.

Register a cluster using Windows Admin Center

The easiest way to register your Azure Stack HCI cluster is using Windows Admin Center. Remember that the user must have Azure Active Directory permissions, or the registration process will not complete; instead, it will exit and leave the registration pending admin approval, and the user will have to re-run the registration wizard once permissions are granted.

  1. Before beginning the registration process, you must first register Windows Admin Center with Azure and sign into Windows Admin Center with your Azure account.


    When registering Windows Admin Center with Azure, it's important to use the same Azure Active Directory (tenant) ID that you plan to use for the cluster registration. An Azure AD tenant ID represents a specific instance of Azure AD containing accounts and groups, whereas an Azure subscription ID represents an agreement to use Azure resources for which charges accrue. To find your tenant ID, visit and select Azure Active Directory. Your tenant ID will be displayed under Tenant information. To get your Azure subscription ID, navigate to Subscriptions and copy/paste your ID from the list.

  2. Open Windows Admin Center and select Settings from the very bottom of the Tools menu at the left. Then select Azure Stack HCI registration from the bottom of the Settings menu. If your cluster has not yet been registered with Azure, then Registration status will say Not registered. Click the Register button to proceed. You can also select Register this cluster from the Windows Admin Center dashboard.


    If you did not register Windows Admin Center in step 1, you'll be asked to do so now. Instead of the cluster registration wizard, you'll see the Windows Admin Center registration wizard.

  3. Specify the Azure subscription ID that you want to register the cluster to. To get your Azure subscription ID, visit, navigate to Subscriptions and copy/paste your ID from the list. If your Azure AD admin gave you an Azure resource group to use, select it from the drop-down menu; otherwise, select Create new. Select the Azure region from the drop-down menu and click Register.

    The cluster registration wizard will ask for your Azure subscription ID, resource group, and region

  4. If you have sufficient Azure Active Directory permissions, the cluster registration workflow should now proceed to completion, and you should be able to see your cluster in the Azure portal. If you receive a message that you need additional Azure Active Directory permissions, proceed to step 5.

  5. If you don't have sufficient Azure Active Directory permissions, you'll need to ask your Azure AD admin to grant permissions to the app. You should see a link to the Azure portal that goes to the cluster's specific app ID, as in the screenshot below. Copy this link and give it to your Azure AD admin. To check whether consent has been granted, select View consent in Azure AD. After consent has been granted, re-run the wizard beginning with step 2 above.

    If you need additional Azure Active Directory permissions to register the cluster, you'll be given a link to provide to your Azure AD admin

Register a cluster using PowerShell

Use the following procedure to register an Azure Stack HCI cluster with Azure using a management PC.

  1. Install the required cmdlets on your management PC. If you are registering a cluster deployed from the current General Availability (GA) image of Azure Stack HCI, simply run the following command. If your cluster was deployed from the Public Preview image, make sure you have applied the November 23, 2020 Preview Update (KB4586852) to each server in the cluster before attempting to register with Azure.

    Install-Module -Name Az.StackHCI


    • You may see a prompt such as Do you want PowerShellGet to install and import the NuGet provider now? to which you should answer Yes (Y).
    • You may further be prompted Are you sure you want to install the modules from 'PSGallery'? to which you should answer Yes (Y).
  2. Perform the registration using the name of any server in the cluster. To get your Azure subscription ID, visit, navigate to Subscriptions and copy/paste your ID from the list.

    Register-AzStackHCI  -SubscriptionId "<subscription_ID>" -ComputerName Server1

    This syntax registers the cluster (of which Server1 is a member), as the current user, with the default Azure region and cloud environment, and using smart default names for the Azure resource and resource group. You can also add the optional -Region, -ResourceName, and -ResourceGroupName parameters to this command to specify these values.

    Remember that the user running the Register-AzStackHCI cmdlet must have Azure Active Directory permissions, or the registration process will not complete; instead, it will exit and leave the registration pending admin approval. Once permissions have been granted, simply re-run Register-AzStackHCI to complete registration.

  3. Authenticate with Azure

    To complete the registration process, you need to authenticate (sign in) using your Azure account. Your account needs to have access to the Azure subscription that was specified in step 2 above in order for registration to proceed. Copy the code provided, navigate to on another device (like your PC or phone), enter the code, and sign in there. The registration workflow will detect when you've logged in and proceed to completion. You should then be able to see your cluster in the Azure portal.

Next steps

You are now ready to: