Choose the correct allocation path when associating an existing VM with reserved capacity

Source facts

An Azure VM references its capacity reservation group through a VM property. Microsoft requires an existing regional VM to be deallocated, associated, and restarted. The documented alternative for associating an existing zonal VM without deallocation is preview. After association and allocation, the reservation’s instance view identifies the VM through virtualMachinesAllocated. Microsoft Learn.

Applicability

Use this check for an existing VM and a specifically identified reservation group in the same subscription. Record the VM’s regional or zonal placement and the intended matching reservation. Do not apply the preview procedure merely because the VM happens to reside in a region that offers zones.

DSE recommendation

Classify the existing VM as regional or zonal before approving its reservation-association procedure. For the regional path, include the interruption and restart in the workload owner’s change plan. If evaluating the zonal preview, obtain an explicit preview-use decision and retain the source conditions with the trial. Separate the request to change the association property from the evidence showing where capacity was actually allocated.

Verification

Inspect the VM’s resulting group reference and the reservation’s instance view. Match the allocated VM identifier to the intended resource rather than relying on a similar display name. For a regional move, also verify the guest and application after restart. If the association exists but the expected allocation evidence is absent, leave the change open and investigate the mismatch before extending the procedure to additional machines.

Official references

Microsoft Learn: Associate a virtual machine to a capacity reservation group. Source reviewed September 9, 2026.