Blog Post

Azure Arc Blog
2 MIN READ

Upgrade Azure Local operating system to new version

mindydiep's avatar
mindydiep
Icon for Microsoft rankMicrosoft
Jun 13, 2025

Today, we’re sharing more details about the end of support for Azure Local, with OS version 25398.xxxx (23H2) on October 31, 2025. After this date, monthly security and quality updates stop, and Microsoft Support remains available only for upgrade assistance. Your billing continues, and your systems keep working, including registration and repair. 

There are several options to upgrade to Azure Local, with OS version 26100.xxxx (24H2) depending on which scenario applies to you.

Scenario #1: You are on Azure Local solution, with OS version 25398.xxxx 

If you're already running the Azure Local solution, with OS version 25398.xxxx, there is no action required. You will automatically receive the upgrade to OS version 26100.xxxx via a solution update to 2509. 

Refer to Azure Local, version 23H2 and 24H2 release information - Azure Local | Microsoft Learn for the latest version of the diagram.

If you are interested in upgrading to OS version 26100.xxxx before the 2509 release, there will be an opt-in process available in the future with production support. 

Scenario #2: You are on Azure Stack HCI and haven’t performed the solution upgrade yet 

Scenario #2a: You are still on Azure Stack HCI, version 22H2 

With the 2505 release, a direct upgrade path from version 22H2 OS (20349.xxxx) to 24H2 OS (26100.xxxx) has been made available. To ensure a validated, consistent experience, we have reduced the process to using the downloadable media and PowerShell to install the upgrade.  

If you’re running Azure Stack HCI, version 22H2 OS, we recommend taking this direct upgrade path to the version 24H2 OS. Skipping the upgrade to the version 23H2 OS will be one less upgrade hop and will help reduce reboots and maintenance planning prior to the solution upgrade. After then, perform post-OS upgrade tasks and validate the solution upgrade readiness.  

Consult with your hardware vendor to determine if version 24H2 OS is supported before performing the direct upgrade path.

The solution upgrade for systems on the 24H2 OS is not yet supported but will be available soon.

Scenario #2b: You are on Azure Stack HCI, version 23H2 OS  

If you performed the upgrade from Azure Stack HCI, version 22H2 OS to version 23H2 OS (25398.xxxx), but haven’t applied the solution upgrade, then we recommend that you perform post-OS upgrade tasks, validate the solution upgrade readiness, and apply the solution upgrade.

Diagram of Upgrade Paths

Conclusion 

We invite you to identify which scenarios apply to you and take action to upgrade your systems. On behalf of the Azure Local team, we thank you for your continuous trust and feedback! 

Learn more 

To learn more, refer to the upgrade documentation.   

For known issues and remediation guidance, see the Azure Local Supportability GitHub repository.

Updated Jul 07, 2025
Version 4.0
adaptive cloud
azure arc

9 Comments

  • awfma's avatar
    awfma
    Copper Contributor
    Aug 01, 2025

    Hi,

    I have a client who was running 22H2 stretched cluster but recently upgraded to 23H2 25398.2505.  I understand this use case falls under Scenario #1 in your article above.

    Although the current environment is running 25398.2505, the previous stretched cluster configurations inherited from 22H2 is still in place.  Will this be an issue when the environment is automatically upgraded to OS version 26100.xxxx via a solution update to 2509?  Will the environment remains in a supported state after automatic upgrade to OS version 26100.xxxx?

    Thanks,

    Adrian

    • philcruicks's avatar
      philcruicks
      Copper Contributor
      Aug 27, 2025

      mindydiep​ I also have the same question...for both this and the direct 22H2 to 24H2 upgrade, is an existing stretch still supported on both scenarios?

  • LCKho3693's avatar
    LCKho3693
    MVP
    Jul 09, 2025

    mindydiep​ Thank you for the great sharing. 
    This the the official information that all of us have been waiting for which provides a clearer, supported and validated path for Azure Local OS upgrading. 
    Well done. 

  • Karl-WE's avatar
    Karl-WE
    MVP
    Jul 01, 2025

    Thank you for sharing this guidance. It is now truly clear and transparent how the upgrades should be executed.

  • Crispin's avatar
    Crispin
    Copper Contributor
    Jun 18, 2025

    Awesome, I did the jump from 22H2 to 24H2 the last week of May in the EOL/EOS race so glad to see something official-adjacent about it. Any word on the Solution Upgrade release (US/east/central)? I understand we should -NOT- use Windows Update to apply the CUs if I am planning on the Solution Update cycles to work, so I am holding off, but that makes compliance slip - unless it IS safe to do it?

    • Crispin's avatar
      Crispin
      Copper Contributor
      Jun 18, 2025

      It doesn't have that same ring like "Happy Azure Stacking!" did... but in this case the OS in question is still called Azure Stack HCI, so Happy Azure Stacking to you! 🤣

  • rajeevkumar2's avatar
    rajeevkumar2
    Copper Contributor
    Jun 16, 2025

    Right now we do not have option to upgrade 23H2 Azure local to 24H2 Azure local?

    what is opt in process for upgrading the OS to version 26100.xxxx ?