Restore the prior quantity when a capacity-reservation increase fails

Source facts

Microsoft warns that an unsuccessful request for more reserved capacity can rarely leave an existing reservation in Failed state and unavailable until its previous quantity is restored. VMs already associated with that failed reservation continue operating normally. The documented recovery can obtain the successfully reserved amount from currentCapacity in the reservation’s instance view and update the requested quantity accordingly. Microsoft Learn.

Applicability

Use this response for a quantity increase on an existing reservation, not as a general remedy for every VM allocation error. Record the intended increase, previous successful amount, reservation identifier, and returned failure. Separate the reservation’s provisioning state from observations of its associated workloads.

DSE recommendation

Preserve the last successfully reserved quantity and use it as the explicit recovery target for an unsuccessful increase. Ask the capacity owner to approve restoring that amount before retrying a larger request. Keep the requested quantity, observed current capacity, and resulting state in one record. Assign any remaining growth requirement its own follow-up instead of interpreting restoration as delivery of the extra capacity.

Verification

After the approved correction, inspect the reservation’s quantity and state again. Compare the restored value with the preserved successful amount and reconcile the list of associated VMs. Have the workload owner check the relevant service separately, particularly if other changes occurred during the incident. Close the recovery only when the reservation-state discrepancy is resolved, and leave the unmet expansion request visible to its owner.

Official references

Microsoft Learn: Modify a capacity reservation in Azure. Source reviewed September 9, 2026.