Event details

This is your chance to be heard. Join us for an open feedback session focused on the current state of Windows Server 2025 and the roadmap for the next version of Windows Server (vNext). We’ll share a...
Pearl-Angeles
Updated May 08, 2026
paulw2's avatar
paulw2
Copper Contributor
May 13, 2026

The reason for the question is that is there a Server Licensing issue with moving from Azure local Cluster to other clusters in the environment.

Artem Pronichkin's avatar
Artem Pronichkin
Icon for Microsoft rankMicrosoft
May 13, 2026

This limitation with Azure Local only affects Live Migration. So, one option to address this is to move the VMs offline. E.g., just copy files over and import them. Given that a migration from VMware still incurs some downtime, a little more downtime could be tolerable.

With that said, the team is actively working on some other VMware migration options, which could move VMs directly to Windows Server clusters. So, no need to use Azure Local in between, if your end goal is to run on Windows Server.

  • DanCuomo's avatar
    DanCuomo
    Icon for Microsoft rankMicrosoft
    May 13, 2026

    Hi paulw2​ - Just to add a little more to Artem's response. In Windows Admin Center: Administration Mode, we currently have a conversion tool which can convert VMware VMs to Hyper-V VMs. This is in preview and will be moved to Windows Admin Center: Virtualization Mode in the fullness of time. Hope this helps.

    Of course, if Azure Local is your final destination, Azure Migrate can assist with your VMware to Hyper-V conversions.