Azure Stack Hub known issues
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.
Compute
Azure Kubernetes Service on Azure Stack Hub
- 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: Microsoft is aware of the problem and is working on a fix.
- Occurrence: Common.
Graph API retirement
- 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.
Networking
Outbound ICMP to internet is blocked by default for tenant VM
- 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. Microsoft is aware of the issue.
- Occurrence: Common.
Compute
Azure Kubernetes Service on Azure Stack Hub
- 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: Microsoft is aware of the issue and is working on a fix.
- Occurrence: Common.
A-series VMs deprecated
- 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.
ESv3 and DSv3 series don't have nested virtualization enabled
- 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: Microsoft is aware of the issue and is working on a fix.
- Occurrence: Common.
Portal
Deployments blade under subscription fails to load
- 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: Microsoft is aware of the issue and is working on a fix.
- Occurrence: Common.
Nodes blade fails to load
- 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: Microsoft is aware of the issue and is working on a fix.
- Occurrence: Occasional.
Compute
Azure Kubernetes Service on Azure Stack Hub
- 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: Microsoft is aware of the problem and is working on a fix.
- Occurrence: Common.
Standard Load Balancer portal error
- 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.
A-series VMs deprecated
- 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.
Portal
Deployments blade under subscription fails to load
- 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: Microsoft is aware of the issue and is working on a fix.
- Occurrence: Common.
Nodes blade fails to load
- 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: Microsoft is aware of the issue and is working on a fix.
- Occurrence: Occasional.
Update
Update URL is changing
- 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/download
tohttps://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.
2311 archived known issues
2306 archived known issues
2301 archived known issues
2206 archived known issues
2108 archived known issues
2102 archived known issues
2008 archived known issues
2005 archived known issues
2002 archived known issues
1910 archived known issues
1908 archived known issues
1907 archived known issues
1906 archived known issues
1905 archived known issues
1904 archived known issues
1903 archived known issues
1902 archived known issues
1901 archived known issues
1811 archived known issues
1809 archived known issues
1808 archived known issues
1807 archived known issues
1805 archived known issues
1804 archived known issues
1803 archived known issues
1802 archived known issues
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 Microsoft Customer Support Services.