Azure Just Killed Renewals for 18 Legacy VM SKUs — Check Your Reservation Portfolio Now
Microsoft has announced that Azure Reserved Instances for 18 legacy VM SKUs will not be eligible for renewal when their current terms expire. Existing reservations will run to their committed end date and continue to provide their discount benefits until that point, but once the term concludes, those reservations cannot be extended or renewed against the same SKU families. For enterprise architects managing large Azure reservation portfolios — where reservations represent millions of dollars in committed spend — this is a material operational event that requires immediate action.
Which SKUs Are Affected
The 18 affected SKUs span older generations of the D-series, E-series, and F-series VM families — including variants of the Dv2, Dv3, Ev3, and Fsv1 families. These are hardware generations that predate the current Dv5, Ev5, and DCsv3 families built on fifth-generation Intel Ice Lake or AMD Milan architecture baselines. Enterprise architects should run an immediate audit using Azure Cost Management or the Reservations API to identify any active reservations against these SKU families and their expiry dates. The GET /providers/Microsoft.Capacity/reservationOrders API endpoint returns full reservation detail including expiryDate, skuName, and reservedResourceType fields.
Migration Path to Current-Generation SKUs
The recommended migration path is from legacy D-series to Dv5 or Dsv5, from legacy E-series to Ev5 or Esv5, and from Fsv1 to the Fsv2 family. The current-generation SKUs offer materially better price-performance ratios: Dv5 VMs deliver approximately 15 to 20 percent better compute performance per vCore compared to Dv3 at comparable or lower list pricing, primarily due to higher base clock frequencies and improved memory bandwidth of the Ice Lake platform.
The migration process involves several steps: assess workload compatibility, resize or redeploy VMs to the target SKU family in non-production, purchase new reservations against the target SKU, then allow the legacy reservation to run to term while the new workload runs on the new reservation. This avoids the disruption of a hard cutover and ensures no reservation discount is wasted mid-term.
Reservation Portfolio Management Checklist
- Run an immediate inventory of all active reservations and identify any against the 18 affected SKU families
- Sort affected reservations by expiry date and triage those expiring within 90 days as urgent
- Validate workload compatibility with Dv5, Ev5, or Fsv2 target SKUs in non-production before committing new reservations
- Purchase replacement reservations against current-generation SKUs before legacy reservations expire to avoid pay-as-you-go pricing gaps
- Implement a 90-day and 180-day expiry alert policy in Azure Cost Management for all future reservations
- Use this event as a trigger to review the full reservation portfolio for utilisation — underutilised reservations should be exchanged or refunded where eligible before committing to new three-year terms
Key Takeaways
- 18 legacy VM SKU reservations cannot be renewed after their current term — this is a hard cutoff, not a soft deprecation
- The current-generation replacements (Dv5, Ev5, Fsv2) offer better price-performance — migration is a net positive
- Enterprises that miss the expiry window and fall to pay-as-you-go rates on large workloads can incur significant unbudgeted spend
- Proactive portfolio auditing and a systematic renewal management process are the only reliable mitigations
