Blog Post

Azure Arc Blog
3 MIN READ

Upgrade to Azure Local, version 23H2 OS

mindydiep's avatar
mindydiep
Icon for Microsoft rankMicrosoft
Apr 04, 2025

Azure Stack HCI is now part of Azure Local. Learn more. 

Today, we’re sharing an update on the upgrade to Azure Local, version 23H2 OS.  

As described in a previous blog post, moving from Azure Stack HCI, version 22H2 to Azure Local, version 23H2 is a two-step process. The first step is to upgrade the operating system using existing processes and tools. The second step is to apply the upgrade for the mandatory Azure Arc solution enablement, which is a guided experience via the Azure portal. 

It is urgent that you perform the first step and install the OS upgrade to Azure Local, version 23H2 OS by May 31, 2025. After then, Azure Stack HCI, version 22H2 OS reaches end of support, and your system will stop receiving critical security updates and will not be eligible for support requests. 

Hear directly from one of our Azure Local customers, Australian supermarket brand Coles, on their experience successfully upgrading the OS for 1000 Azure Local machines in just 8 days! 

Coles: Preparing for the Future: Upgrading Azure Local (Stack HCI) from 22h2 to 23h2 

As we approach the end of life for Azure Local (Stack HCI) 22h2 in May 2025, it is crucial to prepare for the upcoming changes in management and deployment introduced in 23h2. This transition marks a significant step towards enhancing our cloud deployment and upgrade processes. 

The first step in this journey is to upgrade the operating system and cluster functional levels. This foundational move sets the stage for a seamless transition to the new version. Our team successfully upgraded 1000 nodes from 22H2 to 23H2 in just 8 days, showcasing our dedication and efficiency. This remarkable achievement was made possible through meticulous planning, including risk assessments, timeline creation, resource allocation, and establishing contingency plans to ensure a smooth transition. 

Several key technologies and processes played a pivotal role in this upgrade. We leveraged PowerShell scripts for much of the process, finding them to be the most reliable and repeatable method. Through comprehensive testing, we identified improvements that ensured we maintained high standards and minimized risks for the production system rollouts. While the thought of upgrading so many nodes was daunting, utilizing these familiar tools significantly eased the upgrade process. Our team's expertise with these tools enabled us to address challenges promptly and maintain a steady pace. Additionally, cross-departmental collaboration was crucial in streamlining operations and troubleshooting issues effectively. 

Looking ahead, we are excited about the new features and enhancements in 23H2. We are also planning to further refine our upgrade processes based on the insights gained from this experience. 

In conclusion, the successful upgrade from 22H2 to 23H2 demonstrates our team's capability to manage complex transitions efficiently. As we continue to innovate and improve our Azure Local deployment strategies, we remain committed to delivering high-quality solutions that meet the evolving needs of our organization. 

Jason Tayler, Lead Senior Systems Engineer, Coles 

Conclusion 

Coles is one of many customer success stories, and we hope this inspires you 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 about installing the OS upgrade, refer to the upgrade documentation 

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

Updated Apr 04, 2025
Version 1.0

1 Comment

  • I work for a Microsoft Direct Partner i Denmark (Fellowmind), and we are looking at upgrading several 22H2 stacks to 23H2 for multiple customers. We start next monday and I look forward working with this upgrade path. The first customer have a 4 noded cluster. The second customer have multiple 2 node clusters.