The news
Microsoft (MSFT) formalized an Azure VM lifecycle policy in a September 28, 2026 blog post that places its main virtual machine families into four stages, Current, Extended, End of Life and Retired, so customers can see when a VM series needs a migration plan.
The policy covers the General Purpose, Memory Optimized, Compute Optimized and Storage Optimized families, according to the Azure blog post. Current series are recommended for new deployments and sold through pay-as-you-go pricing, Azure Savings Plans and potentially Reserved VM Instances. Extended series stay supported for existing workloads but may be subject to quota restrictions. Microsoft said reserved instances may also be offered for Extended series, and that changes to purchasing options and pricing are possible.
End of Life series run on older platform generations, Microsoft said. Existing deployments stay available within current quota, subject to available capacity, and Microsoft said it will deploy new workload placement capabilities for these VMs. The company acknowledged that some workloads could see small performance differences in rare cases, while saying its existing Azure VM service-level agreements (SLAs) still hold. Reserved instances may no longer be offered, and Microsoft said it expects pricing and availability changes.
Retired series can no longer be provisioned, lose SLA coverage and Microsoft support, and any remaining VMs are deallocated. Microsoft's documentation says deallocated VMs stop working and stop incurring charges.
Microsoft's lifecycle documentation, updated September 25, gives an example for general purpose sizes: v6 and v7 are Current, v4 and v5 are Extended, and v1 through v3 series with an announced retirement are End of Life. It lists the Dv3, Dsv3, Ev3 and Esv3 series as End of Life with a retirement date of November 15, 2029, covering all 32 sizes in those series. After that date customers cannot create, resize into, run or purchase them. The documentation says that retirement does not apply to Azure Government, Azure operated by 21Vianet or sovereign cloud regions.
The blog post points customers to Azure Advisor and Azure Service Health to find affected resources, and describes AI-augmented tools for applying lifecycle guidance across a workload portfolio. The post does not spell out a standard notice period between a retirement announcement and the retirement date.
The numbers
- Lifecycle stages in the new policy
- 4
- Dv3, Dsv3, Ev3 and Esv3 retirement date
- November 15, 2029
- Sizes covered by that retirement
- 32
- Capacity growth restrictions on older series began
- July 2026
- Reserved-instance exchange deadline
- February 1, 2027
Why CEOs should care
For CFOs and FinOps teams, the cost exposure sits in reserved instances. Microsoft's retirement documentation says new or renewed one-year and three-year reserved instances are no longer available for affected A, B, D, E, F and L variants of the v1 through v3 series, and that usage moves to pay-as-you-go rates once existing reservations expire unless another commitment is chosen. Reservations do not transfer automatically to a new VM series. Exchanges are available until February 1, 2027; after that, each eligible active reservation bought before the deadline keeps one final exchange. Finance teams should list every reservation on these series, its expiry date and the pay-as-you-go cost that follows.
For CIOs and infrastructure leads, the capacity rules matter as much as the retirement dates. According to Microsoft's documentation, new subscriptions cannot deploy the restricted older series, existing subscriptions cannot get additional quota for them, and approved quota does not guarantee capacity, so a deployment can still fail. Reserved instances are billing discounts, not capacity guarantees. Teams should check whether disaster recovery or scale-out plans assume redeploying End of Life sizes, and ask whether on-demand capacity reservations, which Microsoft says reserve capacity for a specific size, region and zone, are needed in the meantime.
Procurement leaders and boards should treat migrations as scheduled spending rather than surprise projects. Microsoft suggests Extended v5 sizes as the least disruptive first step and v6 or v7 sizes for the latest features, and its documentation notes that pricing, performance and storage capabilities can vary across generations. Questions for the Microsoft account team: which of our sizes move to End of Life next, and what commitment terms apply after migration?
The bigger picture
The policy formalizes a retirement push that was already under way. In May 2026, The Register reported that Microsoft would stop offering reservations for 17 older VM types and retire 13 of them in 2028, noting that the retiring instances use Intel Xeon processors from the Haswell, Skylake and Cascade Lake generations. The Register's own analysis was that newer chips let Microsoft run more VMs on fewer servers. Microsoft's documentation says Azure is prioritizing investment in newer-generation infrastructure.
What’s next
Key dates on Microsoft's retirement list include September 30, 2026 for the NVv3 and NVv4 GPU series, May 1, 2028 for the D, Ds, Dv2, Dsv2 and Ls series, and November 15, 2028 for series including Av2, F, Fsv2, G and Lsv2. The reserved-instance exchange deadline of February 1, 2027 comes first for most finance teams. Microsoft says the stage of each series in other families is listed on that family's documentation page.
What “Fact-checked” means
Fact-checking means testing a story’s facts against the evidence before it is published. This story went through at least two separate checks before this version was published.
- What we checked
- Its names, figures, dates, job titles, quotes and who said what were checked against the story’s sources, including its main source where it could be opened. The headline was checked for accuracy and overstatement.
- How
- A first check reviewed the whole story. If it passed, a second, skeptical check went back to the sources to look for mistakes in the most important facts. If a check flagged the story, it was edited to fix the problems found, and a separate re-check then reviewed the whole story again.
- Who
- The checks are made by our newsroom, as steps kept separate from the writing, under rules set by our editor, Hussein Mukhtar. A story the checks still flag is held for the editor, who decides whether it is fixed, published or dropped.
- If something is wrong
- “Fact-checked” does not mean error-free. If a material error is found after publication, we correct the story and add a note saying what changed. Report an error
Companies in this story
