Verify capacity-reservation disassociation separately from VM deallocation

Source facts

A deallocated Azure VM remains associated with its capacity reservation group until that reference is changed. Microsoft documents deallocation followed by clearing the association as one removal path. Another path sets reserved quantity to zero before changing the association, for cases where the VM cannot be deallocated and the reservation is no longer required. VM deletion also removes the association, but allocation-state updates can lag completion of the delete request. Microsoft Learn.

Applicability

Use this check when a VM should remain available for future use but should no longer be attached to its current reservation. Do not treat the stopped state alone as evidence that the intended relationship was removed.

DSE recommendation

Confirm both VM state and the reservation reference when closing an approved association-removal change. Have the capacity and workload owners choose the supported path and document whether the reservation itself is still needed. Do not reduce reserved quantity merely to clear one relationship without reviewing the intended reservation use. Keep deletion out of the procedure when the approved outcome is to retain the VM.

Verification

Inspect the VM’s group reference and the reservation’s associated-machine view after the approved operation. If a deletion was separately authorized, wait for its actual completion and inspect Capacity Reservation Instance View instead of inferring allocation state from request submission. Record the retained VM or completed deletion explicitly, together with any remaining association that needs investigation.

Official references

Microsoft Learn: Remove a VM association from a capacity reservation group. Source reviewed September 9, 2026.