Frequently asked questions about Azure Arc VMs for Azure Stack HCI, versions 23H2.
What is changing in Azure Arc Virtual Machine (VM) management on Azure Stack HCI, version 22H2?
On 15 February 2024, the preview of Arc VM management on Azure Stack HCI, version 22H2 will encounter a breaking change. With the upcoming release of Azure Stack HCI version 23H2, we're supporting Arc VM management exclusively on 23H2. The support for Arc VM management preview on Azure Stack HCI on version 22H2 will end on 15 February 2024.
What does this breaking change on Azure Stack HCI, version 22H2 mean for me and my workloads?
The existing Arc VMs created on version 22H2 on your cluster will continue to be accessible through the Azure Command-Line Interface (CLI) until 15 February 2024. However, you can't manage or provision new Arc VMs on Azure portal if you are on version 22H2 from November 2023. To continue the Arc VM preview experience and try out the new features, we strongly recommend that you transition to Azure Stack HCI, version 23H2. Keep in mind that there's no automated migration support for Arc VMs running on Azure Stack HCI, version 22H2.
What major improvements and features can I expect for Arc VMs in the upcoming Azure Stack HCI, version 23H2?
The upcoming Arc VM Management on Azure Stack HCI, version 23H2 has several enhancements and new features. Improvements include a simpler setup for the Arc Resource Bridge, support for static IPs, more flexible storage placement for VMs and VM images, more VM Extensions, improvements to Azure CLI, and more.
How do I upgrade my Azure Arc VM management infrastructure components?
Updates for Arc VM management infrastructure components like MOC, Arc Resource Bridge, and Kubernetes extensions on Azure Stack HCI 23H2 are handled automatically. For more information, see Update overview for Azure Stack HCI, version 23H2.
Why do I need to move to Azure Stack HCI, version 23H2?
Moving to Azure Stack HCI, version 23H2 is essential to continue using Azure Arc VM management since version 22H2 will no longer be supported after 15 February 2024. Version 23H2 has several new and enhanced features that ensure that you have access to a more stable, efficient, and feature-rich platform.
How can I seek assistance during the transition from Azure Stack HCI, version 22H2 to Azure Stack HCI, version 23H2?
The Microsoft Support team is available to help you through the transition and can answer any questions you might have. Feel free to reach out for assistance via the Azure portal.
Can Azure Kubernetes Service on Azure Stack HCI and Windows Server and Azure Arc Resource Bridge coexist on the same Azure Stack HCI cluster?
Yes. Azure Kubernetes Service on Azure Stack HCI and Windows Server and VM provisioning from the Azure portal can be deployed on the same Azure Stack HCI cluster. You can deploy the AKS-HCI management cluster first and then Arc Resource Bridge. In this configuration, uninstalling Azure Kubernetes Service from Azure Stack HCI cluster removes Arc Resource Bridge.
I used to be able to create virtual networks for my Arc VMs in past releases. Starting 2310 (November 2023), I can only create logical networks. What changed?
Starting with the 2310 release of Azure Stack HCI, version 23H2, logical networks have replaced 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 interfaces. Virtual networks created on 22H2 platform cannot be used with 2310 release and beyond, and need to be manually deleted.
Can I use SDN for Azure Stack HCI VMs created from the Azure portal?
SDN is currently not supported for VMs created from the Azure portal.
Is there a fee to use Arc management for VMs on Azure Stack HCI cluster?
VM management for Azure Stack HCI from the Azure control plane doesn't have any extra fees. Some VM extensions might have a fee.
Can I use the same name for gallery image projections and do existing VMs use the new image?
Two images with the same name result in errors at the time of creating them, which is true for other resources as well, like logical networks, virtual hard disks etc. An updated image doesn't change existing VMs that use it. A copy of the VM image is created at the time VM creation.
How can I delete a VM image?
VM images and all other entities can be removed from CLI or from the Azure portal. For more information, see Delete a VM image.
If I delete a gallery image would all the VMs also get deleted which are deployed?
Deleting a gallery image doesn't affect the VMs that were created using that gallery image. The VMs won't be able to show the image name in the VM details.
If I delete Arc Resource Bridge, are the VMs also deleted?
If you inadvertently remove the Arc Resource Bridge via the Azure portal, it results in the deletion of the Azure projection of the on-premises Arc Appliance VM. Importantly, this action doesn't impact your existing workloads. To restore the Azure projection of the Arc Resource Bridge, run az arcappliance create. For more information, see az arcappliance create hci. If the Arc Appliance on-premises VM is accidentally deleted, you lose the ability to manage your VMs through Azure portal, your workloads remain accessible through local on-premises tools like Windows Admin Center, Hyper-V, and PowerShell. To reinstate the Arc Resource Bridge, a redeployment is required. For assistance with this process, contact Microsoft support.