Microsoft defines its Azure instance lifecycle, without any info about timing

Microsoft has updated the lifecycle of an Azure instance, without offering any information on how long it takes for an instance type to expire. Redmond’s “enhanced lifecycle” landed in late September in a post that explains the four phases in the life of a cloudy VM: Current – VMs are recommended for new deployments, are available in many regions, and receive standard maintenance and support; Extended – Still supported, but may be subject to usage quotas and unspecified “changes to purchasing options and pricing.” Microsoft recommends planning a move to Current VMs. End of Life – VMs are still supported but are only available to existing customers and you may not be able to get more of the instances you want. Once VMs reach this stage, Microsoft wants you “actively” working to shift workloads onto Current or Extended VMs. Retired – Unsupported but not quite dead. …