What is Azure Arc VM management? (preview)
Applies to: Azure Stack HCI, versions 22H2 and 21H2
Azure Arc VM management enables you to use the Azure portal to provision and manage Windows and Linux VMs hosted in an on-premises Azure Stack HCI environment. Azure Arc enables IT administrators to delegate permissions and roles to app owners and DevOps teams to enable self-service VM management for their Azure Stack HCI clusters by using Azure management tools, including Azure portal, Azure CLI, Azure PowerShell, and ARM templates. Using Azure Resource Manager templates, you can automate VM provisioning in a secure cloud environment.
To find answers to frequently asked questions about Arc VMs on Azure Stack HCI, see FAQs.
To troubleshoot issues with your Arc VMs or to know existing known issues and limitations, see Troubleshoot Arc virtual machines.
Benefits of Azure Arc VM management
With Azure Arc VM management, you can perform various operations from the Azure portal including:
- Create a VM
- Start, stop, and restart a VM
- Control access and add Azure tags
- Add and remove virtual disks and network interfaces
- Update memory and virtual CPUs for the VM
By using the Azure portal, you get the same consistent experience when provisioning and managing on-premises VMs or cloud VMs. You can access your VMs only, not the host fabric, enabling role-based access control and self-service.
What is Azure Arc Resource Bridge?
A resource bridge is required to enable VM provisioning through the Azure portal on Azure Stack HCI. Azure Arc Resource Bridge is a Kubernetes-backed, lightweight VM that enables users to perform full lifecycle management of resources on Azure Stack HCI from the Azure control plane, including the Azure portal, Azure CLI, and Azure PowerShell. Azure Arc Resource Bridge also creates Azure Resource Manager entities for VM disks, VM images, VM interfaces, VM networks, custom locations, and VM cluster extensions.
To use Arc Resource Bridge side-by-side with Azure Kubernetes Service (for example, to run your container workloads) on the same cluster, there are some limitations that you should be aware of, such as a required deployment order. For a complete list of limitations and known issues, see Limitations and known issues.
A custom location for an Azure Stack HCI cluster is analogous to an Azure region. As an extension of the Azure location construct, custom locations allow tenant administrators to use their Azure Stack HCI clusters as target location for deploying Azure services.
A cluster extension is the on-premises equivalent of an Azure Resource Manager resource provider. The Azure Stack HCI cluster extension helps manage VMs on an Azure Stack HCI cluster in the same way that the "Microsoft.Compute" resource provider manages VMs in Azure, for example.
Arc Appliance is an earlier name for Arc Resource Bridge, and you may see the term used in some places like the PowerShell commands or on the Azure portal. The feature has also been called self-service VMs in the past; however, this is only one of the several capabilities available with Arc-enabled Azure Stack HCI.
Azure Arc VM management deployment workflow
To enable Azure Arc-based VM operations on your Azure Stack HCI cluster, you must:
- Install Azure Arc Resource Bridge on the Azure Stack HCI cluster and create a VM cluster extension. This can be done using Windows Admin Center or PowerShell.
- Create a custom location for the Azure Stack HCI cluster.
- Create virtual network projections which will be used by VM network interfaces.
- Create OS gallery images for provisioning VMs.
- Only one Arc Resource Bridge can be deployed on a cluster.
- Each Azure Stack HCI cluster can have only one custom location.
- Each virtual switch on the Azure Stack HCI cluster can have one virtual network.
- Multiple OS images can be added to the gallery.
- Additional virtual networks and images can be added any time after the initial setup.
Submit and view feedback for