You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-local/release-information-23h2.md
+17-42Lines changed: 17 additions & 42 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,8 +16,6 @@ ms.date: 05/28/2025
16
16
17
17
To enhance your Azure Local (formerly known as Azure Stack HCI) experience, we periodically release 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.
18
18
19
-
To keep your Azure Local solution in a supported state, you have up to six months to install updates, but we recommend installing updates as they're released.
20
-
21
19
This article provides the release information for Azure Local, including the release build and OS build information.
22
20
23
21
## About Azure Local releases
@@ -32,6 +30,16 @@ The following diagram illustrates the feature builds, cumulative updates, and up
32
30
33
31
:::image type="content" source="./media/release-information-23h2/release-trains-supported-update-paths.png" alt-text="Diagram illustrating Azure Local release trains with supported update paths."lightbox="./media/release-information-23h2/release-trains-supported-update-paths.png":::
34
32
33
+
## Key considerations
34
+
35
+
- Azure Arc resource bridge requires solution updates to be applied within one year. This is critical to keep certificates valid and the Azure Local VM functionality working.
36
+
37
+
- Prior to the 2504 release, only one solution version was released monthly with OS build 25398.xxxx.
38
+
39
+
- All future updates will continue using the OS build associated with their respective solution version.
40
+
41
+
- To keep your Azure Local solution in a supported state, you have up to six months to install updates, but we recommend installing updates as they're released.
42
+
35
43
## Feature release availability timing
36
44
37
45
Feature release availability dates depend on the model and SKU of the servers in your cluster.
@@ -43,55 +51,22 @@ If your cluster supports [Solution Builder Extension software updates](./update/
43
51
44
52
## Update paths
45
53
46
-
### Existing deployments
47
-
48
-
For existing deployments, such as the 2411 feature build, you can update to any of the 2411 cumulative update builds. This path includes the 2411.2 and 2411.3 cumulative updates, which are required to update to the 2503 feature build. The 2503 feature build is required to update to the 2504 feature build.
For new deployments, install a feature build directly. For example, you can install the 2504 build which has an OS version 261000.3775 and solution version 12.2504.1001.20. After the installation, you can install the latest cumulative update build (2505) to keep your system up to date.
54
+
Starting with the 2504 release, two solutions versions are available each month, each aligned with a specific OS build. One solution runs OS image version 25398.xxxx and the other solution runs OS image version 26100.xxxx.
57
55
58
-
<!-- ### Move to the next release train
59
-
60
-
Follow these guidelines to skip releases with the same release train as you move to the next release train:
61
-
62
-
- Update the existing deployment to a build that allows you to move to the next release train. The following table provides examples of how to move between release trains:
| From 2411 to 2503 | 2411 -- 2411.2 -- 2411.3 -- 2503 |
67
-
| From 2411 to 2504 | 2411 -- 2411.2 -- 2411.3 -- 2503 -- 2504|
68
-
69
-
### Move within the same release train
70
-
71
-
Follow these guidelines to update to each release within your current release train:
72
-
73
-
- Within your release train, you can update to the latest update build anytime. For example, if you're running the 2411 feature build, you can update to any of the 2411 cumulative update builds, such as 2411.1, 2411.2, or 2411.3.
74
-
75
-
| Timeframe for 2411 release train | Update path |
> To keep your Azure Local instance in a supported state, you have up to six months to install updates. For example, if you're running the 2408 feature build, update to a later build within six months.
| 11.25xx | 25398.xxxx | Use this version to update your system through each feature and cumulative build. |
59
+
| 12.25xx | 26100.xxxx | Use this version to install a specific build directly. |
83
60
84
61
## Azure Local release information summary
85
62
86
63
### Supported versions of Azure Local
87
64
88
65
The following tables summarize the release information for Azure Local across all supported versions. All dates are listed in ISO 8601 format: *YYYY-MM-DD*.
89
66
90
-
Starting in 2504, we offer two releases. One release provides the path to upgrade from 2503 to 2504. The other release supports a new deployment of 2504.
91
-
92
67
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](./update/import-discover-updates-offline-23h2.md).
0 commit comments