VM size series retirements, capacity growth restrictions, and modernization guidance

As Azure continues to invest in higher-performing, more secure, and modern compute infrastructure, it moves away from older-generation hardware. Azure infrastructure expansion focuses on deploying newer-generation hardware that supports the latest virtual machine (VM) offerings.

As a result, certain VM series in the End of Life lifecycle stage have an announced retirement date, and some are also subject to capacity growth restrictions starting in July 2026. Plan to modernize to newer-generation VM families and series to ensure continued access to current platform capabilities, improved performance, enhanced security, and long-term capacity availability.

Retired and retiring VM size series

Retired VM size series run on older hardware that's no longer supported. Series with Retirement Status listed as Announced are still available until the Planned Retirement Date. At the retirement date, any remaining VMs in a retired series are deallocated, stop working, stop incurring charges, and no longer have SLA or support. Plan your modernization to a replacement series well before the retirement date.

End of Life size series aren't retired yet and remain supported until their retirement date. For a list of End of Life sizes, see End of Life Azure VM size series. To learn more about the Current, Extended, End of Life, and Retired lifecycle stages, see the VM lifecycle overview.

General purpose retired sizes

Compute optimized retired sizes

Memory optimized retired sizes

GPU accelerated retired sizes

NVv3-series and NVv4-series have announced retirements planned for September 30, 2026. Review the following entries and modernize to a supported alternative before that date.

Impacted VM series

The following VM series are affected by capacity growth restrictions:

Quota limitations

Existing subscriptions can continue to deploy the preceding VMs within already approved quota, subject to capacity availability. New subscriptions can't deploy the affected VM series.

Recommended modernization paths

If you use impacted VM series, modernize to Current or Extended VM families. Recommended modernization targets generally include v5 VM series in the Current or Extended stage, depending on workload requirements, performance objectives, and storage compatibility considerations. Use Current sizes for new deployments.

Modernization recommendations

Modernization resources

To help identify the most suitable replacement VM, review the following resources:

• VM modernization guidance

These resources provide detailed recommendations for alternative virtual machine series, modernization planning considerations, and workload-specific guidance.

Frequently asked questions

What do "capacity growth restrictions" mean?

Capacity growth restrictions mean that Azure might not approve additional quota requests, new deployments, or capacity expansion requests for impacted VM series due to limited availability of the underlying hardware. These capacity controls don't affect existing running VMs.

When do capacity growth restrictions begin?

Capacity growth restrictions for the impacted VM series begin in July 2026.

Why are these VM series affected?

Azure prioritizes investment in newer-generation infrastructure that delivers improved performance, security, reliability, and platform capabilities. Older VM generations depend on hardware platforms that are no longer a focus for infrastructure expansion.

Can an existing subscription continue deploying affected VM SKUs after July 31, 2026?

Yes. An existing subscription can continue to deploy, redeploy, and operate affected VM SKUs within its already-approved quota, subject to capacity availability.

Can an existing subscription request more quota for an affected VM series?

No. You can't get more quota for affected VM series. Plan new growth on newer-generation VM series.

Can a new subscription deploy an affected VM SKU?

No. New subscriptions are restricted from deploying the affected VM series.

What happens to quota increase requests already submitted?

Requests submitted before enforcement took effect continue through the standard review process. Rollout timing might vary by region or system, so some customers might encounter the restriction before July 31. If you submitted the request, it proceeds through normal evaluation. If there's no option to request quota for an affected VM series, the restriction is active.

Does this restriction mean the D(s)v3 and E(s)v3 VM series are retired?

No. This restriction is about capacity growth, not retirement. Retirement follows a separate process with dedicated customer communications, timelines, and transition guidance.

Separately from these capacity growth restrictions, the Dv3, Dsv3, Ev3, and Esv3 series are in the End of Life stage and retire on November 15, 2029. Until that date, these series remain supported under Azure SLAs, subject to the capacity growth restrictions in this article. For retirement details, see Retired and retiring VM size series.

Can customers continue normal operations on existing VMs and environments as long as they stay within their approved quota?

Existing subscriptions with previously approved quota aren't affected by this change. Customers can continue deploying impacted VM SKUs within their existing approved quota limits, subject to capacity availability. However, approved quota doesn't guarantee capacity availability in the region and deployments might still fail if sufficient capacity isn't available.

Does reimaging one of the impacted VM series in a Virtual Machine Scale Set deallocate it?

No. Reimaging replaces the OS disk so that operating-system and configuration changes can be applied. It doesn't remove the VM or change its VM series. For details, see Reimage a virtual machine in a scale set.

How do I identify the best replacement VM for my workload?

Azure provides VM modernization guidance to help you identify the most appropriate replacement VM family and series based on workload requirements, performance needs, and storage compatibility considerations. Review the VM modernization guidance before selecting a replacement VM.

Are there pricing differences between End of Life and newer VM families?

Pricing, performance, storage capabilities, and hardware characteristics might vary across VM generations. Validate workload requirements and review the documentation for the recommended target VM families and series before you modernize.

Reserved instances

Will existing reserved instances (RIs) continue to work after the quota growth restrictions, including during redeployment, disaster recovery, or failover?

Yes. Existing RIs remain valid through their purchased term and continue providing discounts for matching usage after quota growth restrictions take effect. Capacity growth restrictions don't invalidate existing RIs.

RIs are billing benefits, not capacity reservations. An RI discount might apply to matching usage, but it doesn't guarantee VM creation, redeployment, disaster recovery, failover, or scaling if capacity is unavailable.

Existing subscriptions can deploy or redeploy affected VM sizes within approved quota, subject to capacity availability. New subscriptions, additional quota, and capacity expansion might be restricted.

Review disaster recovery and restore plans, modernize to newer VM generations where appropriate, and update RIs, Savings Plans, and capacity strategies to align with the target environment.

Do RIs provide protection from growth restrictions, and how do they work with on-demand capacity reservations?

Purchasing an RI doesn't reserve capacity or protect against capacity growth restrictions. RIs provide a discount for eligible usage but don't guarantee capacity availability.

Customers who require capacity assurance should evaluate on-demand capacity reservations (ODCRs). Customers who need flexibility across VM families or regions should consider Azure Savings Plan for Compute.

RIs and ODCRs serve different purposes: RIs provide billing discounts, while ODCRs reserve capacity for a specific VM size, region, and zone.

What happens to existing RIs and costs when I modernize from applicable A, B, D, E, F, or L variants of v1 through v3 series to v5 or later?

RIs don't automatically transfer when you modernize to a different VM series. Exchange an eligible RI to match the new VM series or transition to Azure Savings Plan for Compute. If you don't make an update, the RI might no longer apply, which could result in additional costs.

RI exchanges are available until February 1, 2027. After that date, each eligible active reservation purchased before the deadline retains one final exchange.

What commitment discounts remain available, and how should I plan future purchases or renewals?

• For affected applicable A, B, D, E, F, or L variants of v1 through v3 VM series, new or renewed one-year and three-year RIs are no longer available.
• For newer VM generations, RIs remain available for eligible VM series.
• Azure Savings Plan for Compute remains available as a flexible commitment option across eligible VM generations.

Review the reservation portfolio before February 1, 2027, and plan how to use any remaining exchange rights for eligible active RIs. For more information, see Manage Azure Reservations.

What options are available for customers with large usage of applicable A, B, D, E, F, or L variants of v1 through v3 when existing RIs expire? Is there an exception process for RI renewals?

Existing RIs remain valid through their committed term and continue providing discounts for eligible usage. However, no exceptions or extensions are planned for RI purchase or renewal end dates. Work with your Microsoft account team to evaluate modernization and alternative commitment options.

Affected applicable A, B, D, E, F, or L variants of v1 through v3 RIs can't be renewed or repurchased after expiration. Once expired, usage moves to pay-as-you-go rates unless you select another commitment option.

You can:

• Continue running affected VMs at pay-as-you-go rates.
• Transition to Azure Savings Plan for Compute.
• Modernize to newer VM generations and purchase new RIs, an Azure Savings Plan for Compute, or both.

On-demand capacity reservations (ODCR)

Do existing capacity reservations for impacted VM series continue to function after the quota restriction takes effect?

Yes. Existing on-demand capacity reservations (ODCRs) continue to function because they consume existing quota allocations. You can continue using your reservations up to the limits of both your available quota and reserved capacity.

Can I continue deploying VMs against an existing capacity reservation for an impacted VM series?

Yes. You can continue deploying VMs against an existing capacity reservation within the reservation's allocated capacity. You don't need extra quota to deploy VMs that consume capacity already reserved within the same subscription.

Can I create new capacity reservations for impacted VM series after the quota restriction is implemented?

Yes, as long as quota is already available within an existing subscription. However, be aware that scenarios involving shared capacity reservations across subscriptions might be impacted because you can't grant extra quota to consuming subscriptions after the quota freeze takes effect.