Azure VM lifecycle sets retirement rules, but no fixed timetable

Microsoft’s September 28 policy explains how support, capacity and buying options change as older virtual-machine series approach retirement.

Microsoft’s September 28 policy explains how support, capacity and buying options change as older virtual-machine series approach retirement.
Microsoft has updated its Azure virtual-machine lifecycle policy to define how support, availability and purchasing conditions change as VM series age. Customers may face capacity restrictions and pricing changes before retirement, when existing machines will stop running and lose support.
Published on September 28, the policy sets out four stages: Current, Extended, End of Life and Retired. It is not yet clear how these stages differ from the previous lifecycle arrangement. Microsoft has not supplied fixed durations for the stages, The Register reported on October 7.
A virtual machine, or VM, is a virtual computer used to run applications and other tasks in the cloud. The first Azure VM families covered are General Purpose, Memory Optimized, Compute Optimized and Storage Optimized.
Microsoft recommends starting transition planning during Extended, rather than waiting for support to end. A quota is a limit on the amount of VM capacity a customer can use; restrictions on quotas can limit a customer’s ability to expand a deployment.
| Stage | Support and availability | Purchasing and pricing | Recommended action |
|---|---|---|---|
| Current | Standard maintenance and support, with broad availability across Azure regions. | Pay-as-you-go pricing and Azure Savings Plans. Azure Reserved VM Instances may also be offered. | Use for new deployments and expansion. |
| Extended | Standard maintenance and support continue. Available across multiple regions, but quota restrictions are possible. | Pay-as-you-go pricing and Azure Savings Plans; Reserved VM Instances may be offered. Purchasing options and pricing may change. | Begin evaluating and planning a move to Current VMs. |
| End of Life | Begins when retirement is formally announced. Standard maintenance and support continue. Available to existing customers in supported regions, within existing quotas and subject to capacity. New deployments and quota requests face restrictions. | Pay-as-you-go pricing and Azure Savings Plans remain available; Reserved Instances may no longer be offered. Customers should expect pricing and availability changes. | Actively plan and move applications and other workloads to Current or Extended VMs. |
| Retired | No Microsoft support or service-level agreement coverage. New VMs cannot be created, and existing VMs will be deallocated. | No longer available for purchase. | The move to Current or Extended VMs should be complete. |
Deallocation leaves a VM dormant, with its data preserved, The Register reports. That does not mean the VM continues running. At retirement, the machine also loses the service-level agreement, or SLA, that sets out Azure’s service commitments.
Microsoft also plans new ways to place workloads on End of Life VMs. It says customers may experience minor performance variations in rare cases, while existing SLAs will still be met. The lifecycle policy is general guidance and may have product-specific, regional or operational exceptions.
Microsoft told The Register it would continue to provide advance notice when selected older-generation VM series enter End of Life. A spokesperson also said customers receive direct notifications about their specific VM retirements. Microsoft’s policy promises migration tools and guidance during End of Life.
Microsoft says Azure Advisor and Azure Service Health help customers find upcoming VM retirements, identify affected resources and track their transition with recommended actions. Those tools and retirement notices give customers a way to identify which deployments need to move before their VM series reaches Retired.

The appeal follows a release of hundreds of claimed solutions and a dispute over how to check, credit and explain SI-generated proofs.
6 min

Sierra, Walmart and Stripe are working with Meta on rules the partners say would help businesses recognize authorized agents and see their activity.
2 min

A patch is reported to fix the flaw; CISA also recommends limiting control-system network exposure.
2 min