Azure Stack 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 butons 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

Network Security Groups

  • 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

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

  • Applicable: This issue applies to all supported releases.

  • Cause: The primary NIC of a VM cannot be changed. Deleting/Detaching the primary NIC will result in issues starting up the VM.

  • 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

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 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

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 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

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 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

CentOS

  • Applicable: This issue applies to all supported releases.
  • Cause: The virtual machine scale set creation experience provides CentOS-based 7.2 as an option for deployment. CentOS 7.2 is not available on Azure Stack Marketplace which will cause deployment failures calling out that the image is not found.
  • Remediation: Select another operating system for your deployment, or use an Azure Resource Manager template specifying another CentOS image that has been downloaded prior to deployment from the marketplace by the operator.
  • Occurrence: Common

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

Archive

To access archived known issues for an older version, use the version selector dropdown above the table of contents on the left, and select the version you want to see.

Next steps

1904 archived known issues

1903 archived known issues

1902 archived known issues

1901 archived known issues

1811 archived known issues

1809 archived known issues

1808 archived known issues

1807 archived known issues

1805 archived known issues

1804 archived known issues

1803 archived known issues

1802 archived known issues

You can access older versions of Azure Stack known issues on the TechNet Gallery. These archived documents are provided for reference purposes only and do not imply support for these versions. For information about Azure Stack support, see Azure Stack servicing policy. For further assistance, contact Microsoft Customer Support Services.