Azure VM Lifecycle Explained: Current, End of Life, Retirement and Capacity Risks

The useful distinction is this: End of Life does not mean a VM shuts down immediately. Retired does. Between those points, support can continue even as access to new capacity, quota and purchasing options narrows.

What the four stages mean​

• Current: Microsoft recommends these series for new deployments and expansion. They receive standard maintenance and support, with broad regional availability. Pay-as-you-go and Azure Savings Plans are available; Reserved VM Instances may also be offered.
• Extended: Existing workloads remain supported, but customers should start evaluating Current-series replacements. Quota restrictions are possible, and purchasing options or prices may change.
• End of Life: Retirement has been formally announced. Standard maintenance and support continue until retirement, and Microsoft says it will provide notifications, migration guidance and tooling. Existing customers may use these VMs in supported regions within existing quota, subject to capacity. New deployments and quota requests can be restricted; Reserved Instances may cease to be offered.
• Retired: The series can no longer be provisioned or purchased. Microsoft says remaining VMs will be deallocated, and the series will no longer have an SLA or Microsoft support.

Those labels are general policy, not a guarantee that every series has identical terms. Microsoft expressly allows for product-specific, regional and operational exceptions. It has not set a universal retirement-notice period or supplied a replacement size for every workload in the announcement.

Why quota is only half the capacity story​

A concrete example comes from Microsoft Learn’s guidance for Dv3, Dsv3, Ev3 and Esv3. These series are in End of Life and are scheduled to retire on November 15, 2029. Until then, they remain supported, but capacity-growth restrictions are separate from the retirement date. Microsoft says an existing subscription can deploy affected sizes within its approved quota only if capacity is available; quota itself is not a reservation of a physical host. New subscriptions and additional quota face restrictions for the affected series.

Purchasing can change earlier, too. Microsoft’s modernization guide says new purchases and renewals of one- and three-year Reserved VM Instances for those four series ended after July 1, 2026, while existing reservations continue for their purchased terms. That is a series-specific example, not a rule that every End-of-Life VM loses reservations on the same schedule.

For an administrator planning disaster recovery or scale-out, this makes a practical difference. A workload might run normally today yet encounter an allocation failure when it needs another VM. Microsoft also notes that a Reserved Instance provides a billing benefit, not guaranteed capacity.

A sensible next pass through your VM estate​

• Inventory the VM series behind production, test and recovery workloads. Check each series’ lifecycle status and its own retirement notice rather than planning from the four labels alone.
• Check the target region, quota and available replacement sizes. Include planned growth and failover, not just currently running VMs.
• Validate the replacement against the workload. For the Dv3/Dsv3 and Ev3/Esv3 transitions, Microsoft identifies v5 options and newer v6 or v7 paths. Its guidance flags differences such as boot generation, storage interfaces and networking support that can make a simple size swap an unsafe assumption.
• Review commitments and schedule a tested migration before retirement. Check whether an existing reservation will still match the target series, then test application behavior and recovery before changing production capacity. Microsoft says Azure Advisor and Azure Service Health can help surface upcoming retirements and affected resources.

Microsoft also says it plans new workload-placement capabilities for End-of-Life VMs. It warns of possible minor performance variations in rare cases while saying existing Azure VM SLAs will still be met; the announcement does not explain the mechanism or name the affected series. Likewise, its proposed AI-augmented modernization tools have no specified release date. For now, the most dependable planning inputs remain the series-specific notice and the realities of each subscription, region and workload.

Update: Microsoft says VM lifecycle has no fixed public cadence (October 7, 2026)​

Microsoft has not committed to a standard number of years that an Azure VM series will remain Current, Extended or End of Life. According to The Register, a Microsoft spokesperson said the company will continue to give advance notice when “select older-generation VM series” enter End of Life, but did not provide a timetable or minimum notice period.

The spokesperson also said customers will be notified directly about VM retirements specific to their deployments. For administrators, that reinforces the need to track Azure Service Health notices and series-level retirement guidance rather than treating the four lifecycle labels as a schedule.