Enhancing Microsoft Azure Virtual Machine lifecycle

Imported from official source

Azure continuously advances through new infrastructure generations, platform capabilities, services, and innovations that lead the industry in performance, security, reliability, and efficiency. Our Virtual Machine (VM) Lifecycle policy guides how we manage these transitions, giving Azure customers transparency, predictability, and guidance to plan for and execute technology changes with confidence. Our goal is to help every organization plan and navigate these modernization steps in line with Azure’s latest innovations and ongoing platform investments.

To give you access to the most advanced cloud and AI infrastructure, deployed on the most sophisticated silicon and hardware, the Azure Virtual Machine lifecycle is built around three customer outcomes:

  • Transparency to easily understand the lifecycle status of Azure technologies, Microsoft’s level of ongoing investment, and the recommended path forward as new innovations become available.
  • Predictability to plan against defined lifecycle stages, understand what to expect at each stage, and advance notice as technologies progress through their lifecycle.
  • Guidance to help you modernize and adopt newer technologies rapidly and with confidence, along with AI-led tooling to accelerate workload transitions and recommendations.
  • This lifecycle provides a shared taxonomy, common stages, and consistent commitments for how we communicate technology evolution.

    The lifecycle stages, spanning Current, Extended, End of Life, and Retired, are defined below, with dedicated Microsoft investment levels, regional and quota availability, applicable purchasing options, and pricing. The policy establishes clear lifecycle stages, expected customer experiences, and Microsoft’s commitments at each stage so customers can confidently plan, deploy, and modernize workloads over time.

    Note: Lifecycle details described in this policy represent general guidance and may be subject to product-specific, regional, or operational exceptions.

    This is an extract. The publication continues at the source.

    Read the original at the source: https://azure.microsoft.com/en-us/blog/enhancing-microsoft-azure-virtual-machine-lifecycle/

    Officially imported this from Microsoft Azure’s own source and shows an extract. If you work there, claiming the profile and verifying the domain lets you choose to show the full text here.

    Provenance

    Organization
    Microsoft Azure — imported from official source
    Official source
    https://azure.microsoft.com/en-us/blog/feed/ RSS
    Imported
    September 29, 2026 13:00
    Versions
    1 recorded
    Identity
    https://azure.microsoft.com/en-us/blog/?p=54069

    Officially records where a publication came from, not whether it is true. Imported records are reproduced from an organization's own official source.