Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article lists known issues in Azure Stack Hub releases. The list is updated as new issues are identified.
To access known issues for a different version, use the version selector dropdown above the table of contents on the left.
Important
Review this article before applying the update.
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
The Microsoft Entra ID Graph API service is being retired. This retirement affects all Azure Stack Hub customers, and requires you to run the script included in this article for all affected applications.
- Applicable: This issue applies to release 2311 and later.
- Cause: Azure Kubernetes Service on Azure Stack Hub, currently in preview, is being discontinued and won't be released to general availability. If you try to register a new subscription to the Microsoft.Containerservice resource provider, the registration stays in the Registering state. If you try to create a new managed Kubernetes cluster or access existing managed Kubernetes clusters, you might see the raining cloud error screen.
- Remediation: We are aware of the problem and is working on a fix.
- Occurrence: Common.
- Applicable: This issue applies to all supported versions of Azure Stack Hub.
- Cause: The Microsoft Entra ID Graph API service is being retired.
- Remediation: Run the script included in this article for all impacted applications. The script sets a flag that configures these applications for an extension that allows these specific applications to continue calling the legacy Graph API until June 2025.
- Occurrence: Occasional.
- Applicable: This issue applies to release 2311 and later.
- Cause: The issue is caused by a change in the default ICMP behavior introduced with Windows Server 2022 that diverges from previous behavior, as well as Azure behavior.
- Remediation: You can add an inbound NSG rule to allow outbound ICMP packets to the internet. We are aware of the issue.
- Occurrence: Common.
- Applicable: This issue applies to release 2311 and later.
- Cause: Azure Kubernetes Service on Azure Stack Hub, currently in preview, is being discontinued and won't be released to general availability. If you try to register a new subscription to the Microsoft.Containerservice resource provider, the registration stays in the Registering state. If you try to create a new managed Kubernetes cluster or access existing managed Kubernetes clusters, you might see the raining cloud error screen.
- Remediation: We are aware of the issue and is working on a fix.
- Occurrence: Common.
- Applicable: This issue applies to release 2406 and later.
- Cause: The A-series VMs are deprecated in Azure, so they shouldn't be used in Azure Stack Hub.
- Remediation: Although Azure Stack Hub isn't removing the A-series SKU, other undefined behavior might occur if you continue using it (such as with the load balancer, VMSS, etc.). Therefore, you should use a different VM SKU when you're ready. There is no cost difference in using different VM SKUs on Azure Stack Hub.
- Occurrence: Common.
- Applicable: This issue applies to release 2408.
- Cause: Neither of the newly introduced ESv3 or DSv3 series; for example, E20s_v3, has nested virtualization enabled.
- Remediation: We are aware of the issue and is working on a fix.
- Occurrence: Common.
- Applicable: This issue applies to release 2406 and later.
- Cause: Due to a change in how subscription-level deployments are stored, an internal server error occurs when deploying or viewing deployments at subscription scope.
- Remediation: This issue is fixed in release 2501.
- Occurrence: Common.
- Applicable: This issue applies to release 2311 and later.
- Cause: The Nodes blade on the portal fails to load when a GPU property isn't configured.
- Remediation: We are aware of the issue and is working on a fix.
- Occurrence: Occasional.
- Applicable: This issue applies to release 2311 and later.
- Cause: Azure Kubernetes Service on Azure Stack Hub, currently in preview, is being discontinued and won't be released to general availability. If you try to register a new subscription to the Microsoft.Containerservice resource provider, the registration stays in the Registering state. If you try to create a new managed Kubernetes cluster or access existing managed Kubernetes clusters, you might see the raining cloud error screen.
- Remediation: We are aware of the problem and is working on a fix.
- Occurrence: Common.
- Applicable: This issue applies to release 2406 and later.
- Cause: The Standard Load Balancer portal blades for Logs and Diagnostic settings both show errors displaying the content.
- Remediation: The Standard Load Balancer in Azure Stack Hub does not support any diagnostic features.
- Occurrence: Common.
- Applicable: This issue applies to release 2406 and later.
- Cause: The A-series VMs are deprecated in Azure, so they shouldn't be used in Azure Stack Hub.
- Remediation: Although Azure Stack Hub isn't removing the A-series SKU, other undefined behavior might occur if you continue using it (such as with the load balancer, VMSS, etc.). Therefore, you should use a different VM SKU when you're ready. There is no cost difference in using different VM SKUs on Azure Stack Hub.
- Occurrence: Common.
- Applicable: This issue applies to release 2406 and later.
- Cause: Due to a change in how subscription-level deployments are stored, an internal server error occurs when deploying or viewing deployments at subscription scope.
- Remediation: This issue is fixed in release 2501.
- Occurrence: Common.
- Applicable: This issue applies to release 2311 and later.
- Cause: The Nodes blade on the portal fails to load when a GPU property isn't configured.
- Remediation: We are aware of the issue and is working on a fix.
- Occurrence: Occasional.
- Applicable: This issue applies to all supported versions of Azure Stack Hub.
- Cause: The update URL for Azure Stack Hub is changing from
https://azurestackhub.azureedge.net/PR/downloadtohttps://azurestackhub.download.prss.microsoft.com. - Remediation: To enable the update process, you must update your client firewall rules to allow HTTPS traffic from the Azure Stack Hub base URL
https://azurestackhub.download.prss.microsoft.com. - Occurrence: Common.
You can access older versions of Azure Stack Hub known issues in the table of contents on the left side, under the 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 Azure Customer Support Services.