Urgent.News

What's breaking now, across thousands of outlets.

Tech

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 defines its Azure instance lifecycle, without any info about timing

Microsoft has introduced a new lifecycle for its Azure instances, outlining four stages: Current, Extended, End of Life and Retired. The Current phase is for new deployments, while the Extended phase may entail usage quotas and changes to purchasing options and pricing. After this, the End of Life stage begins, during which the VMs are still supported but not available for new customers.

The Retired phase is when the VMs are unsupported and not available for provisioning. Microsoft's commitment to helping customers navigate these transitions is evident through the "predictable, transparent, and supported" guidance provided in the lifecycle updates. The company also mentioned that it plans to continue notifying customers about specific VM retirements.

Microsoft states that it runs its servers for six years, but the link between this hardware retirement schedule and the new Azure lifecycle is unclear. Regardless, the updates encourage customers to consider moving to newer instance types for improved performance and reduced energy consumption, which could lead to cost savings for Microsoft.

Written by urgent.news from The Register's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at theregister.com →

More in Tech

Taming the Exchange API: Handling -4509 Errors and the F-065 Retry Mechanism in Quant Systems

Taming the Exchange API: Handling -4509 Errors and the F-065 Retry Mechanism in Quant Systems Tags: #algotrading #crypto #ai #buildinpublic The Incident: When Local Truth Meets Exchange Reality It was…

  • -4509 error occurs when GTE order lacks anchored open position
  • F-065 Retry Mechanism handles transient API rejection errors
  • Three failed stop-loss adjustments before successful F-065 retry

More from Wednesday 7 October →