Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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 previous-generation VM series are subject to capacity growth restrictions starting in July 2026. Plan migrations to newer-generation VM families and series to ensure continued access to current platform capabilities, improved performance, enhanced security, and long-term capacity availability.
Impacted VM series
The following VM series are affected by these capacity growth restrictions:
| VM category | Impacted VM series |
|---|---|
| Compute optimized | F, Fs, Fsv2 |
| General purpose | D, Ds, Dv2, Dsv2, Dv3, Dsv3, Dv4, Dsv4, Ddv4, Ddsv4, Dav4, Dasv4, B, Bs, Av2, Amv2 |
| Memory optimized | Ev3, Esv3, Ev4, Esv4, Edv4, Edsv4, Eav4, Easv4, G, Gs |
| Storage optimized | Ls, Lsv2 |
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.
| Scenario | Outcome |
|---|---|
| New subscription | Can't deploy affected SKUs. |
| Existing subscription using already-approved quota | Can deploy or redeploy affected SKUs, subject to capacity availability. |
| Existing subscription requesting additional quota | Additional quota isn't approved. |
| Existing subscription with quota, but insufficient regional capacity | Deployment might fail even though quota is available. |
| Existing subscriptions using shared Capacity Reservations | No impact on deployment if existing subscription uses quota from shared pool and within approved limits. |
Recommended migration paths
If you use impacted VM series, migrate to newer-generation VM families. Recommended migration targets generally include v5, v6, and v7 VM series, depending on workload requirements, performance objectives, and storage compatibility considerations.
Migration recommendations
| Current VM category | Impacted VM series | Recommended target VM series |
|---|---|---|
| General purpose | Dv3, Dsv3, Dv4, Dsv4, Ddsv4, Ddav4, Dav4, Dasv4 | Dv5, Dv6, Dv7 (based on workload requirements) |
| Memory optimized | Ev3, Esv3, Ev4, Esv4, Edv4, Edsv4, Easv4, Eav4 | Ev5, Esv6, Esv7 (based on workload requirements) |
Migration resources
To help identify the most suitable replacement VM, review the following resources:
These resources provide detailed recommendations for alternative virtual machine series, migration 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.
Important
Quota is an approved limit; it isn't a capacity reservation or guarantee. A VM deployment might still encounter an allocation failure if capacity is unavailable in the requested region or zone.
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 or D(d)(s)v4 and E(d)(s)v4 VM series are retired?
No. This restriction is about capacity growth, not retirement. Retirement follows a separate process with dedicated customer communications, timelines, and migration guidance. This notice doesn't include a retirement announcement for the D(s)v3 and E(s)v3 or D(d)(s)v4 and E(d)(s)v4 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.
Why aren't D(s)v3 and E(s)v3 or D(d)(s)v4 and E(d)(s)v4 VM series listed in the Retired VM Sizes Migration Guide?
The Retired VM Sizes Migration Guide only includes VM series with a published retirement plan. While some of the VM series affected by the capacity growth restrictions have retirement dates, the D(s)v3 and E(s)v3 or D(d)(s)v4 and E(d)(s)v4 VM series don't currently have a published retirement plan and remain supported until further notice. These VM series continue to be fully supported under Azure SLAs. The recommended VM series for these VMs are D(d)sv5 or newer and E(d)s v5 and newer.
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 migration 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 migration guidance before selecting a replacement VM.
Are there pricing differences between previous-generation and newer-generation 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 migration.
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, migrate 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 migrate from applicable A, B, D, E, F, or L variants of v1 through v4 series to v5 or later?
RIs don't automatically transfer when you migrate 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 v4 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 migration 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.
- Migrate 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.
Important
You might encounter problems when using shared capacity reservations across subscriptions. In this scenario, the consuming subscription might require extra quota to use the shared reservation. Because quota increases are restricted for the affected VM series, this scenario could prevent extra deployments even when reserved capacity is available.
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.