Microsoft defines its Azure instance lifecycle, without any info about timing
Redmond explains how VMs die, but not when you can expect that to happen
Microsoft has introduced a new lifecycle for its Azure instances, although the timeframe for these changes remains undisclosed. The updated lifecycle comprises four stages: Current, Extended, End of Life, and Retired. VMs are categorized as Current when they are suitable for new deployments, widely available in regions, and receive regular maintenance and support.
Extended VMs are still supported but may face usage quotas and changes to purchasing options or pricing. During the End of Life phase, VMs remain operational for existing customers but may face limitations in availability and provisioning. The Retired stage marks VMs as unsupported, with no new instances available and data preserved.
Microsoft introduced this lifecycle to aid customers in navigating infrastructure transitions and adopting newer technologies. The company emphasizes its commitment to transparent and predictable change, offering early visibility and practical assistance to help customers modernize their Azure instances confidently. However, the spokesperson clarified that Microsoft does not set a fixed cadence for instance lifecycle transitions and only notifies customers directly regarding specific VM retirements.
Microsoft has previously mentioned running its servers for six years, but the link between this hardware retirement schedule and the new Azure lifecycle remains unclear. Regardless, the company is encouraging Azure customers to regularly evaluate their need to shift to newer instance types, which could benefit from more powerful processors and improved energy efficiency.
Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
