Frequently asked questions about Azure Local VMs enabled by Azure Arc for version 2311.2 and later.
How do I update my infrastructure components for VM management?
Updates for virtual machine (VM) management infrastructure components are handled automatically. These components include MOC, Azure Arc resource bridge, and Kubernetes extensions on Azure Local 2311.2 or later. For more information, see Update overview for Azure Local.
Will I be charged when I update my VM by using the Azure Update Manager service?
No. You can update VMs for free when you use Azure Update Manager. However, updating unmanaged VMs that you created by using Windows Admin Center or Hyper-V Manager, and that were Azure Arc-enabled independently (these are now Arc-enabled servers), does incur a charge. For more information, see the Azure Update Manager pricing for Azure Arc-enabled servers.
Why do I need to move to Azure Local?
Moving to Azure Local is essential to continue using Azure Local VM management, because support for version 22H2 ended on February 15, 2024. Azure Local has several new and enhanced features that provide access to a stable, efficient, and feature-rich platform.
How can I seek assistance during the transition to Azure Local?
The Microsoft support team is available to help you through the transition and can answer any questions you might have. You can get assistance via the Azure portal.
You can also learn more about upgrading at About Azure Local upgrades.
Can Azure Kubernetes Service on Azure Local and Azure Kubernetes Service on Windows Server coexist with Azure Arc resource bridge on the same Azure Local instance?
Yes. Azure Kubernetes Service on Azure Local and Azure Kubernetes Service on Windows Server can be deployed on the same Azure Local instance as VM provisioning from the Azure portal. You can deploy the Azure Kubernetes Service on Azure Stack HCI management system first and then deploy Azure Arc resource bridge. In this configuration, uninstalling Azure Kubernetes Service from Azure Local removes Azure Arc resource bridge.
I used to be able to create virtual networks for my VMs in past releases. Now, I can create only logical networks. What changed?
Starting with the 2311.2 release of Azure Local, logical networks replace virtual networks. Logical networks are the Azure resources that represent your physical network.
To connect virtual machines to your network, you need to create logical networks on which you can place your VM network adapters. You can't use virtual networks created on earlier versions with the Azure Local 2311.2 release and later. You need to manually delete those virtual networks.
Can I use software-defined networking for Azure Local VMs created from the Azure portal?
Software-defined networking (SDN) is currently not supported for VMs created from the Azure portal. For more information on using SDN in Azure Local, see the technical reference for SDN in Azure Local.
How can I perform live migration of Azure Local VMs?
Live migration of Azure Local VMs is supported via on-premises tools like Failover Cluster Manager or Windows Admin Center. Live migration of VM storage is not supported.
Is there a fee to manage Azure Local VMs?
No. You can manage Azure Local VMs by using the Azure CLI or the Azure portal. In either case, no fee is charged. Some VM extensions might have a fee.
When I'm creating an Azure Local VM via the Azure portal and I choose trusted launch as the security type, why is the image dropdown list blank?
Trusted launch for Azure Local VMs currently supports only a select set of Azure Marketplace images. For a list of supported images, see Guest operating system images.
When you create a trusted launch VM in the Azure portal, the image dropdown list shows only the images that trusted launch supports. The image dropdown list appears blank if you select an unsupported image, including a custom image. The list also appears blank if trusted launch doesn't support any of the images available on your Azure Local system.
Can I use the same name for gallery image projections, and do existing VMs use the new image?
Trying to create two images with the same name results in an error. The same situation is true for other resources, like logical networks or virtual hard disks. You must use a unique name.
An updated image doesn't change existing VMs that use it. A copy of the VM image is created at the time of VM creation.
How can I delete a VM image?
You can remove VM images and all other entities by using the Azure CLI or the Azure portal. For more information, see Delete a VM image.
If I delete a gallery image, are all the deployed VMs also deleted?
Deleting a gallery image removes the image name from VM details. It doesn't affect the VMs that you created by using the image.
If I delete Azure Arc resource bridge, are the VMs also deleted?
If you inadvertently remove Azure Arc resource bridge via the Azure portal, it results in the deletion of the Azure projection of the on-premises appliance VM. Importantly, this action doesn't affect your existing workloads.
To restore the Azure projection of the Azure Arc resource bridge, run az arcappliance create. For more information, see az arcappliance create hci.
If the on-premises appliance VM is accidentally deleted, you lose the ability to manage your VMs through the Azure portal. However, your workloads remain accessible through local on-premises tools like Windows Admin Center, Hyper-V, and PowerShell. To reinstate Azure Arc resource bridge, you need to redeploy it. For assistance with this process, contact Microsoft support.