Azure Local release information

Important

Azure Local versions 11.2510.1002.93 and 12.2510.1002.531 (supersedes 12.2510.1002.529) are now available.

If you're on 11.2510.1002.87, you can upgrade directly to 12.2510.1002.531.
If you're on an earlier version, first update to 11.2510.1002.93, then upgrade to 12.2510.1002.531.

To enhance your Azure Local (formerly known as Azure Stack HCI) experience, Microsoft periodically releases feature updates that introduce new capabilities and improvements. Additionally, Azure Local provides cumulative updates that include monthly quality and security enhancements. These updates are listed for each instance, ensuring your devices remain protected and productive.

This article provides the release information for Azure Local, including the release build and OS build information.

About Azure Local releases

Note

Azure Local previously followed an annual release cadence for OS and feature updates, with versions like 23H2 and 22H2. The versioning model changed to align with a monthly release train, like 2507 and 2506. However, some documentation might still reference the older versioning.

Azure Local includes multiple release trains: 2411, 2503, 2504, 2505, and so forth. Each release train after 2411 is either a feature build or cumulative update.

Feature build: The feature update build is the initial version of the software in a release train. Feature releases go beyond quality and security fixes, incorporating product enhancements, including updates for Azure Local services and agents.
Cumulative build: A cumulative update build includes the incremental updates from the most recent feature build.

The following diagram illustrates the feature builds, cumulative updates, and update paths.

Key considerations

Before the 2504 release, the solution only released one version each month, and it aligned with OS build 25398.xxxx.
Starting with Azure Local 2503, you can discover and import update packages for Azure Local with limited connectivity to Azure. For more information on how to import and discover update packages with limited connectivity, see Update via PowerShell with limited connectivity.

Starting with release 2504, Microsoft released two Azure Local solution versions each month, each aligned to a specific OS build. All future updates for a solution version continue to use its associated OS build. The following table lists each solution version and its corresponding OS build.

Solution version	OS build	Update path	Use case
10.2xxx or 11.25xx	25398.xxxx	2411 --> 2411.2 --> 2411.3 --> 2503 --> 2504 --> 2505 --> so forth.	Use this version to update your system through each feature and cumulative build.
12.25xx	26100.xxxx	2504 --> 2505 or other.	After 2504, use this version to install any of the subsequent releases directly within a feature release train.

To keep your Azure Local solution in a supported state, you have up to six months to install updates. However, before installing the feature update, make sure to install the last released cumulative update. For example, before installing the 2510 feature update, you must first install the last cumulative update, which is 2509 in this case.
Azure Arc resource bridge requires solution updates to be applied within one year. This requirement is critical to keep certificates valid and the Azure Local VM functionality working.
Before you can update to the 2511 release, you must first apply the 12.2510 update. The 12.2510 (24H2) update becomes automatically available once you apply 11.2510. Apply the 12.2510 update to keep your Azure Local up-to-date.

End of support for Azure Local versions

Important

Versions not updated within six months are no longer supported. Running an unsupported version may expose your environment to security vulnerabilities, compliance issues, or regulatory requirements associated with using an unsupported version. Microsoft doesn't guarantee or provide remediation for risks resulting from the continued use of unsupported versions. For supported versions, see the release trains diagram or the Support versions table.

OS version 22H2

Azure Stack HCI OS, version 22H2 is already out of support.

Monthly security and quality updates have stopped.
Your system continues to work, including registration and repair.
Billing has continued.
Microsoft Support is available only for upgrade assistance.

To continue receiving updates, we recommend upgrading your operating system to a newer version via PowerShell.

If you're running OS version 20349.xxxx (22H2) you won't be able to purchase Windows Server Subscription or Extended Security Updates (ESU).

If you're running an Azure Stack HCI, version 22H2 stretch cluster or managing the cluster via System Center Virtual Machine Manager, review the Supported workloads and configurations table for update timelines.

OS version 23H2

Azure Stack HCI, version 23H2 OS (OS version 25398.xxxx) will reach end of support in April 2026.

Each Azure Local release is supported for six months, whether you're on 23H2 (11.x.x.x) or 24H2 (12.x.x.x).
October 2025 (version 11.2510) is the final 23H2 release.
Support for the 23H2 OS without the Azure Local solution is available until April 2026.

After April 2026:

You won't receive monthly security and quality updates for 23H2.
Support requests are only available for patching to a supported release.

Stretched clusters running the 23H2 OS are supported until April 2026. For more information, see Upgrade stretched clusters to 23h2.

Starting with 2602, the Azure portal displays an "End of Support at the end of April" banner for devices running OS version 25398.xxxx (23H2).

Feature release availability timing

Feature release availability dates depend on the model and stock-keeping unit (SKU) of the servers in your cluster.

If your cluster supports Solution Builder Extension software updates, you receive feature release updates (for example, 2504 or 2510) after your hardware vendor completes their validation and confirms the release is ready. This process typically takes a few weeks following the Microsoft release and varies by hardware vendor.

Note

The validation process ensures a reliable update experience for your cluster. It minimizes potential problems and reduces the overall number of updates you need to manage for Azure Local.