Azure Stack Hub archived known issues

Article
10/24/2024

This article lists known issues in unsupported Azure Stack Hub releases. The list is updated as new issues are identified.

To access known issues for a different archived version, use the version selector dropdown above the table of contents on the left.

App Service

Incorrect rotation status after secret rotation of resource provider certificates

Applicable: This issue applies to all Azure Stack Hub add-on resource providers.
Cause: After secret rotation, the rotation state shows as "in progress" even though the rotation completed successfully, the provisioning state shows "successful," and the expiration date is updated.
Remediation: None. No impact to your system or workloads.
Occurrence: All supported versions of Azure Stack Hub.

Portal

Incorrect reporting of node CPU cores in the admin portal

Applicable: This issue applies to release 2301.
Cause: The number of cores reported in the Azure Stack Hub admin portal in the cluster Nodes Capacity window is incorrect. This is cosmetic and an issue with a change in 2301 with respect to how the Fabric Resource Provider gets this information. This impacts both new deployments and existing stamps updating to 2301, but doesn't affect operation of the stamp or any workload deployments.
Remediation: Microsoft is aware of the problem and is working on a fix.
Occurrence: Minor portal issue that occurs consistently.

App Service

Incorrect rotation status after secret rotation of resource provider certificates

Applicable: This issue applies to all Azure Stack Hub add-on resource providers.
Cause: After secret rotation, the rotation state shows as "in progress" even though the rotation completed successfully, the provisioning state shows "successful," and the expiration date is updated.
Remediation: None. No impact to your system or workloads.
Occurrence: All supported versions of Azure Stack Hub.

Alerts

Geographical region not provided

Applicable: This issue applies to release 2206.
Cause: The alert Geographical region not provided is displayed, and asks you to make a choice for Schrems II compliance.
Remediation: You can run the following PowerShell cmdlet to set geographical preference:
```
Set-DataResidencyLocation -Europe:$true or $false 
```
The residency location for the data will be updated and all data will be stored and processed in the EU. Close this alert manually, or ignore it after the geographical region preference appears in the admin portal (as described in EU Schrems II initiative for Azure Stack Hub). The alert remains active for up to one week, even after the choice is made.
Occurrence: Common

Encryption recovery keys retrieval warning

Applicable: This issue applies to release 2206 and later.
Cause: An Encryption recovery keys retrieval warning is displayed, and asks you to retrieve and securely store the encryption recovery keys outside of Azure Stack Hub. The warning occurs to ensure that you have retrieved the recovery keys. If you have previously retrieved the recovery keys and are getting this alert after the 2206 update (or beyond), please make sure to collect the recovery keys again. Recovery keys may be required in the case where host nodes display the BitLocker recovery key screen after unplanned reboots; for example, power outages.
Remediation: Retrieve the encryption keys and store them in a secure location outside of Azure Stack Hub. From the PEP, run the following command, and save the recovery keys that are returned:
```
## Retrieves recovery keys for all volumes that are encrypted with BitLocker
Get-AzsRecoveryKeys -raw
```
For more information, see Retrieving BitLocker recovery keys. Note that the alert will automatically close within 24 hours after running Get-AzsRecoveryKeys and storing those recovery keys in a secure location outside of Azure Stack Hub.
Occurrence: Common

Portal

Possibility of portal errors during update

Applicable: This issue applies to release 2206.
Cause: The update blade and/or the portal dashboard can become unusable and show an error during the update itself.
Remediation: If the portal is unavailable for more than 1 hour, you can use the PEP to check the status of the update. For more information, see Monitor updates in Azure Stack Hub using the privileged endpoint.

Applicable: This issue applies to release 2108 and newer.
Cause: The Azure portal recommends the upgrade from Basic to Standard SKU; however, this functionality is not supported in Azure Stack Hub.
Remediation: Don't attempt the upgrade, as it will fail.
Occurrence: Common

Applicable: This issue applies to releases 2102 and newer.
Cause: Menu items are not displayed when clicking on disk instance on the Virtual Machines overview blade.
Remediation: Refresh the page and the menu should reappear. Alternatively, you can navigate to the specific disk instance via the Disks area in the portal.
Occurrence: Minor portal issue that occurs consistently.

Datacenter integration

Graph configuration fails

Applicable: This issue applies to release 2206.
Cause: The configuration of Graph fails with an invalid credential error.
Remediation: If credentials are correct, you must supply them as username only, rather than domainname\username.
Occurrence: Common

Update

Update to 2108 will not proceed if there are AKS clusters or ACR registries created and the private previews of AKS and ACR services are installed

Applicable: This issue applies to Azure Kubernetes Service (AKS) and Azure Container Registry (ACR) private preview customers who plan to upgrade to 2108.
Remediation: The operator must delete all AKS clusters and ACR Registries and uninstall the private preview of the AKS and ACR services.
Occurrence: Any stamp that has the AKS and ACR private previews installed will experience this message.

For known Azure Stack Hub update issues, see Troubleshooting Updates in Azure Stack Hub.

Networking

Load Balancer

Load Balancer rules

Applicable: This issue applies to all supported releases.
Cause: Updating/changing the load distribution property (session persistence) has no effect and some virtual machines might not participate in the traffic load distribution. For example, if you have 4 backend virtual machines and only 2 clients connecting to the load balancer, and the load distribution is set to client IP, the client sessions will always use the same backend virtual machines. Changing the load distribution property to "none" to distribute the client connections across all the backend virtual machines will have no effect.
Remediation: Recreating the load balancing rule will ensure the selected settings are correctly configured to all backend VMs.
Occurrence: Common

Cannot create a Virtual Machine Scale Set with a data disk attached

Applicable: This issue applies to release 2108.
Cause: Missing properties for the object type data disk.
Remediation: Add data disks after deployment.
Occurrence: Common

Create disk snapshot can fail

Applicable: This issue applies to release 2108.
Cause: Missing properties for snapshot operation.
Remediation: Apply hotfix 1.2108.2.73.
Occurrence: Common

Portal

Container registries

Metrics unavailable for container registries in the user portal

Applicable: This issue applies to the public preview release of Azure Container Registry on Azure Stack Hub.
Cause: An issue is preventing metrics from displaying when viewing a container registry in the Azure portal. The metrics are also not available in Shoebox.
Remediation: No remediation available, will be addressed in an upcoming hotfix.
Occurrence: Common

Container Registry operator experience prompting to install although installation already complete

Applicable: This issue applies to the public preview release of Azure Container Registry on Azure Stack Hub.
Cause: Seven days following the installation of Container Registry, the operator experience in the admin portal may prompt the operator to install Container Registry again. The service is operating normally but the operator experience is not available. Tenants are able to create and manage container registries.
Remediation: No remediation available, will be addressed in an upcoming hotfix.
Occurrence: Common

Administrative subscriptions

Applicable: This issue applies to all supported releases.
Cause: The two administrative subscriptions that were introduced with version 1804 should not be used. The subscription types are Metering, and Consumption.
Remediation: If you have resources running on these two subscriptions, recreate them in user subscriptions.
Occurrence: Common

Create DNS blade results in portal crashing

Applicable: This issue applies to all supported releases with hotfix version 1.2108.2.81.
Cause: Two specific flows sometimes end with the user portal crashing:
- Create a resource > Networking > DNS zone
- Create a resource > Networking > Connection
Remediation: The following workflow can ensure there are no crashes:
- All services > DNS zone > + Add or All services > Connections > + Add
Occurrence: Common

Portal shows "Unidentified User" instead of user email

Applicable: This issue applies to all systems with hotfix version 1.2108.2.81 that are using a Microsoft Entra account without an email address in the account profile.
Remediation: Sign in to the Azure portal, and add an email address to the Microsoft Entra account that is experiencing this issue.
Occurrence: Common

Applicable: This issue applies to release 2108 and newer.
Cause: The Azure portal recommends the upgrade from Basic to Standard SKU; however, this functionality is not supported in Azure Stack Hub.
Remediation: Don't attempt the upgrade, as it will fail.
Occurrence: Common

Applicable: This issue applies to releases 2102 and newer.
Cause: Menu items are not displayed when clicking on disk instance on the Virtual Machines overview blade.
Remediation: Refresh the page and the menu should reappear. Alternatively, you can navigate to the specific disk instance via the Disks area in the portal.
Occurrence: Minor portal issue that occurs consistently.

Data plane clusters are in an unhealthy state with all nodes in warning state

Applicable: This issue applies to all supported releases of Event Hubs on Azure Stack Hub.
Cause: Internal infrastructure secrets may be nearing expiration.
Remediation: Update to the latest Event Hubs on Azure Stack Hub release, then complete the process in How to rotate secrets for Event Hubs on Azure Stack Hubs.

Data plane clusters' health isn't getting updated in admin portal or scale-out of clusters results in access denied

Applicable: This issue applies to all supported releases of Event Hubs on Azure Stack Hub.
Cause: Internal components haven't refreshed their cache with new secrets, after secret rotation is completed.
Remediation: Open a support request to receive assistance.

Azure Stack Hub backup fails

Applicable: This issue applies to all supported releases of Event Hubs on Azure Stack Hub.
Cause: Internal infrastructure secrets may have expired.
Remediation: Open a support request to receive assistance.

Azure Kubernetes Service (AKS)

Applications deployed to AKS clusters fail to access persistent volumes

Applicable: This issue applies to release 2108.
Cause: When you deploy an AKS cluster using:
- Kubernetes 1.19, or
- Kubernetes 1.20 with Kubenet as the network plug-in
  And deploy an application that uses persistent volumes, you will note an issue with the application's pod when it tries to deploy a persistent volume. If you look into the pod's log, you may find an error regarding permissions denied. The problem resides in Azure Stack Hub's Azure Disk CSI driver.
Remediation: When deploying an AKS cluster, you should select only Kubernetes version 1.20 and Azure CNI for the Network plugin.
Occurrence: Common

Update

For known Azure Stack Hub update issues, see Troubleshooting Updates in Azure Stack Hub.

Update to 2102 fails during pre-update checks for AKS/ACR

Applicable: This issue applies to Azure Kubernetes Service (AKS) and Azure Container Registry (ACR) private preview customers who plan to upgrade to 2102 or apply any hotfixes.
Remediation: Uninstall AKS and ACR prior to updating to 2102, or prior to applying any hotfixes after updating to 2102. Restart the update after uninstalling these services.
Occurrence: Any stamp that has ACR or AKS installed will experience this failure.

Portal

Administrative subscriptions

Applicable: This issue applies to all supported releases.
Cause: The two administrative subscription types Metering and Consumption have been disabled and should not be used. If you have resources in them, an alert is generated until those resources are removed.
Remediation: If you have resources running on these two subscriptions, recreate them in user subscriptions.
Occurrence: Common

Networking

Virtual network gateway

Documentation links are Azure-specific

Applicable: This issue applies to all supported releases.
Cause: The documentation links in the overview page of Virtual Network gateway link to Azure-specific documentation instead of Azure Stack Hub. Use the following links for the Azure Stack Hub documentation:

Load balancer

Load Balancer rules

Applicable: This issue applies to all supported releases.
Cause: Updating/changing the load distribution property (session persistence) has no effect and some virtual machines might not participate in the traffic load distribution. For example, if you have 4 backend virtual machines and only 2 clients connecting to the load balancer, and the load distribution is set to client IP, the client sessions will always use the same backend virtual machines. Changing the load distribution property to "none" to distribute the client connections across all the backend virtual machines will have no effect.
Remediation: Recreating the load balancing rule will ensure the selected settings are correctly configured to all backend VMs.
Occurrence: Common

IPv6 button visible on "Add frontend IP address"

Applicable: This issue applies to release 2008 and later.
Cause: IPv6 button is visible on the Add frontend IP address option on a load balancer. These buttons are disabled and cannot be selected.
Occurrence: Common

Backend and frontend ports when floating IP is enabled

Applicable: This issue applies to all supported releases.
Cause: Both the frontend port and backend port need to be the same in the load balancing rule when floating IP is enabled. This behavior is by design.
Occurrence: Common

Health and alerts

Azure Kubernetes Service (AKS) or Azure Container Registry (ACR) resource providers fail in test-azurestack

Applicable: This issue applies to release 2102 and earlier.

Cause: When you run the test-azurestack update readiness command the test triggers the following two warnings:

WARNING: Name resolution of containerservice.aks.azs failed
WARNING: Name resolution of containerregistry.acr.azs failed

Remediation: These warnings are to be expected since you don't have the Azure Kubernetes Service (AKS) or Azure Container Registry (ACR) resource provider installed.
Occurrence: Common

No alerts in Syslog pipeline

Applicable: This issue applies to release 2102.
Cause: The alert module for customers depending on Syslog for alerts has been disabled in this release. For this release, the health and monitoring pipeline was modified to reduce the number of dependencies and services requirements. As a result, the new services will not emit alerts to the Syslog pipeline.
Remediation: None.
Occurrence: Common

Usage

Wrong status on infrastructure backup

Applicable: This issue applies to release 2102.
Cause: The infrastructure backup job can display the wrong status (failed or successful) while the status itself is refreshed. This does not impact the consistency of the backup data, but can cause confusion if an actual failure occurred.
Remediation: The issue will be fixed in the next hotfix for 2102.

Update

For known Azure Stack Hub update issues, see Troubleshooting Updates in Azure Stack Hub.

Update failed to install package Microsoft.AzureStack.Compute.Installer to CA VM

Applicable: This issue applies to all supported releases.
Cause: During update, a process takes a lock on the new content that needs to be copied to CA VM. When the update fails, the lock is released.
Remediation: Resume the update.
Occurrence: Rare

Portal

Administrative subscriptions

Applicable: This issue applies to all supported releases.
Cause: The two administrative subscriptions that were introduced with version 1804 should not be used. The subscription types are Metering subscription, and Consumption subscription.
Remediation: If you have resources running on these two subscriptions, recreate them in user subscriptions.
Occurrence: Common

Networking

Network Security Groups

VM deployment fails due to DenyAllOutbound rule

Applicable: This issue applies to all supported releases.
Cause: An explicit DenyAllOutbound rule to the internet cannot be created in an NSG during VM creation as this will prevent the communication required for the VM deployment to complete. It will also deny the two essential IPs that are required in order to deploy VMs: DHCP IP:169.254.169.254 and DNS IP: 168.63.129.16.
Remediation: Allow outbound traffic to the internet during VM creation, and modify the NSG to block the required traffic after VM creation is complete.
Occurrence: Common

Virtual Network Gateway

Documentation links are Azure-specific

Applicable: This issue applies to all supported releases.
Cause: The documentation links in the overview page of Virtual Network gateway link to Azure-specific documentation instead of Azure Stack Hub. Use the following links for the Azure Stack Hub documentation:

Load Balancer

Load Balancer directing traffic to one backend VM in specific scenarios

Applicable: This issue applies to all supported releases.
Cause: When enabling Session Affinity on a load balancer, the 2 tuple hash utilizes the PA IP (Physical Address IP) instead of the private IPs assigned to the VMs. In scenarios where traffic directed to the load balancer arrives through a VPN, or if all the client VMs (source IPs) reside on the same node and Session Affinity is enabled, all traffic is directed to one backend VM.
Occurrence: Common

IPv6 button visible on "Add frontend IP address"

Applicable: This issue applies to the 2008 release.
Cause: The IPv6 button is visible and enabled when creating the frontend IP configuration of a public load balancer. This is a cosmetic issue on the portal. IPv6 is not supported on Azure Stack Hub.
Occurrence: Common

Backend port and frontend port need to be the same when floating IP is enabled

Applicable: This issue applies to all releases.
Cause: Both the frontend port and backend port need to be the same in the load balancing rule when floating IP is enabled. This behavior is by design.
Occurrence: Common

Compute

Stop or start VM

Stop-Deallocate VM results in MTU configuration removal

Applicable: This issue applies to all supported releases.
Cause: Performing Stop-Deallocate on a VM results in MTU configuration on the VM to be removed. This behavior is inconsistent with Azure.
Occurrence: Common

2005 archived known issues

This article lists known issues in Azure Stack Hub releases. The list is updated as new issues are identified.

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.

Update

For known Azure Stack Hub update issues, see Troubleshooting Updates in Azure Stack Hub.

Update failed to install package Microsoft.AzureStack.Compute.Installer to CA VM

Applicable: This issue applies to all supported releases.
Cause: During update, a process takes a lock on the new content that needs to be copied to CA VM. When the update fails, the lock is released.
Remediation: Resume the update.
Occurrence: Rare

Portal

Administrative subscriptions

Applicable: This issue applies to all supported releases.
Cause: The two administrative subscriptions that were introduced with version 1804 should not be used. The subscription types are Metering subscription, and Consumption subscription.
Remediation: If you have resources running on these two subscriptions, recreate them in user subscriptions.
Occurrence: Common

Networking

Network Security Groups

Cannot delete an NSG if NICs not attached to running VM

Applicable: This issue applies to all supported releases.
Cause: When disassociating an NSG and a NIC that is not attached to a running VM, the update (PUT) operation for that object fails at the network controller layer. The NSG will be updated at the network resource provider layer, but not on the network controller, so the NSG moves to a failed state.
Remediation: Attach the NICs associated to the NSG that needs to be removed with running VMs, and disassociate the NSG or remove all the NICs that were associated with the NSG.
Occurrence: Common

VM deployment fails due to DenyAllOutbound rule

Applicable: This issue applies to all supported releases.
Cause: An explicit DenyAllOutbound rule to the internet cannot be created in an NSG during VM creation as this will prevent the communication required for the VM deployment to complete.
Remediation: Allow outbound traffic to the internet during VM creation, and modify the NSG to block the required traffic after VM creation is complete.
Occurrence: Common

Virtual Network Gateway

Documentation links are Azure-specific

Applicable: This issue applies to all supported releases.
Cause: The documentation links in the overview page of Virtual Network gateway link to Azure-specific documentation instead of Azure Stack Hub. Use the following links for the Azure Stack Hub documentation:

Load Balancer

Load Balancer directing traffic to one backend VM in specific scenarios

Applicable: This issue applies to all supported releases.
Cause: When enabling Session Affinity on a load balancer, the 2 tuple hash utilizes the PA IP (Physical Address IP) instead of the private IPs assigned to the VMs. In scenarios where traffic directed to the load balancer arrives through a VPN, or if all the client VMs (source IPs) reside on the same node and Session Affinity is enabled, all traffic is directed to one backend VM.
Occurrence: Common

Public IP is in a failed state

Applicable: This issue applies to all supported releases.
Cause: The IdleTimeoutInMinutes value for a public IP that is associated to a load balancer cannot be changed. The operation puts the public IP into a failed state.
Remediation: To bring the public IP back into a successful state, change the IdleTimeoutInMinutes value on the load balancer rule that references the public IP back to the original value (the default is 4 minutes).
Occurrence: Common

Compute

Stop-Deallocate VM results in MTU configuration

Applicable: This issue applies to all supported releases.
Cause: Performing Stop-Deallocate on a VM results in MTU configuration on the VM to be removed. This behavior is inconsistent with Azure.
Occurrence: Common

Issues deploying virtual machine scale set with Standard_DS2_v2 size using the portal

Applicable: This issue applies to the 2005 release.
Cause: A portal bug causes scale set creation with Standard_DS2_v2 size to fail.
Remediation: Use PowerShell or CLI to deploy this virtual machine scale set VM size.

Issues using VM extensions in Ubuntu Server 20.04

Applicable: This issue applies to Ubuntu Server 20.04 LTS.
Cause: Some Linux distributions have transitioned to Python 3.8 and removed the legacy /usr/bin/python entrypoint for Python altogether. Linux distribution users who have transitioned to Python 3.x must ensure the legacy /usr/bin/python entry point exists before attempting to deploy those extensions to their VMs. Otherwise, the extension deployment might fail.
Remediation: Follow the resolution steps in Issues using VM extensions in Python 3-enabled Linux Azure Virtual Machines systems but skip step 2, because Azure Stack Hub does not have the Run command functionality.

NVv4 VM size on portal

Applicable: This issue applies to 2002 and later.
Cause: When going through the VM creation experience, you will see the VM size: NV4as_v4. Customers who have the hardware required for the AMD MI25-based Azure Stack Hub GPU preview are able to have a successful VM deployment. All other customers will have a failed VM deployment with this VM size.
Remediation: By design in preparation for the Azure Stack Hub GPU preview.

Consumed compute quota

Applicable: This issue applies to all supported releases.
Cause: When creating a new virtual machine, you may receive an error such as This subscription is at capacity for Total Regional vCPUs on this location. This subscription is using all 50 Total Regional vCPUs available.. This indicates that the quota for total cores available to you has been reached.
Remediation: Ask your operator for an add-on plan with additional quota. Editing the current plan's quota will not work or reflect increased quota.
Occurrence: Rare

VM overview blade does not show correct computer name

Applicable: This issue applies to all releases.
Cause: When viewing details of a VM in the overview blade, the computer name shows as (not available). This is by design for VMs created from specialized disks/disk snapshots, and appears for Marketplace images as well.
Remediation: View the Properties blade under Settings.

Virtual machine scale set

Create failures during patch and update on 4-node Azure Stack Hub environments

Applicable: This issue applies to all supported releases.
Cause: Creating VMs in an availability set of 3 fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a 4-node Azure Stack Hub environment.
Remediation: You can create single VMs in an availability set with 2 fault domains successfully. However, scale set instance creation is still not available during the update process on a 4-node Azure Stack Hub deployment.

Storage

Retention period reverts to 0

Applicable: This issue applies to releases 2002 and 2005.
Cause: If you specify a time period other than 0 in the retention period setting, it reverts to 0 (the default value of this setting) during the 2002 or 2005 update. The 0 days setting takes effect immediately after the update finishes, which causes all existing deleted storage accounts and any upcoming newly deleted storage accounts to be immediately out of retention and marked for periodic garbage collection (which runs hourly).
Remediation: Manually specify the retention period to a correct period. Any storage account that has already been garbage collected before the new retention period is specified, is not recoverable.

Resource providers

SQL/MySQL

Applicable: This issue applies to release 2002.
Cause: If the stamp contains SQL resource provider (RP) version 1.1.33.0 or earlier, upon update of the stamp, the blades for SQL/MySQL do not load.
Remediation: Update the RP to version 1.1.47.0.

App Service

Applicable: This issue applies to release 2002.
Cause: If the stamp contains App Service resource provider (RP) version 1.7 and older, upon update of the stamp, the blades for App Service do not load.
Remediation: Update the RP to version 2002 Q2.

PowerShell

Error thrown when installing the Az modules

Applicable: This issue applies to 2002 and later
Cause: When installing the module, an error is thrown. The error message begins: Register-PacakgeSource : A parameter cannot be found that matches parameter name. 'PackageManagementProvider'. Or the error message may include the following text: PackageManagement\Install-Package : Cannot convert value "2.0.1-preview" to type "System.Version". Error: "Input string was not in a correct format."
Remediation: Run the following cmdlet in the same session:
Install-Module PowershellGet -MinimumVersion 2.3.0 -Force
Close your session and start a new elevated PowerShell session.
Occurrence: Common

When installing Az module falsely throws Admin rights required error

Applicable: This issue applies to 2002 and later
Cause: When installing the module from an elevated prompt, an error is thrown. The error says, Administrator rights required.
Remediation: Close your session and start a new elevated PowerShell session. Make sure there isn't an existing Az. Accounts module loaded in the session.
Occurrence: Common

Known issues for supported versions

Known issues for supported versions of Azure Stack Hub can be found under Overview > Release notes > Known issues

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.

2002 archived known issues

This article lists known issues in Azure Stack Hub releases. The list is updated as new issues are identified.

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.

Update

After applying the 2002 update, an alert for an "Invalid Time Source" may incorrectly appear in the Administrator portal. This false-positive alert can be ignored and will be fixed in an upcoming release.

For known Azure Stack Hub update issues, see Troubleshooting Updates in Azure Stack Hub.

Update failed to install package Microsoft.AzureStack.Compute.Installer to CA VM

Applicable: This issue applies to all supported releases.
Cause: During update, a process takes a lock on the new content that needs to be copied to CA VM. When the update fails, the lock is released.
Remediation: Resume the update.
Occurrence: Rare

Create failures during patch and update on 4-node Azure Stack Hub environments

Applicable: This issue applies to all supported releases.
Cause: Creating VMs in an availability set of 3 fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a 4-node Azure Stack Hub environment.
Remediation: You can create single VMs in an availability set with 2 fault domains successfully. However, scale set instance creation is still not available during the update process on a 4-node Azure Stack Hub deployment.

Portal

Administrative subscriptions

Applicable: This issue applies to all supported releases.
Cause: The two administrative subscriptions that were introduced with version 1804 should not be used. The subscription types are Metering subscription, and Consumption subscription.
Remediation: If you have resources running on these two subscriptions, recreate them in user subscriptions.
Occurrence: Common

Subscription permissions

Applicable: This issue applies to all supported releases.
Cause: You cannot view permissions to your subscription using the Azure Stack Hub portals.
Remediation: Use PowerShell to verify permissions.
Occurrence: Common

Storage account options

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the name of storage accounts is shown as Storage account - blob, file, table, queue; however, file is not supported in Azure Stack Hub.
Occurrence: Common

Create Managed Disk snapshot

Applicable: This issue applies to release 2002.
Cause: In the user portal, when creating a Managed Disk snapshot, the Account type box is empty. When you select the Create button with an empty account type, the snapshot creation fails.
Remediation: Select an account type from the Account type dropdown list, then create the snapshot.
Occurrence: Common

Alert for network interface disconnected

Applicable: This issue applies to 1908 and later.
Cause: When a cable is disconnected from a network adapter, an alert does not show in the administrator portal. This issue is caused because this fault is disabled by default in Windows Server 2019.
Occurrence: Common

Networking

DenyAllOutbound rule cannot be created

Applicable: This issue applies to all supported releases.
Cause: An explicit DenyAllOutbound rule to the internet cannot be created in an NSG during VM creation as this will prevent the communication required for the VM deployment to complete.
Remediation: Allow outbound traffic to the internet during VM creation, and modify the NSG to block the required traffic after VM creation is complete.
Occurrence: Common

ICMP protocol not supported for NSG rules

Applicable: This issue applies to all supported releases.
Cause: When creating an inbound or an outbound network security rule, the Protocol option shows an ICMP option. This is currently not supported on Azure Stack Hub. This issue is fixed and will not appear in the next Azure Stack Hub release.
Occurrence: Common

Cannot delete an NSG if NICs not attached to running VM

Applicable: This issue applies to all supported releases.
Cause: When disassociating an NSG and a NIC that is not attached to a running VM, the update (PUT) operation for that object fails at the network controller layer. The NSG will be updated at the network resource provider layer, but not on the network controller, so the NSG moves to a failed state.
Remediation: Attach the NICs associated to the NSG that needs to be removed with running VMs, and disassociate the NSG or remove all the NICs that were associated with the NSG.
Occurrence: Common

Load Balancer directing traffic to one backend VM in specific scenarios

Applicable: This issue applies to all supported releases.
Cause: When enabling Session Affinity on a load balancer, the 2 tuple hash utilizes the PA IP (Physical Address IP) instead of the private IPs assigned to the VMs. In scenarios where traffic directed to the load balancer arrives through a VPN, or if all the client VMs (source IPs) reside on the same node and Session Affinity is enabled, all traffic is directed to one backend VM.
Occurrence: Common

Network interface

Adding/removing network interface

Applicable: This issue applies to all supported releases.
Cause: A new network interface cannot be added to a VM that is in a running state.
Remediation: Stop the virtual machine before adding or removing a network interface.
Occurrence: Common

Primary network interface

Applicable: This issue applies to all supported releases.
Cause: The primary NIC of a VM cannot be changed. Deleting or detaching the primary NIC results in issues when starting up the VM.
Occurrence: Common

Public IP

Applicable: This issue applies to all supported releases.
Cause: The IdleTimeoutInMinutes value for a public IP that is associated to a load balancer cannot be changed. The operation puts the public IP into a failed state.
Remediation: To bring the public IP back into a successful state, change the IdleTimeoutInMinutes value on the load balancer rule that references the public IP back to the original value (the default value is 4 minutes).
Occurrence: Common

Virtual Network Gateway

Documentation

Applicable: This issue applies to all supported releases.
Cause: The documentation links in the overview page of Virtual Network gateway link to Azure-specific documentation instead of Azure Stack Hub. Use the following links for the Azure Stack Hub documentation:

Compute

Create or delete VM

Can't create a Standard_DS2_v2 VM scale set on portal

Applicable: This issue applies to the 2002 release.
Cause: There is a portal bug that prevents virtual machine scale set creation with the Standard_DS2_v2 VM size. Creating one will error out with: "{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see Troubleshoot common Azure deployment errors for usage details.","details":[{"code":"BadRequest","message":"{\r\n "error": {\r\n "code": "NetworkProfileValidationError",\r\n "message": "Virtual Machine size Standard_DS2_v2 is not in the allowed list of VM sizes for accelerated networking to be enabled on the VM at index 0 for virtual machine scale set /subscriptions/x/resourceGroups/RGVMSS/providers/Microsoft.Compute/virtualMachineScaleSets/vmss. Allowed sizes: ."\r\n }\r\n}"}]}"
Remediation: Create a virtual machine scale set with PowerShell or a Resource Manager template.

NVv4 VM deployment fails

Applicable: This issue applies to release 2002 and later.
Cause: When going through the VM creation experience, you will see the VM size: NV4as_v4. Customers who have the hardware required for the AMD MI25-based Azure Stack Hub GPU preview are able to have a successful VM deployment. All other customers will have a failed VM deployment with this VM size.
Remediation: By design in preparation for the Azure Stack Hub GPU preview.

Failed to update serial output settings for VM

Applicable: This issue applies to all supported releases.
Cause: When creating a new virtual machine (VM), the following error might be displayed: Failed to start virtual machine 'vm-name'. Error: Failed to update serial output settings for VM 'vm-name'. The error occurs if you enable boot diagnostics on a VM, but delete your boot diagnostics storage account.
Remediation: Recreate the storage account with the same name you used previously.
Occurrence: Common

Subscription is at capacity for Total Regional vCPUs

Applicable: This issue applies to all supported releases.
Cause: When creating a new virtual machine, you may receive an error such as This subscription is at capacity for Total Regional vCPUs on this location. This subscription is using all 50 Total Regional vCPUs available.. This indicates that the quota for total cores available to you has been reached.
Remediation: Ask your operator for an add-on plan with additional quota. Editing the current plan's quota will not work or reflect increased quota.
Occurrence: Rare

Start or stop VM

VM diagnostics storage account not found

Applicable: This issue applies to all supported releases.
Cause: When trying to start a stop-deallocated virtual machine,the following error might be displayed: VM diagnostics Storage account 'diagnosticstorageaccount' not found. Ensure storage account is not deleted. The error occurs if you attempt to start a VM with boot diagnostics enabled, but the referenced boot diagnostics storage account is deleted.
Remediation: Recreate the storage account with the same name you used previously.
Occurrence: Common

Configuration and setup

VM overview blade shows incorrect computer name

Applicable: This issue applies to all releases.
Cause: When viewing details of a VM in the overview blade, the computer name shows as (not available). This is by design for VMs created from specialized disks/disk snapshots, and appears for Marketplace images as well.
Remediation: View the Properties blade under Settings.

Storage

Retention period revert to 0

Applicable: This issue applies to release 2002 and 2005.
Cause: If you previously specified a time period other than 0 in retention period setting, it would be reverted back to 0 (the default value of this setting) during 2002 and 2005 update. And the 0 days setting would take effect immediately after update finished, which causes all the existing deleted storage accounts and any upcoming newly deleted storage account being immediately out of retention and marked for periodic garbage collection (which runs hourly).
Remediation: Manually specify the retention period to a proper period. However, any storage account already been garbage collected before the new retention period is specified is not recoverable.

Resource providers

SQL/MySQL

Applicable: This issue applies to release 2002.
Cause: If the stamp contains SQL resource provider (RP) version 1.1.33.0 or earlier, upon update of the stamp, the blades for SQL/MySQL will not load.
Remediation: Update the RP to version 1.1.47.0

App Service

Applicable: This issue applies to release 2002.
Cause: If the stamp contains App Service resource provider (RP) version 1.7 and older, upon update of the stamp, the blades for App Service do not load.
Remediation: Update the RP to version 2020 Q2.

PowerShell

Error thrown when installing the Az modules

Applicable: This issue applies to 2002 and later
Cause: When installing the module, an error is thrown. The error message begins: Register-PacakgeSource : A parameter cannot be found that matches parameter name. 'PackageManagementProvider'. Or the error message may include the following text: PackageManagement\Install-Package : Cannot convert value "2.0.1-preview" to type "System.Version". Error: "Input string was not in a correct format."
Remediation: Run the following cmdlet in the same session:
Install-Module PowershellGet -MinimumVersion 2.3.0 -Force
Close your session and start a new elevated PowerShell session.
Occurrence: Common

When installing Az module falsely throws Admin rights required error

Applicable: This issue applies to 2002 and later
Cause: When installing the module from an elevated prompt, an error is thrown. The error says, Administrator rights required.
Remediation: Close your session and start a new elevated PowerShell session. Make sure there isn't an existing Az. Accounts module loaded in the session.
Occurrence: Common

Marketplace

Storage account creating failure when configuring Auto Backup

Applicable: This issue applies to 2002.
Cause: When configuring the automated backup of SQL VMs with a new storage account, it fails with the error Deployment template validation failed. The template parameter for 'SqlAutobackupStorageAccountKind' is not found.
Remediation: Apply the latest 2002 hotfix.

Auto backup cannot be configured with TLS 1.2 enabled

Applicable: This issue applies to new installations of 2002 and later, or any previous release with TLS 1.2 enabled.
Cause: When configuring the automated backup of SQL VMs with an existing storage account, it fails with the error SQL Server IaaS Agent: The underlying connection was closed: An unexpected error occurred on a send.
Occurrence: Common

1910 archived known issues

This article lists known issues in Azure Stack Hub releases. The list is updated as new issues are identified.

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.

Update

For known Azure Stack Hub update issues, see Troubleshooting Updates in Azure Stack Hub.

Portal

Administrative subscriptions

Applicable: This issue applies to all supported releases.
Cause: The two administrative subscriptions that were introduced with version 1804 should not be used. The subscription types are Metering subscription, and Consumption subscription.
Remediation: If you have resources running on these two subscriptions, recreate them in user subscriptions.
Occurrence: Common

Duplicate Subscription button in Lock blade

Applicable: This issue applies to all supported releases.
Cause: In the administrator portal, the Lock blade for user subscriptions has two buttons that say Subscription.
Occurrence: Common

Subscription permissions

Applicable: This issue applies to all supported releases.
Cause: You cannot view permissions to your subscription using the Azure Stack Hub portals.
Remediation: Use PowerShell to verify permissions.
Occurrence: Common

Storage account settings

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the storage account Configuration blade shows an option to change security transfer type. The feature is currently not supported in Azure Stack Hub.
Occurrence: Common

Upload blob with OAuth error

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when you try to upload a blob using the OAuth(preview) option, the task fails with an error message.
Remediation: Upload the blob using the SAS option.
Occurrence: Common

Upload blob option unsupported

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when you try to upload a blob in the upload blade, there is an option to select Microsoft Entra ID or Key Authentication, however Microsoft Entra ID is not supported in Azure Stack Hub.
Occurrence: Common

Alert for network interface disconnected

Applicable: This issue applies to 1908 and above.
Cause: When a cable is disconnected from a network adapter, an alert does not show in the administrator portal. This issue is caused because this fault is disabled by default in Windows Server 2019.
Occurrence: Common

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when you select a managed disk, with disk type Premium SSD, the drop-down list shows OS Disk. The tooltip next to that option says Certain OS Disk sizes may be available for free with Azure Free Account; however, this is not valid for Azure Stack Hub. In addition, the list includes Free account eligible which is also not valid for Azure Stack Hub.
Occurrence: Common

Delete a storage container

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when a user attempts to delete a storage container, the operation fails when the user does not toggle Override Azure Policy and RBAC Role settings.
Remediation: Ensure that the box is checked for Override Azure Policy and RBAC Role settings.
Occurrence: Common

Refresh button on virtual machines fails

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when you navigate to Virtual Machines and try to refresh using the button at the top, the states fail to update accurately.
Remediation: The status is automatically updated every 5 minutes regardless of whether the refresh button has been clicked or not. Wait 5 minutes and check the status.
Occurrence: Common

Storage account options

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the name of storage accounts is shown as Storage account - blob, file, table, queue; however, file is not supported in Azure Stack Hub.
Occurrence: Common

Storage account configuration

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when you create a storage account and view its Configuration, you cannot save configuration changes, as it results in an AJAX error.
Occurrence: Common

Capacity monitoring in SQL resource provider keeps loading

Applicable: This issue applies to the Azure Stack Hub 1910 update or later, with SQL resource provider version 1.1.33.0 or earlier installed.
Cause: The current version of the SQL resource provider is not compatible with some of the latest portal changes in the 1910 update.
Remediation: Follow the resource provider update process to apply the SQL resource provider hotfix 1.1.47.0 after Azure Stack Hub is upgraded to the 1910 update (SQL RP version 1.1.47.0). For the MySQL resource provider, it is also recommended that you apply the MySQL resource provider hotfix 1.1.47.0 after Azure Stack Hub is upgraded to 1910 update (MySQL RP version 1.1.47.0).
Occurrence: Common

Access Control (IAM)

Applicable: This issue applies to all supported releases.
Cause: The IAM extension is out of date. The Ibiza portal that shipped with Azure Stack Hub introduces a new behavior that causes the RBAC extension to fail if the user is opening the Access Control (IAM) blade for a subscription that is not selected in the global subscription selector (Directory + Subscription in the user portal). The blade displays Loading in a loop, and the user cannot add new roles to the subscription. The Add blade also displays Loading in a loop.
Remediation: Ensure that the subscription is checked in the Directory + Subscription menu. The menu can be accessed from the top of the portal, near the Notifications button, or via the shortcut on the All resources blade that displays Don't see a subscription? Open Directory + Subscription settings. The subscription must be selected in this menu.

SQL resource provider

Applicable: This issue applies to stamps that are running 1908 or earlier.
Cause: When deploying the SQL resource provider (RP) version 1.1.47.0, the portal shows no assets other than those associated with the SQL RP.
Remediation: Delete the RP, upgrade the stamp, and re-deploy the SQL RP.

Activity log blade

Applicable: This issue applies to stamps that are running 1907 or later.
Cause: When accessing the activity log, the portal only shows the first page of entries. Load more results will not load addition entries.
Remediation: Adjust the time range in the filter to review entries that fall after the first page.

Networking

Load balancer

Error: Failed to save load balancer backend pool

Applicable: This issue applies to all supported releases.
Cause: When adding availability set VMs to the backend pool of a load balancer, an error message is displayed on the portal stating Failed to save load balancer backend pool. This is a cosmetic issue on the portal; the functionality is still in place and VMs are successfully added to the backend pool internally.
Occurrence: Common

Network Security Groups

VM deployment fails due to DenyAllOutbound rule

Applicable: This issue applies to all supported releases.
Cause: An explicit DenyAllOutbound rule cannot be created in an NSG as this will prevent all internal communication to infrastructure needed for the VM deployment to complete.
Occurrence: Common

Cannot delete an NSG if NICs not attached to running VM

Applicable: This issue applies to all supported releases.
Cause: When disassociating an NSG and a NIC that is not attached to a running VM, the update (PUT) operation for that object fails at the network controller layer. The NSG will be updated at the network resource provider layer, but not on the network controller, so the NSG moves to a failed state.
Remediation: Attach the NICs associated to the NSG that needs to be removed with running VMs, and disassociate the NSG or remove all the NICs that were associated with the NSG.
Occurrence: Common

Network interface

NIC cannot be added to running VM

Applicable: This issue applies to all supported releases.
Cause: A new network interface cannot be added to a VM that is in a running state.
Remediation: Stop the virtual machine before adding or removing a network interface.
Occurrence: Common

VM startup issues after deleting/detaching primary NIC

Applicable: This issue applies to all supported releases.
Cause: The primary NIC of a VM cannot be changed. Deleting or detaching the primary NIC results in issues when starting up the VM.
Occurrence: Common

Virtual Network Gateway

Virtual Network gateway appears as a Next Hop Type routing option

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when you create a route table, Virtual Network gateway appears as one of the next hop type options; however, this is not supported in Azure Stack Hub.
Occurrence: Common

Virtual Network Gateway blade shows option to use Alerts

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Virtual Network Gateway blade shows an option to use Alerts. This feature is currently not supported in Azure Stack Hub.
Occurrence: Common

Virtual Network Gateway blade shows Active-Active option

Applicable: This issue applies to all supported releases.
Cause: In the user portal, while creating, and in the resource menu of Virtual Network Gateway, you will see an option to enable Active-Active configuration. This feature is currently not supported in Azure Stack Hub.
Occurrence: Common

Connections blade shows VPN troubleshooter feature

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Connections blade displays a feature called VPN Troubleshooter. This feature is currently not supported in Azure Stack Hub.
Occurrence: Common

VPN gateway resource shows VPN Troubleshoot and Metrics feature

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the VPN Troubleshoot feature and Metrics in a VPN gateway resource appears, however this is not supported in Azure Stack Hub.
Occurrence: Common

Documentation links are Azure-specific

Applicable: This issue applies to all supported releases.
Cause: The documentation links in the overview page of Virtual Network gateway link to Azure-specific documentation instead of Azure Stack Hub. Use the following links for the Azure Stack Hub documentation:

Service endpoints not available

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Virtual Network blade shows an option to use Service Endpoints. This feature is currently not supported in Azure Stack Hub.
Occurrence: Common

Compute

VM boot diagnostics

Applicable: This issue applies to all supported releases.
Cause: When creating a new Windows virtual machine (VM), the following error might be displayed: Failed to start virtual machine 'vm-name'. Error: Failed to update serial output settings for VM 'vm-name'. The error occurs if you enable boot diagnostics on a VM, but delete your boot diagnostics storage account.
Remediation: Recreate the storage account with the same name you used previously.
Occurrence: Common

Consumed compute quota

Applicable: This issue applies to all supported releases.
Cause: When creating a new virtual machine, you may receive an error such as This subscription is at capacity for Total Regional vCPUs on this location. This subscription is using all 50 Total Regional vCPUs available.. This indicates that the quota for total cores available to you has been reached.
Remediation: Ask your operator for an add-on plan with additional quota. Editing the current plan's quota will not work or reflect increased quota.
Occurrence: Rare

Privileged Endpoint

Applicable: This issue applies to 1910 and earlier releases.
Cause: Unable to connect to the Privileged Endpoint (ERC VMs) from a computer running a non-English version of Windows.
Remediation: This is a known issue that has been fixed in releases later than 1910. As a workaround you can run the New-PSSession and Enter-PSSession PowerShell cmdlets using the en-US culture; for examples, set the culture using this script: https://resources.oreilly.com/examples/9780596528492/blob/master/Use-Culture.ps1.
Occurrence: Rare

Virtual machine scale set

Create failures during patch and update on 4-node Azure Stack Hub environments

Applicable: This issue applies to all supported releases.
Cause: Creating VMs in an availability set of 3 fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a 4-node Azure Stack Hub environment.
Remediation: You can create single VMs in an availability set with 2 fault domains successfully. However, scale set instance creation is still not available during the update process on a 4-node Azure Stack Hub deployment.

1908 archived known issues

This article lists known issues in releases of Azure Stack. 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 section before applying the update.

Important

If your Azure Stack 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.

1908 update process

Applicable: This issue applies to all supported releases.
Cause: When attempting to install the Azure Stack update, the status for the update might fail and change state to PreparationFailed. This is caused by the update resource provider (URP) being unable to properly transfer the files from the storage container to an internal infrastructure share for processing.
Remediation: Starting with version 1901 (1.1901.0.95), you can work around this issue by clicking Update now again (not Resume). The URP then cleans up the files from the previous attempt, and restarts the download. If the problem persists, we recommend manually uploading the update package by following the Install updates section.
Occurrence: Common

Portal

Administrative subscriptions

Applicable: This issue applies to all supported releases.
Cause: The two administrative subscriptions that were introduced with version 1804 should not be used. The subscription types are Metering subscription, and Consumption subscription.
Remediation: If you have resources running on these two subscriptions, recreate them in user subscriptions.
Occurrence: Common

Subscriptions Properties blade

Applicable: This issue applies to all supported releases.
Cause: In the administrator portal, the Properties blade for subscriptions does not load correctly
Remediation: You can view these subscription properties in the Essentials pane of the Subscriptions Overview blade.
Occurrence: Common

Subscriptions Lock blade

Applicable: This issue applies to all supported releases.
Cause: In the administrator portal, the Lock blade for user subscriptions has two buttons that say subscription.
Occurrence: Common

Subscription permissions

Applicable: This issue applies to all supported releases.
Cause: You cannot view permissions to your subscription using the Azure Stack portals.
Remediation: Use PowerShell to verify permissions.
Occurrence: Common

Storage account settings

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the storage account Configuration blade shows an option to change security transfer type. The feature is currently not supported in Azure Stack.
Occurrence: Common

Upload blob

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when you try to upload a blob using the OAuth(preview) option, the task fails with an error message.
Remediation: Upload the blob using the SAS option.
Occurrence: Common

Networking

Service endpoints

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Virtual Network blade shows an option to use Service Endpoints. This feature is currently not supported in Azure Stack.
Occurrence: Common

Network interface

Applicable: This issue applies to all supported releases.
Cause: A new network interface cannot be added to a VM that is in a running state.
Remediation: Stop the virtual machine before adding/removing a network interface.
Occurrence: Common

Virtual Network Gateway

Local network gateway deletion

Applicable: This issue applies to all supported releases.
Cause: In the user portal, deleting the Local Network Gateway displays the following error message: Cannot delete a Local Network Gateway with an active connection, even though there is no active connection.
Mitigation: The fix for this issue will be released in 1907. A workaround for this issue is to create a new Local Network Gateway with the same IP address, address space and configuration details with a different name. The old LNG can be deleted once the environment has been updated to 1907.
Occurrence: Common

Alerts

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Virtual Network Gateway blade shows an option to use Alerts. This feature is currently not supported in Azure Stack.
Occurrence: Common

Active-Active

Applicable: This issue applies to all supported releases.
Cause: In the user portal, while creating, and in the resource menu of Virtual Network Gateway, you will see an option to enable Active-Active configuration. This feature is currently not supported in Azure Stack.
Occurrence: Common

VPN troubleshooter

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Connections blade shows a feature called VPN Troubleshooter. This feature is currently not supported in Azure Stack.
Occurrence: Common

Documentation

Applicable: This issue applies to all supported releases.
Cause: The documentation links in the overview page of Virtual Network gateway link to Azure-specific documentation instead of Azure Stack. Use the following links for the Azure Stack documentation:

Compute

VM boot diagnostics

Applicable: This issue applies to all supported releases.
Cause: When creating a new Windows virtual machine (VM), the following error may be displayed: Failed to start virtual machine 'vm-name'. Error: Failed to update serial output settings for VM 'vm-name'. The error occurs if you enable boot diagnostics on a VM, but delete your boot diagnostics storage account.
Remediation: Recreate the storage account with the same name you used previously.
Occurrence: Common

Virtual machine scale set

Create failures during patch and update on 4-node Azure Stack environments

Applicable: This issue applies to all supported releases.
Cause: Creating VMs in an availability set of 3 fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a 4-node Azure Stack environment.
Remediation: You can create single VMs in an availability set with 2 fault domains successfully. However, scale set instance creation is still not available during the update process on a 4-node Azure Stack.

Ubuntu SSH access

Applicable: This issue applies to all supported releases.
Cause: An Ubuntu 18.04 VM created with SSH authorization enabled does not allow you to use the SSH keys to sign in.
Remediation: Use VM access for the Linux extension to implement SSH keys after provisioning, or use password-based authentication.
Occurrence: Common

Virtual machine scale set reset password does not work

Applicable: This issue applies to all supported releases.
Cause: A new reset password blade appears in the scale set UI, but Azure Stack does not support resetting password on a scale set yet.
Remediation: None.
Occurrence: Common

Rainy cloud on scale set diagnostics

Applicable: This issue applies to all supported releases.
Cause: The virtual machine scale set overview page shows an empty chart. Clicking on the empty chart opens a "rainy cloud" blade. This is the chart for scale set diagnostic information, such as CPU percentage, and is not a feature supported in the current Azure Stack build.
Remediation: None.
Occurrence: Common

Virtual machine diagnostic settings blade

Applicable: This issue applies to all supported releases.
Cause: The virtual machine diagnostic settings blade has a Sink tab, which asks for an Application Insight Account. This is the result of a new blade and is not yet supported in Azure Stack.
Remediation: None.
Occurrence: Common

1907 archived known issues

This article lists known issues in releases of Azure Stack. 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 section before applying the update.

Important

If your Azure Stack 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.

1907 update process

Applicable: This issue applies to all supported releases.
Cause: When attempting to install the 1907 Azure Stack update, the status for the update might fail and change state to PreparationFailed. This is caused by the update resource provider (URP) being unable to properly transfer the files from the storage container to an internal infrastructure share for processing.
Remediation: Starting with version 1901 (1.1901.0.95), you can work around this issue by clicking Update now again (not Resume). The URP then cleans up the files from the previous attempt, and restarts the download. If the problem persists, we recommend manually uploading the update package by following the Import and install updates section.
Occurrence: Common

Portal

Administrative subscriptions

Applicable: This issue applies to all supported releases.
Cause: The two administrative subscriptions that were introduced with version 1804 should not be used. The subscription types are Metering subscription, and Consumption subscription.
Remediation: If you have resources running on these two subscriptions, recreate them in user subscriptions.
Occurrence: Common

Subscriptions Properties blade

Applicable: This issue applies to all supported releases.
Cause: In the administrator portal, the Properties blade for subscriptions does not load correctly
Remediation: You can view these subscription properties in the Essentials pane of the Subscriptions Overview blade.
Occurrence: Common

Subscription permissions

Applicable: This issue applies to all supported releases.
Cause: You cannot view permissions to your subscription using the Azure Stack portals.
Remediation: Use PowerShell to verify permissions.
Occurrence: Common

Storage account settings

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the storage account Configuration blade shows an option to change security transfer type. The feature is currently not supported in Azure Stack.
Occurrence: Common

Upload blob

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when you try to upload a blob using the OAuth(preview) option, the task fails with an error message.
Remediation: Upload the blob using the SAS option.
Occurrence: Common

Networking

Service endpoints

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Virtual Network blade shows an option to use Service Endpoints. This feature is currently not supported in Azure Stack.
Occurrence: Common

Network interface

Applicable: This issue applies to all supported releases.
Cause: A new network interface cannot be added to a VM that is in a running state.
Remediation: Stop the virtual machine before adding/removing a network interface.
Occurrence: Common

Virtual Network Gateway

Alerts

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Virtual Network Gateway blade shows an option to use Alerts. This feature is currently not supported in Azure Stack.
Occurrence: Common

Active-Active

Applicable: This issue applies to all supported releases.
Cause: In the user portal, while creating, and in the resource menu of Virtual Network Gateway, you will see an option to enable Active-Active configuration. This feature is currently not supported in Azure Stack.
Occurrence: Common

VPN troubleshooter

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Connections blade shows a feature called VPN Troubleshooter. This feature is currently not supported in Azure Stack.
Occurrence: Common

Network Connection Type

Applicable: This issue applies to any 1906 or 1907 environment.
Cause: In the user portal, the AddConnection blade shows an option to use VNet-to-VNet. This feature is currently not supported in Azure Stack.
Occurrence: Common

Documentation

Applicable: This issue applies to all supported releases.
Cause: The documentation links in the overview page of Virtual Network gateway link to Azure-specific documentation instead of Azure Stack. Use the following links for the Azure Stack documentation:

Compute

VM boot diagnostics

Applicable: This issue applies to all supported releases.
Cause: When creating a new Windows virtual machine (VM), the following error may be displayed: Failed to start virtual machine 'vm-name'. Error: Failed to update serial output settings for VM 'vm-name'. The error occurs if you enable boot diagnostics on a VM, but delete your boot diagnostics storage account.
Remediation: Recreate the storage account with the same name you used previously.
Occurrence: Common

Virtual machine scale set

Create failures during patch and update on 4-node Azure Stack environments

Applicable: This issue applies to all supported releases.
Cause: Creating VMs in an availability set of 3 fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a 4-node Azure Stack environment.
Remediation: You can create single VMs in an availability set with 2 fault domains successfully. However, scale set instance creation is still not available during the update process on a 4-node Azure Stack.

Ubuntu SSH access

Applicable: This issue applies to all supported releases.
Cause: An Ubuntu 18.04 VM created with SSH authorization enabled does not allow you to use the SSH keys to sign in.
Remediation: Use VM access for the Linux extension to implement SSH keys after provisioning, or use password-based authentication.
Occurrence: Common

Virtual machine scale set reset password does not work

Applicable: This issue applies to the 1906 and 1907 releases.
Cause: A new reset password blade appears in the scale set UI, but Azure Stack does not support resetting password on a scale set yet.
Remediation: None.
Occurrence: Common

Rainy cloud on scale set diagnostics

Applicable: This issue applies to the 1906 and 1907 releases.
Cause: The virtual machine scale set overview page shows an empty chart. Clicking on the empty chart opens a "rainy cloud" blade. This is the chart for scale set diagnostic information, such as CPU percentage, and is not a feature supported in the current Azure Stack build.
Remediation: None.
Occurrence: Common

Virtual machine diagnostic settings blade

Applicable: This issue applies to the 1906 and 1907 releases.
Cause: The virtual machine diagnostic settings blade has a Sink tab, which asks for an Application Insight Account. This is the result of a new blade and is not yet supported in Azure Stack.
Remediation: None.
Occurrence: Common

1906 archived known issues

This article lists known issues in releases of Azure Stack. 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 section before applying the update.

Important

If your Azure Stack 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.

1906 update process

Applicable: This issue applies to all supported releases.
Cause: When attempting to install the 1906 Azure Stack update, the status for the update might fail and change state to PreparationFailed. This is caused by the update resource provider (URP) being unable to properly transfer the files from the storage container to an internal infrastructure share for processing.
Remediation: Starting with version 1901 (1.1901.0.95), you can work around this issue by clicking Update now again (not Resume). The URP then cleans up the files from the previous attempt, and restarts the download. If the problem persists, we recommend manually uploading the update package by following the Import and install updates section.
Occurrence: Common

Portal

Administrative subscriptions

Applicable: This issue applies to all supported releases.
Cause: The two administrative subscriptions that were introduced with version 1804 should not be used. The subscription types are Metering subscription, and Consumption subscription.
Remediation: If you have resources running on these two subscriptions, recreate them in user subscriptions.
Occurrence: Common

Subscription resources

Applicable: This issue applies to all supported releases.
Cause: Deleting user subscriptions results in orphaned resources.
Remediation: First delete user resources or the entire resource group, and then delete the user subscriptions.
Occurrence: Common

Subscription permissions

Applicable: This issue applies to all supported releases.
Cause: You cannot view permissions to your subscription using the Azure Stack portals.
Remediation: Use PowerShell to verify permissions.
Occurrence: Common

Subscriptions Properties blade

Applicable: This issue applies to all supported releases.
Cause: In the administrator portal, the Properties blade for Subscriptions does not load correctly
Remediation: You can view these subscriptions properties in the Essentials pane of the Subscriptions Overview blade
Occurrence: Common

Storage account settings

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the storage account Configuration blade shows an option to change security transfer type. The feature is currently not supported in Azure Stack.
Occurrence: Common

Upload blob

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when you try to upload a blob using the OAuth(preview) option, the task fails with an error message.
Remediation: Upload the blob using the SAS option.
Occurrence: Common

Update

Applicable: This issue applies to the 1906 release.
Cause: In the operator portal, update status for the hotfix shows an incorrect state for the update. Initial state indicates that the update failed to install, even though it is still in progress.
Remediation: Refresh the portal and the state will update to "in progress."
Occurrence: Intermittent

Networking

Service endpoints

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Virtual Network blade shows an option to use Service Endpoints. This feature is currently not supported in Azure Stack.
Occurrence: Common

Network interface

Applicable: This issue applies to all supported releases.
Cause: A new network interface cannot be added to a VM that is in a running state.
Remediation: Stop the virtual machine before adding/removing a network interface.
Occurrence: Common

Virtual Network Gateway

Alerts

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Virtual Network Gateway blade shows an option to use Alerts. This feature is currently not supported in Azure Stack.
Occurrence: Common

Active-Active

Applicable: This issue applies to all supported releases.
Cause: In the user portal, while creating, and in the resource menu of Virtual Network Gateway, you will see an option to enable Active-Active configuration. This feature is currently not supported in Azure Stack.
Occurrence: Common

VPN troubleshooter

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Connections blade shows a feature called VPN Troubleshooter. This feature is currently not supported in Azure Stack.
Occurrence: Common

Documentation

Applicable: This issue applies to all supported releases.
Cause: The documentation links in the overview page of Virtual Network gateway link to Azure-specific documentation instead of Azure Stack. Please use the following links for the Azure Stack documentation:

Load balancer

Add backend pool

Applicable: This issue applies to all supported releases.
Cause: In the user portal, if you attempt to add a Backend Pool to a Load Balancer, the operation fails with the error message failed to update Load Balancer....
Remediation: Use PowerShell, CLI or a Resource Manager template to associate the backend pool with a load balancer resource.
Occurrence: Common

Create inbound NAT

Applicable: This issue applies to all supported releases.
Cause: In the user portal, if you attempt to create an Inbound NAT Rule for a Load Balancer, the operation fails with the error message Failed to update Load Balancer....
Remediation: Use PowerShell, CLI or a Resource Manager template to associate the backend pool with a load balancer resource.
Occurrence: Common

Compute

VM boot diagnostics

Applicable: This issue applies to all supported releases.
Cause: When creating a new Windows virtual machine (VM), the following error may be displayed: Failed to start virtual machine 'vm-name'. Error: Failed to update serial output settings for VM 'vm-name'. The error occurs if you enable boot diagnostics on a VM, but delete your boot diagnostics storage account.
Remediation: Recreate the storage account with the same name you used previously.
Occurrence: Common

Virtual machine scale set

Create failures during patch and update on 4-node Azure Stack environments

Applicable: This issue applies to all supported releases.
Cause: Creating VMs in an availability set of 3 fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a 4-node Azure Stack environment.
Remediation: You can create single VMs in an availability set with 2 fault domains successfully. However, scale set instance creation is still not available during the update process on a 4-node Azure Stack.

Ubuntu SSH access

Applicable: This issue applies to all supported releases.
Cause: An Ubuntu 18.04 VM created with SSH authorization enabled does not allow you to use the SSH keys to sign in.
Remediation: Use VM access for the Linux extension to implement SSH keys after provisioning, or use password-based authentication.
Occurrence: Common

Virtual machine scale set reset password does not work

Applicable: This issue applies to the 1906 release.
Cause: A new reset password blade appears in the scale set UI, but Azure Stack does not support resetting password on a scale set yet.
Remediation: None.
Occurrence: Common

Rainy cloud on scale set diagnostics

Applicable: This issue applies to the 1906 release.
Cause: The virtual machine scale set overview page shows an empty chart. Clicking on the empty chart opens a "rainy cloud" blade. This is the chart for scale set diagnostic information, such as CPU percentage, and is not a feature supported in the current Azure Stack build.
Remediation: None.
Occurrence: Common

Virtual machine diagnostic settings blade

Applicable: This issue applies to the 1906 release.
Cause: The virtual machine diagnostic settings blade has a Sink tab, which asks for an Application Insight Account. This is the result of a new blade and is not yet supported in Azure Stack.
Remediation: None.
Occurrence: Common

1905 archived known issues

This article lists known issues in the 1905 release of Azure Stack. The list is updated as new issues are identified.

Important

Review this section before applying the update.

Update process

Host node update prerequisite failure

Applicable: This issue applies to the 1905 update.
Cause: When attempting to install the 1905 Azure Stack update, the status for the update might fail due to Host Node Update Prerequisite. This is generally caused by a host node having insufficient free disk space.
Remediation: Contact Azure Stack support to receive assistance clearing disk space on the host node.
Occurrence: Uncommon

Preparation failed

Applicable: This issue applies to all supported releases.
Cause: When attempting to install the 1905 Azure Stack update, the status for the update might fail and change state to PreparationFailed. This is caused by the update resource provider (URP) being unable to properly transfer the files from the storage container to an internal infrastructure share for processing. The 1905 update package is larger than previous update packages which may make this issue more likely to occur.
Remediation: Starting with version 1901 (1.1901.0.95), you can work around this issue by clicking Update now again (not Resume). The URP then cleans up the files from the previous attempt, and restarts the download. If the problem persists, we recommend manually uploading the update package by following the Import and install updates section.
Occurrence: Common

Portal

Subscription resources

Applicable: This issue applies to all supported releases.
Cause: Deleting user subscriptions results in orphaned resources.
Remediation: First delete user resources or the entire resource group, and then delete the user subscriptions.
Occurrence: Common

Subscription permissions

Applicable: This issue applies to all supported releases.
Cause: You cannot view permissions to your subscription using the Azure Stack portals.
Remediation: Use PowerShell to verify permissions.
Occurrence: Common

Marketplace management

Applicable: This issue applies to 1904 and 1905
Cause: The marketplace management screen is not visible when you sign in to the administrator portal.
Remediation: Refresh the browser or go to Settings and select the option Reset to default settings.
Occurrence: Intermittent

Docker extension

Applicable: This issue applies to all supported releases.
Cause: In both the administrator and user portals, if you search for Docker, the item is incorrectly returned. It is not available in Azure Stack. If you try to create it, an error is displayed.
Remediation: No mitigation.
Occurrence: Common

Upload blob

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when you try to upload a blob using the OAuth(preview) option, the task fails with an error message.
Remediation: Upload the blob using the SAS option.
Occurrence: Common

Template

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the template deployment UI does not populate parameters for the template names beginning with "_" (the underscore character).
Remediation: Remove the "_" (underscore character) from the template name.
Occurrence: Common

Networking

Load balancer

Add backend pool

Applicable: This issue applies to all supported releases.
Cause: In the user portal, if you attempt to add a Backend Pool to a Load Balancer, the operation fails with the error message failed to update Load Balancer....
Remediation: Use PowerShell, CLI or a Resource Manager template to associate the backend pool with a load balancer resource.
Occurrence: Common

Create inbound NAT

Applicable: This issue applies to all supported releases.
Cause: In the user portal, if you attempt to create an Inbound NAT Rule for a Load Balancer, the operation fails with the error message Failed to update Load Balancer....
Remediation: Use PowerShell, CLI or a Resource Manager template to associate the backend pool with a load balancer resource.
Occurrence: Common

Create load balancer

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Create Load Balancer window shows an option to create a Standard load balancer SKU. This option is not supported in Azure Stack.
Remediation: Use the Basic load balancer options instead.
Occurrence: Common

Public IP address

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Create Public IP Address window shows an option to create a Standard SKU. The Standard SKU is not supported in Azure Stack.
Remediation: Use the Basic SKU for public IP address.
Occurrence: Common

Compute

VM boot diagnostics

Applicable: This issue applies to all supported releases.
Cause: When creating a new Windows virtual machine (VM), the following error may be displayed: Failed to start virtual machine 'vm-name'. Error: Failed to update serial output settings for VM 'vm-name'. The error occurs if you enable boot diagnostics on a VM, but delete your boot diagnostics storage account.
Remediation: Recreate the storage account with the same name you used previously.
Occurrence: Common

VM resize

Applicable: This issue applies to the 1905 release.
Cause: Unable to successfully resize a managed disk VM. Attempting to resize the VM generates an error with "code": "InternalOperationError", "message": "An internal error occurred in the operation."
Remediation: We are working to remediate this in the next release. Currently, you must recreate the VM with the new VM size.
Occurrence: Common

Virtual machine scale set

Remove scale set

Applicable: This issue applies to all supported releases.
Cause: You cannot remove a scale set from the Virtual machine scale sets blade.
Remediation: Select the scale set that you want to remove, then click the Delete button from the Overview pane.
Occurrence: Common

Create failures during patch and update on 4-node Azure Stack environments

Applicable: This issue applies to all supported releases.
Cause: Creating VMs in an availability set of 3 fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a 4-node Azure Stack environment.
Remediation: You can create single VMs in an availability set with 2 fault domains successfully. However, scale set instance creation is still not available during the update process on a 4-node Azure Stack.

Scale set instance view blade doesn't load

Applicable: This issue applies to 1904 and 1905 release.
Cause: The instance view blade of a virtual machine scale set located at Azure Stack portal -> Dashboard -> Virtual machine scale sets -> AnyScaleSet - Instances -> AnyScaleSetInstance fails to load, and displays a crying cloud image.
Remediation: There is currently no remediation and we are working on a fix. Until then, please use the CLI command az vmss get-instance-view to get the instance view of a scale set.

Ubuntu SSH access

Applicable: This issue applies to all supported releases.
Cause: An Ubuntu 18.04 VM created with SSH authorization enabled does not allow you to use the SSH keys to sign in.
Remediation: Use VM access for the Linux extension to implement SSH keys after provisioning, or use password-based authentication.
Occurrence: Common

Next steps

1904 archived known issues

This article lists known issues in the 1904 release of Azure Stack. The list is updated as new issues are identified.

Important

Review this section before applying the update.

Update process

Applicable: This issue applies to all supported releases.
Cause: When attempting to install an Azure Stack update, the status for the update might fail and change state to PreparationFailed. This is caused by the update resource provider (URP) being unable to properly transfer the files from the storage container to an internal infrastructure share for processing.
Remediation: Starting with version 1901 (1.1901.0.95), you can work around this issue by clicking Update now again (not Resume). The URP then cleans up the files from the previous attempt, and starts the download again.
Occurrence: Common

Portal

Administrative subscriptions

Applicable: This issue applies to all supported releases.
Cause: The two administrative subscriptions that were introduced with version 1804 should not be used. The subscription types are Metering subscription, and Consumption subscription.
Remediation: If you have resources running on these two subscriptions, recreate them in user subscriptions.
Occurrence: Common

Subscription resources

Applicable: This issue applies to all supported releases.
Cause: Deleting user subscriptions results in orphaned resources.
Remediation: First delete user resources or the entire resource group, and then delete the user subscriptions.
Occurrence: Common

Subscription permissions

Applicable: This issue applies to all supported releases.
Cause: You cannot view permissions to your subscription using the Azure Stack portals.
Remediation: Use PowerShell to verify permissions.
Occurrence: Common

Docker extension

Applicable: This issue applies to all supported releases.
Cause: In both the administrator and user portals, if you search for Docker, the item is incorrectly returned. It is not available in Azure Stack. If you try to create it, an error is displayed.
Remediation: No mitigation.
Occurrence: Common

Marketplace management

Applicable: This is a new issue with release 1904.
Cause: The marketplace management screen is not visible when you sign in to the administrator portal.
Remediation: Refresh the browser.
Occurrence: Intermittent

Marketplace management

Applicable: This issue applies to 1904.
Cause: When you filter results in the Add from Azure blade in the Marketplace management tab in the administrator portal, you may see incorrect filtered results.
Remediation: Sort results by the Name column and the results will be corrected.
Occurrence: Intermittent

Marketplace management

Applicable: This issue applies to 1904.
Cause: When you filter results in Marketplace management in the administrator portal, you will see duplicated publisher names under the publisher drop-down.
Remediation: Select all the duplicates to have the correct list of all the Marketplace products that are available under that publisher.
Occurrence: Intermittent

Docker extension

Applicable: This issue applies to all supported releases.
Cause: In both the administrator and user portals, if you search for Docker, the item is incorrectly returned. It is not available in Azure Stack. If you try to create it, an error is displayed.
Remediation: No mitigation.
Occurrence: Common

Upload blob

Applicable: This issue applies to all supported releases.
Cause: In the user portal, when you try to upload a blob using the OAuth(preview) option, the task fails with an error message.
Remediation: Upload the blob using the SAS option.
Occurrence: Common

Template

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the template deployment UI does not populate parameters for the template names beginning with "_" (the underscore character).
Remediation: Remove the "_" (underscore character) from the template name.
Occurrence: Common

Networking

Load balancer

Add backend pool

Applicable: This issue applies to all supported releases.
Cause: In the user portal, if you attempt to add a Backend Pool to a Load Balancer, the operation fails with the error message Failed to update Load Balancer....
Remediation: Use PowerShell, CLI, or an Azure Resource Manager template to associate the backend pool with a load balancer resource.
Occurrence: Common

Create inbound NAT

Applicable: This issue applies to all supported releases.
Cause: In the user portal, if you attempt to create an Inbound NAT Rule for a Load Balancer, the operation fails with the error message Failed to update Load Balancer....
Remediation: Use PowerShell, CLI, or an Azure Resource Manager template to associate the backend pool with a load balancer resource.
Occurrence: Common

Create load balancer

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Create Load Balancer window shows an option to create a Standard load balancer SKU. This option is not supported in Azure Stack.
Remediation: Use the Basic load balancer options instead.
Occurrence: Common

Public IP address

Applicable: This issue applies to all supported releases.
Cause: In the user portal, the Create Public IP Address window shows an option to create a Standard SKU. The Standard SKU is not supported in Azure Stack.
Remediation: Use the Basic SKU instead for public IP addresses.
Occurrence: Common

Compute

VM boot diagnostics

Applicable: This issue applies to all supported releases.
Cause: When creating a new Windows Virtual Machine (VM), the following error may be displayed: Failed to start virtual machine 'vm-name'. Error: Failed to update serial output settings for VM 'vm-name'. The error occurs if you enable boot diagnostics on a VM, but delete your boot diagnostics storage account.
Remediation: Recreate the storage account with the same name you used previously.
Occurrence: Common

Virtual machine scale set

Remove scale set

Applicable: This issue applies to all supported releases.
Cause: You cannot remove a scale set from the Virtual Machine Scale Sets blade.
Remediation: Select the scale set that you want to remove, then click the Delete button from the Overview pane.
Occurrence: Common

Create failures during patch and update on 4-node Azure Stack environments

Applicable: This issue applies to all supported releases.
Cause: Creating VMs in an availability set of 3 fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a 4-node Azure Stack environment.
Remediation: You can create single VMs in an availability set with 2 fault domains successfully. However, scale set instance creation is still not available during the update process on a 4-node Azure Stack.

Ubuntu SSH access

Applicable: This issue applies to all supported releases.
Cause: An Ubuntu 18.04 VM created with SSH authorization enabled does not allow you to use the SSH keys to sign in.
Remediation: Use VM access for the Linux extension to implement SSH keys after provisioning, or use password-based authentication.
Occurrence: Common

Compute host agent alert

Applicable: This is a new issue with release 1904.

Cause: A Compute host agent warning appears after restarting a node in the scale unit. The restart changes the default startup setting for the compute host agent service. This alert looks similar to the following example:

NAME  
Compute Host Agent is not responding to calls.
SEVERITY  
Warning
STATE  
Active
CREATED TIME  
5/16/2019, 10:08:23 AM
UPDATED TIME  
5/22/2019, 12:27:27 PM
COMPONENT  
M#####-NODE02
DESCRIPTION  
Could not communicate with the Compute Host Agent running on node: M#####-NODE02
REMEDIATION  
Please disable Compute Host Agent feature flag and collect logs for further diagnosis.

Remediation:
- This alert can be ignored. The agent not responding does not have any impact on operator and user operations or user applications. The alert will reappear after 24 hours if it is closed manually.
- The issue is fixed in the latest Azure Stack hotfix for 1904.
Occurrence: Common

Virtual machine scale set instance view

Applicable: This issue applies to the 1904 and 1905 releases.
Cause: The instance view blade of a scale set located on the Azure Stack portal, in Dashboard > Virtual machine scale sets > AnyScaleSet - Instances > AnyScaleSetInstance fails to load.
Remediation: There is currently no remediation and we are working on a fix. Until then, please use the CLI cmdlet az vmss get-instance-view to get the instance view of a virtual machine scale set.

User image service

Applicable: This issue applies to all supported releases.
Cause: Failed user image creation will put the user image service into a bad state. User image creation and deletion operations will start to fail. User image deletion may fail with error: "Error: An internal disk management error occurred."
Remediation: No mitigation. Open a support ticket with Microsoft.

Storage

Applicable: This issue applies to all supported releases.
Cause: ConvertTo-AzureRmVMManagedDisk is not supported in Azure Stack and results in creating a disk with $null ID. This prevents you from performing operations on the VM, such as start and stop. The disk does not appear in the UI, nor does it appear via the API. The VM at that point cannot be repaired and must be deleted.
Remediation: To convert your disks correctly, follow the convert to managed disks guide.

App Service

Tenants must register the storage resource provider before creating their first Azure Function in the subscription.
Some tenant portal user experiences are broken due to an incompatibility with the portal framework in 1903; principally, the UX for deployment slots, testing in production and site extensions. To work around this issue, use the Azure App Service PowerShell module or the Azure CLI. The portal experience will be restored by upgrading your deployment of Azure App Service on Azure Stack to 1.6 (Update 6).

Share via

Azure Stack Hub archived known issues

App Service

Incorrect rotation status after secret rotation of resource provider certificates

Portal

Incorrect reporting of node CPU cores in the admin portal

App Service

Incorrect rotation status after secret rotation of resource provider certificates

Alerts

Geographical region not provided

Encryption recovery keys retrieval warning

Portal

Possibility of portal errors during update

Public IP and Load Balancer blades display a banner that recommends upgrading from Basic to Standard SKU

Menu items not displayed when clicking on disk instance on VM overview blade

Datacenter integration

Graph configuration fails

Update

Update to 2108 will not proceed if there are AKS clusters or ACR registries created and the private previews of AKS and ACR services are installed

Networking

Load Balancer

Load Balancer rules

Cannot create a Virtual Machine Scale Set with a data disk attached

Create disk snapshot can fail

Portal

Container registries

Metrics unavailable for container registries in the user portal

Container Registry operator experience prompting to install although installation already complete

Administrative subscriptions

Create DNS blade results in portal crashing

Portal shows "Unidentified User" instead of user email

Public IP and Load Balancer blades display a banner that recommends upgrading from Basic to Standard SKU

Menu items not displayed when clicking on disk instance on VM overview blade

Data plane clusters are in an unhealthy state with all nodes in warning state

Data plane clusters' health isn't getting updated in admin portal or scale-out of clusters results in access denied

Azure Stack Hub backup fails

Azure Kubernetes Service (AKS)

Applications deployed to AKS clusters fail to access persistent volumes

Update

Update to 2102 fails during pre-update checks for AKS/ACR

Portal

Administrative subscriptions

Networking

Virtual network gateway

Documentation links are Azure-specific

Load balancer

Load Balancer rules

IPv6 button visible on "Add frontend IP address"

Backend and frontend ports when floating IP is enabled

Health and alerts

Azure Kubernetes Service (AKS) or Azure Container Registry (ACR) resource providers fail in test-azurestack

No alerts in Syslog pipeline

Usage

Wrong status on infrastructure backup

Update

Update failed to install package Microsoft.AzureStack.Compute.Installer to CA VM

Portal

Administrative subscriptions

Networking

Network Security Groups

VM deployment fails due to DenyAllOutbound rule

Virtual Network Gateway

Documentation links are Azure-specific

Load Balancer

Load Balancer directing traffic to one backend VM in specific scenarios

IPv6 button visible on "Add frontend IP address"

Backend port and frontend port need to be the same when floating IP is enabled

Compute

Stop or start VM

Stop-Deallocate VM results in MTU configuration removal

2005 archived known issues

Update

Update failed to install package Microsoft.AzureStack.Compute.Installer to CA VM

Portal

Administrative subscriptions

Networking

Network Security Groups

Cannot delete an NSG if NICs not attached to running VM

VM deployment fails due to DenyAllOutbound rule

Virtual Network Gateway