Azure previews in-place regional-to-zonal VM migration

Azure introduced a public preview for moving regional, nonzonal VMs and VM Scale Sets in Flexible orchestration into a selected availability zone. The Compute team says the process preserves the VM resource ID and name, OS and data disks, NICs, IP addresses, and scale-set membership rather than rebuilding the resource.

Placement can change without replacement

The migration closes an awkward gap for estates created before teams adopted zonal architecture. Operators deallocate a machine, assign zone 1, 2, or 3 through the preview workflow, and restart it. Microsoft describes the move as one-way and performed per VM. Configurations including Basic SKU public IPs and unmanaged disks are not supported.

A zonal label improves placement clarity but does not make a single VM resilient to a zone outage. Service resilience still requires appropriately distributed instances, load balancing, state replication, and capacity in more than one zone.

Plan for downtime and capacity

Run eligibility checks and confirm the target size is offered in the desired zone. Record dependencies tied to source IP, disks, proximity, or host placement. Because deallocation stops the VM, coordinate an application maintenance window and drain traffic first.

Move a noncritical instance, validate its preserved identifiers and network behavior, then test the service before proceeding in batches. For a scale set, protect capacity while instances move one at a time and ensure autoscaling cannot undo the planned sequence.

Document that reversal is unavailable in the preview. The rollback plan should restore service through another instance or deployment, not assume the moved VM can return to regional placement.