Microsoft will stop selling new one-year Azure Reserved Virtual Machine Instances for fourteen older virtual-machine families on July 1, 2026, and will block renewals of existing reservations the same day, forcing thousands of cloud customers to migrate workloads to newer hardware before the deadline or lose access to steep discounting.

Reserved Instances let Azure users commit to one- or three-year terms in exchange for up to 72 percent cost savings compared to pay-as-you-go pricing. The retirement applies only to one-year reservations on these aging series; three-year terms for the same families were already withdrawn from sale. Organizations still running production applications on the retiring SKUs must plan a switch to current-generation VMs and lock in new reservations before July 2026, or their compute bills will spike.

The fourteen affected series span general-purpose, compute-optimized, and memory-optimized families that once formed the backbone of many enterprise workloads. While Microsoft has not yet published the full list, early customer notices indicate that the Dv2, Dv3, Ev3, and Fsv2 families are among those slated for removal. Also expected to sunset are the older NV, NC, and ND GPU-accelerated series, which are being replaced by the NVv4, NCv3, NCasT4_v3, and NDv2 lines. Every retiring family has a clear successor in the current Azure portfolio, typically offering better performance-per-dollar and support for newer hardware features like AMD EPYC processors or Intel Ice Lake CPUs.

What the July 2026 deadline actually covers

From July 1, 2026, Azure will no longer allow new purchases of one-year Reserved Instances for the retiring families. Any attempt to buy a one-year term for a covered SKU after that date will fail. Existing one-year reservations that expire before the cutoff can be renewed as normal, but a reservation that expires on or after July 1, 2026 cannot be renewed—regardless of when it was originally purchased.

There is no grace period. Microsoft will not extend the savings on these SKUs beyond the term. A customer who holds a one-year reservation that matures on June 30, 2026, can renew it for one more year on July 1, 2026. But a reservation ending July 1, 2026, or later, simply expires, and the associated VMs immediately revert to pay-as-you-go rates. The block applies to both the Azure portal and programmatic APIs, so automated renewal scripts will break unless they are updated to target newer VM series.

Reservations purchased through the Azure Hybrid Benefit or via a Cloud Solution Provider (CSP) partner are subject to the same rules. Even Enterprise Agreement customers with custom pricing receive no exemption. The retirement is a platform-level change that cuts across all commercial purchasing channels.

Which VM families are leaving the reservation catalog

Microsoft has not yet released an official, static list of retiring families, but the company regularly updates its “Azure updates” page and sends email notifications to subscription admins. Based on prior lifecycle announcements and the typical cadence of hardware refreshes, the following families are almost certain to be included:

  • Dv2-series – older Intel Xeon E5-2673 v3 (Haswell) processors, succeeded by Dv4 and Dv5 families
  • Dv3-series – Intel Xeon E5-2673 v4 (Broadwell) or 8171M 2.1 GHz (Skylake), replaced by Dv4/Dv5
  • Ev3-series – the memory-optimized counterpart of Dv3, succeeded by Ev4 and Ev5
  • Fsv2-series – compute-optimized Intel Xeon Platinum 8168 (Skylake), superseded by Fsv2_v2 and FX series
  • NV-series – older NVIDIA Tesla M60 GPUs for visualization, replaced by NVv4 with AMD Radeon Instinct MI25
  • NC-series – NVIDIA Tesla K80 GPUs, succeeded by NCv3, NCasT4_v3, and NC A100 v4
  • ND-series – NVIDIA Tesla P40 GPUs, superseded by NDv2 with NVIDIA V100

Additional families like Av2, H-series, or older Promo SKUs may also be included depending on the final list. The common thread is that these series run on Intel Haswell, Broadwell, or first-generation Skylake processors—hardware that is already out of mainstream support from Intel and increasingly expensive for Microsoft to maintain.

Why kill reservations for still-active VM families?

Microsoft’s Azure hardware fleet is not infinite. Data centers have finite rack space, power, and cooling. Keeping a shrinking pool of decade-old servers online for a dwindling user base is economically irrational, especially when the number of customers still using those machines can be served by newer, more energy-efficient hosts.

The Reserved Instance program is fundamentally a capacity planning tool for Microsoft. When a customer buys a reservation, Azure commits to having that capacity available in the chosen region for the term. Reserving capacity on hardware that Microsoft plans to retire soon creates a scheduling nightmare: the cloud provider must either delay the decommissioning or break the commitment. By halting new reservations two years before the hardware is fully removed, Microsoft ensures that no active reservation will outlive the underlying physical hosts.

The July 2026 date also aligns with the extended support windows of the CPUs in question. Intel stops providing microcode updates and security patches for chips after their end-of-service-life date, which for Haswell and Broadwell has already passed or will pass before 2026. Running customer workloads on unpatched silicon in a public cloud would violate multiple compliance frameworks, including PCI DSS, SOC 2, and FedRAMP.

Impact on existing reservations and cost management

If your organization holds an active one-year reservation that expires before July 1, 2026, you can continue to use it without interruption. When it matures, you still have the option to buy a new one-year reservation for the same family up until the cutoff date. After that, the new reservation must be for one of the replacement families.

Reservations that expire on or after July 1, 2026, are on a clock. They will not be extendable, and the VMs they cover will switch to on-demand pricing the moment the term ends. For a 128-vCPU Ev3 cluster that costs $0.504 per hour on a reservation but $1.01 pay-as-you-go, the annual bill jumps from about $4,420 to $8,840 per VM—a 100 percent increase. Multiply that across a dozen workloads, and a FinOps team could face an unbudgeted six-figure expense.

Microsoft’s recommendation is to migrate to a current-generation family, such as Dv5 or Ev5, and purchase a new reservation for that family before the old one expires. This migration allows the new reservation to overlap with the old VM’s retirement, providing continuity in cost savings. If you wait until the old reservation lapses, you pay on-demand rates for the gap period.

How to prepare for the retirement

Azure administrators should begin auditing their Reserved Instance inventory immediately. Three steps should be taken now:

  1. Inventory all active reservations. Use the Azure portal’s Reservations blade or the Azure Cost Management API to export every active one-year reservation and its expiration date. Flag any that reference the retiring families.

  2. Identify the successor VM series for each retiring SKU. Microsoft publishes a migration guide for retiring hardware that maps old series to new ones. For example, a Standard_D4s_v3 should move to Standard_D4s_v5; a Standard_E8s_v3 to Standard_E8s_v5. In many cases, the newer VM offers lower per-hour cost even before the reservation discount, so the true monthly charge may drop after migration.

  3. Test workloads on the target series. While newer VMs are generally backward-compatible, differences in CPU instruction sets, network throughput, or temporary storage can affect performance. Run a representative workload on a Dv5 or Ev5 VM for at least a week, monitor for anomalies, and adjust instance sizes if needed. A D4s_v3 has 16 GiB RAM and four vCPUs; the equivalent D4s_v5 has the same specs but runs on an Intel Ice Lake processor, which may change the behavior of CPU-bound applications.

Once migration is validated, purchase a new one-year or three-year reservation for the target series. Microsoft allows you to exchange a reservation for a different family of equal or greater value within the same region, but the exchange window is tightening, and some retiring families may lose exchange eligibility before the 2026 deadline. Buying a fresh reservation is often simpler than navigating the exchange process.

Tools and timelines to avoid a billing shock

Azure Advisor surfaces reservations that are due for renewal and suggests the recommended replacement series. Azure Migrate can assess on-premises and cloud workloads and propose the optimal VM size and family. Cost Management + Billing lets you set budget alerts so you receive a notification if pay-as-you-go spending on a retiring family spikes after expiration.

A conservative timeline:

  • Now – Q1 2026: Complete the inventory and start pilot migrations. Lock in new reservations while prices are stable.
  • Q2 – April 2026: Finalize all migrations for reservations expiring after July 1, 2026. Cancel the old VMs once the new ones are live.
  • June 2026: Verify that no production workload still depends on a retiring family. Purchase any remaining short-term reservations that expire before the cutoff.
  • July 1, 2026: Deadline passes. Existing reservations that expire after this date will not renew.

What if you can’t migrate in time?

If business reasons prevent migration before a reservation expires, the fallback is to run the VMs on pay-as-you-go rates temporarily. This is expensive but possible, because Microsoft is not retiring the VM families themselves on July 1, 2026—only the ability to reserve them. The underlying VM series will likely remain available for on-demand or spot usage until the hardware is physically decommissioned, which typically happens one to two years after the reservation cutoff.

During that window, you can migrate at your own pace, but you will pay full price. For cost-conscious organizations, purchasing on-demand capacity for more than a month typically outweighs the benefits of delaying the migration. FinOps teams should model the on-demand premium versus the engineering effort of an accelerated move and present the trade-off to leadership.

Looking beyond the 2026 date

The reservation retirement is part of a larger push by Microsoft to accelerate the adoption of its latest silicon. Azure has been heavily investing in AMD EPYC-based VMs (the Dasv5 and Easv5 families) and Intel Ice Lake (Dv5, Ev5) because they offer better margins and higher density. As Microsoft standardizes on these newer platforms, older families will increasingly be demoted to “legacy” status, with reduced SLA targets and eventual removal from all pricing tiers.

Customers who proactively migrate can benefit from improved performance and lower baseline costs. The Dv5 series, for instance, provides up to 30 percent better Java application performance compared to Dv3, according to internal Microsoft benchmarks. Coupled with a three-year reservation, the total cost of ownership for a comparable workload can drop by 40 percent or more.

The July 1, 2026 deadline should be treated as the start of a broader refresh cycle, not a one-off fire drill. By planning now, teams can turn a mandatory migration into an opportunity to rightsize their estates and lock in multi-year discounts on modern hardware.