Skip to content

Commit 851df88

Browse files
author
Mitchell Bifeld
committed
Updated CLI link
1 parent 52e6930 commit 851df88

File tree

3 files changed

+3
-7
lines changed

3 files changed

+3
-7
lines changed

support/azure/virtual-machines/linux/serial-console-linux.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ By default, all subscriptions have serial console access enabled. You can disabl
8989
### Use Serial Console with custom boot diagnostics storage account firewall enabled
9090

9191
> [!WARNING]
92-
> There's a known issue where Azure Serial Console might fail to connect when a custom boot diagnostics storage account has firewall restrictions when using the [az serial-console](../../../../cli/azure/serial-console) command. To avoid connectivity issues, use Serial Console in the Azure Portal.
92+
> There's a known issue where Azure Serial Console might fail to connect when a custom boot diagnostics storage account has firewall restrictions when using the [az serial-console](/cli/azure/serial-console) command. To avoid connectivity issues, use Serial Console in the Azure Portal.
9393
9494
> [!IMPORTANT]
9595
> By the end of 2025, Azure Serial Console will no longer utilize boot diagnostics storage accounts for establishing a connection. No customer action is required for this change. This change doesn't affect serial logs or screenshots.

support/azure/virtual-machines/windows/serial-console-errors.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,7 @@ tags: azure-resource-manager
99
ms.service: azure-virtual-machines
1010
ms.tgt_pltfrm: vm
1111
ms.workload: infrastructure-services
12-
<<<<<<< HEAD
1312
ms.date: 09/10/2025
14-
=======
15-
ms.date: 8/26/2025
16-
>>>>>>> a1f209e9d7d710950ac720a947cd004e0f6cc1d6
1713
ms.author: jarrettr
1814
ms.custom: sap:VM Admin - Windows (Guest OS)
1915
---
@@ -36,7 +32,7 @@ Error | Mitigation
3632
"Azure Serial Console requires boot diagnostics to be enabled. Click here to configure boot diagnostics for your virtual machine." | Make sure that the virtual machine (VM) or VM scale set has [boot diagnostics](boot-diagnostics.md) enabled. If you use the Serial Console on a VM scale set instance, make sure that your instance has the latest model.
3733
"Azure Serial Console requires a virtual machine to be running. Use the Start button to start your virtual machine." | The VM Scale Sets instance must be in a started state to access the Serial Console (your VM must not be stopped or deallocated). Make sure that your VM or VM Scale Sets instance is running, and then try again.
3834
"Azure Serial Console is not enabled for this subscription, contact your subscription administrator to enable." | The Azure Serial Console can be disabled at a subscription level. If you're a subscription administrator, you can [enable and disable the Azure Serial Console](./serial-console-enable-disable.md). If you aren't a subscription administrator, contact your subscription administrator for the next steps.
39-
A "Forbidden" response was encountered when accessing this VM's boot diagnostic storage account. | There's a known issue where Azure Serial Console might fail to connect when a custom boot diagnostics storage account has firewall restrictions when using the [az serial-console](../../../../cli/azure/serial-console) command. To avoid connectivity issues, use Serial Console in the Azure Portal.
35+
A "Forbidden" response was encountered when accessing this VM's boot diagnostic storage account. | There's a known issue where Azure Serial Console might fail to connect when a custom boot diagnostics storage account has firewall restrictions when using the [az serial-console](/cli/azure/serial-console) command. To avoid connectivity issues, use Serial Console in the Azure Portal.
4036
You don't have the required permissions to use this VM with the serial console. Ensure you have at least Virtual Machine Contributor role permissions.| Serial console access requires that you have contributor level access on your VM or VM scale set. For more information, see the [Azure Serial Console](serial-console-overview.md) overview page.
4137
The storage account '' used for boot diagnostics on this VM couldn't be found. Verify that boot diagnostics is enabled for this VM, this storage account hasn't been deleted, and you have access to this storage account. | Double check that you didn't delete the boot diagnostics storage account for your VM or VM scale set.
4238
The serial console connection to the VM encountered an error: 'Bad Request' (400) | This error can occur if your boot diagnostics URI is incorrect. For example, "http://" instead of "https://" is used. To fix the URI, run the following command: `az vm boot-diagnostics enable --name vmName --resource-group rgName --storage https://<storageAccountUri>.blob.core.windows.net/`.

support/azure/virtual-machines/windows/serial-console-windows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -142,7 +142,7 @@ By default, all subscriptions have serial console access enabled. You can disabl
142142
### Use Serial Console with custom boot diagnostics storage account firewall enabled
143143

144144
> [!WARNING]
145-
> There's a known issue where Azure Serial Console might fail to connect when a custom boot diagnostics storage account has firewall restrictions when using the [az serial-console](../../../../cli/azure/serial-console) command. To avoid connectivity issues, use Serial Console in the Azure Portal.
145+
> There's a known issue where Azure Serial Console might fail to connect when a custom boot diagnostics storage account has firewall restrictions when using the [az serial-console](/cli/azure/serial-console) command. To avoid connectivity issues, use Serial Console in the Azure Portal.
146146
147147
> [!IMPORTANT]
148148
> By the end of 2025, Azure Serial Console will no longer utilize boot diagnostics storage accounts for establishing a connection. No customer action is required for this change. This change doesn't affect serial logs or screenshots.

0 commit comments

Comments
 (0)