Check subscription admission before planning growth on restricted older VM series

Source facts

Microsoft’s notice restricts deployment of the listed older VM series in new subscriptions and disallows additional quota for affected series. Existing subscriptions may deploy within previously approved quota, but only when capacity is available. The controls do not interrupt already-running VMs and are not themselves a retirement announcement. Shared capacity reservations can still encounter a consuming-subscription quota requirement that cannot be increased under the restriction. Microsoft Learn.

Applicability

Review growth, redeployment, and recovery targets that depend on a series named in the notice. Match the exact family and variant rather than assuming all older or all current-generation sizes share the same restriction. Keep an existing running estate separate from permission and capacity for its next deployment.

DSE recommendation

Classify each planned deployment by target subscription and approved quota before assuming an older VM size remains an admissible target. Review any shared-reservation consumer independently of the reservation owner. Where the plan depends on new admission or extra quota, identify a compatible newer-generation alternative and assign its qualification to the workload owner.

Verification

Inspect the target subscription’s actual quota and deployment eligibility, then perform an approved representative deployment test where appropriate. Record the exact size, region or zone, and allocation result. Do not treat unused quota as reserved hardware, or a working source VM as proof that a recovery destination can recreate it. Keep a rejected admission path explicit in the recovery plan until an alternative is validated.

Official references

Microsoft Learn: Previous-generation capacity-growth restrictions. Source reviewed September 9, 2026.