Azure Stack Hub release notes
This article describes the contents of Azure Stack Hub update packages. The update includes improvements and fixes for the latest release of Azure Stack Hub.
To access release notes for a different version, use the version selector dropdown above the table of contents on the left.
Important
This update package requires an OEM package version of 2.3 or later. For more information, see the OEM contact information.
Important
The 2311 update introduces a change in the base host OS, updated to Windows Server 2022. Disconnected customers must obtain and update a SQL Server 2019 product key (PID). You must get the key before starting the update. To obtain this key, contact Microsoft support. If you start the update without this key, the update will fail shortly after starting, with a "Prepare of Role Cloud raised an exception" message, which advises you contact support. You can resume the update after applying the new key.
Important
This update package is only for Azure Stack Hub integrated systems. Do not apply this update package to the Azure Stack Development Kit (ASDK).
Important
If your Azure Stack Hub instance is behind by more than two updates, it's considered out of compliance. You must update to at least the minimum supported version to receive support.
Important
If your Azure Stack Hub instance does not have an active support contract with the hardware partner, it's considered out of compliance. You must have an active support contract for the hardware to receive support.
Before applying the update, make sure to review the following information:
For help with troubleshooting updates and the update process, see Troubleshoot patch and update issues for Azure Stack Hub.
You can download the Azure Stack Hub update package using the Azure Stack Hub update downloader tool.
The Azure Stack Hub 2408 update build number is 1.2408.0.19.
The Azure Stack Hub 2408 update build type is Full. This build contains only important security updates.
The 2501 update has the following expected runtimes based on our internal testing:
- 4 nodes: 8-28 hours
- 8 nodes: 11-30 hours
- 12 nodes: 14-34 hours
- 16 nodes: 17-40 hours
Exact update durations typically depend on the capacity used on your system by tenant workloads, your system network connectivity (if connected to the internet), and your system hardware specifications. Durations that are shorter or longer than the expected value are not uncommon and do not require action by Azure Stack Hub operators unless the update fails. This runtime approximation is specific to the 2408 update and should not be compared to other Azure Stack Hub updates.
For more information about update build types, see Manage updates in Azure Stack Hub.
Important
- With the 2408 update, we are introducing the ESv3 and DSv3 VM SKUs. These new SKUs are designed to provide higher IOPS for both OS and data disks. For more information, see Azure Stack Hub VM SKUs.
- We are also introducing two new VM SKUs to support the L40s GPUs.
- Starting with Azure Stack Hub 2311, we are not releasing updated Azure Stack Development Kit (ASDK) versions. This decision is due to modifications to internal services that would lead to substantial complexity for the ASDK. The currently released ASDK version remains suitable for operational, testing, or training purposes, including for the Azure Stack Hub Foundation Core scripts used for Azure-Stack-Hub-Foundation-Core.
For information about security updates in this update of Azure Stack Hub, see Azure Stack Hub security updates.
Azure Stack Hub releases hotfixes regularly. Starting with the 2005 release, when you update to a new major version (for example, 1.2008.x to 1.2102.x), the latest hotfixes (if any) in the new major version are installed automatically. From that point forward, if a hotfix is released for your build, you should install it.
Note
Azure Stack Hub hotfix releases are cumulative; you only need to install the latest hotfix to get all fixes included in any previous hotfix releases for that version.
For more information, see our servicing policy.
Azure Stack Hub hotfixes are only applicable to Azure Stack Hub integrated systems; do not attempt to install hotfixes on the ASDK.
The 2408 release of Azure Stack Hub must be applied on the 2406 release with the following hotfix installed:
When you update to a new major version (for example, 1.2108.x to 1.2206.x), the latest hotfixes (if any) in the new major version are installed automatically. From that point forward, if a hotfix is released for your build, you should install it.
After the installation of 2408, if any hotfixes for 2408 are subsequently released, you should install them:
The Azure Stack Hub 2406 update build number is 1.2406.0.8.
The Azure Stack Hub 2406 update build type is Full. This build contains only important security updates.
The 2408 update has the following expected runtimes based on our internal testing:
- 4 nodes: 8-28 hours
- 8 nodes: 11-30 hours
- 12 nodes: 14-34 hours
- 16 nodes: 17-40 hours
Exact update durations typically depend on the capacity used on your system by tenant workloads, your system network connectivity (if connected to the internet), and your system hardware specifications. Durations that are shorter or longer than the expected value are not uncommon and do not require action by Azure Stack Hub operators unless the update fails. This runtime approximation is specific to the 2406 update and should not be compared to other Azure Stack Hub updates.
For more information about update build types, see Manage updates in Azure Stack Hub.
- With 2406 we are announcing the general availability of the Azure Stack Hub Standard Load Balancer. The Standard Load Balancer enables several new load balancing scenarios such as: standalone VMs in backend pools, HTTPs probes, high-availability ports, and TCP Reset on idle.
- With 2406 we are announcing the general availability of Azure Container Registry. Azure Container Registry is a private, secure, and close-to-compute registry for Windows container images, Linux container images, Helm charts, and other OCI artifacts. At no extra cost, it enables both connected and disconnected customers to quickly and reliably store, deploy, and manage container workloads through the user portal, PowerShell, Azure CLI, and/or Docker CLI. It also enables those customers to assign role-based access control (RBAC) and to create webhooks. Container Registry is now fully supported and fully integrated with other components of Azure Stack Hub, such as the Azure Kubernetes Service (AKS) engine. To install Container Registry, follow the instructions here.
- With 2406 we are announcing the general availability of Azure Site Recovery. Azure Site Recovery on Azure Stack Hub helps to ensure business continuity by replicating virtual machine (VM) workloads from a primary site to a secondary location. The GA version has a simplified deployment (no dependency services). Note that the transition from preview versions to GA requires a full reinstallation of the Azure Site Recovery solution (no upgrade path is be possible).
- Starting with Azure Stack Hub 2311, we are not releasing updated Azure Stack Development Kit (ASDK) versions. This decision is due to modifications to internal services that would lead to substantial complexity for the ASDK. The currently released ASDK version remains suitable for operational, testing, or training purposes, including for the Azure Stack Hub Foundation Core scripts used for Azure-Stack-Hub-Foundation-Core.
For information about security updates in this update of Azure Stack Hub, see Azure Stack Hub security updates.
Azure Stack Hub releases hotfixes regularly. Starting with the 2005 release, when you update to a new major version (for example, 1.2008.x to 1.2102.x), the latest hotfixes (if any) in the new major version are installed automatically. From that point forward, if a hotfix is released for your build, you should install it.
Note
Azure Stack Hub hotfix releases are cumulative; you only need to install the latest hotfix to get all fixes included in any previous hotfix releases for that version.
For more information, see our servicing policy.
Azure Stack Hub hotfixes are only applicable to Azure Stack Hub integrated systems; do not attempt to install hotfixes on the ASDK.
The 2406 release of Azure Stack Hub must be applied on the 2311 release with the following hotfix installed:
When you update to a new major version (for example, 1.2108.x to 1.2206.x), the latest hotfixes (if any) in the new major version are installed automatically. From that point forward, if a hotfix is released for your build, you should install it.
After the installation of 2406, if any hotfixes for 2406 are subsequently released, you should install them:
The Azure Stack Hub 2311 update build number is 1.2311.1.22.
The Azure Stack Hub 2311 update build type is Full. This build contains only important security updates.
The 2311 update has the following expected runtimes based on our internal testing:
- 4 nodes: 36-50 hours
- 8 nodes: 36-50 hours
- 12 nodes: 50-80 hours
- 16 nodes: 50-90 hours
Important
Disconnected environments have additional prerequisite steps, which might increase this duration. See the following section for required steps to obtain and update a SQL Server 2019 product key (PID).
Exact update durations typically depend on the capacity used on your system by tenant workloads, your system network connectivity (if connected to the internet), and your system hardware specifications. Durations that are shorter or longer than the expected value are not uncommon and do not require action by Azure Stack Hub operators unless the update fails. This runtime approximation is specific to the 2311 update and should not be compared to other Azure Stack Hub updates.
For more information about update build types, see Manage updates in Azure Stack Hub.
- The VPN Fast Path for operators feature, and for users, is now generally available. The new VPN SKUs enable scenarios in which higher network throughput is necessary. See the documentation for more information about this feature.
- With 2311 we are announcing the public preview of the Azure Stack Hub Standard Load Balancer. This feature enables several scenarios: allowing standalone VMs to be in a backend pool, HTTPS probes, high-availability ports, and TCP reset on idle.
- Azure Site Recovery is currently in public preview, which features a simplified deployment process that only requires one dependency. We aim to further streamline this solution by the time of our general availability launch in early 2024, at which point we plan to eliminate all dependencies except for the Site Recovery resource provider itself. In the meantime, we encourage you to test and provide feedback on the public preview to help us enhance the GA version. Be aware that the transition from preview to GA will require a full reinstallation of the Azure Site Recovery solution (no update or upgrade path will be possible).
2311 introduces a change in the base host OS, updated to Windows Server 2022, in order to simplify future updates and security fixes. This change is part of the fabric. Azure Stack Hub environments that have outbound connectivity do not require any additional changes, and the update is installed directly.
Important
Disconnected customers must obtain and update a SQL Server 2019 product key (PID). You must get the key before starting the update. To obtain this key, contact Microsoft support. If you start the update without this key, the update will fail shortly after starting, with a "Preparation of Role Cloud raised an exception" message, which advises you contact support. You can resume the update after applying the new key.
Starting with Azure Stack Hub 2311, we are not releasing new Azure Stack Development Kit (ASDK) versions. This decision is due to modifications to internal services that would lead to substantial complexity for the ASDK. The currently released ASDK version remains suitable for operational, testing, or training purposes, including for the Azure Stack Hub Foundation Core scripts used for Azure-Stack-Hub-Foundation-Core.
For information about security updates in this update of Azure Stack Hub, see Azure Stack Hub security updates.
Azure Stack Hub releases hotfixes regularly. Starting with the 2005 release, when you update to a new major version (for example, 1.2008.x to 1.2102.x), the latest hotfixes (if any) in the new major version are installed automatically. From that point forward, if a hotfix is released for your build, you should install it.
Note
Azure Stack Hub hotfix releases are cumulative; you only need to install the latest hotfix to get all fixes included in any previous hotfix releases for that version.
For more information, see our servicing policy.
Azure Stack Hub hotfixes are only applicable to Azure Stack Hub integrated systems; do not attempt to install hotfixes on the ASDK.
The 2311 release of Azure Stack Hub must be applied on the 2306 release with the following hotfix installed:
When you update to a new major version (for example, 1.2108.x to 1.2206.x), the latest hotfixes (if any) in the new major version are installed automatically. From that point forward, if a hotfix is released for your build, you should install it.
After the installation of 2311, if any hotfixes for 2311 are subsequently released, you should install them:
You can access older versions of Azure Stack Hub release notes in the table of contents on the left side, under Resources > Release notes archive. Select the desired archived version from the version selector dropdown in the upper left. These archived articles are provided for reference purposes only and do not imply support for these versions. For information about Azure Stack Hub support, see Azure Stack Hub servicing policy. For further assistance, contact Microsoft Customer Support Services.