Azure Serial Console for Linux
The Serial Console in the Azure portal provides access to a text-based console for Linux virtual machines (VMs) and virtual machine scale set instances. This serial connection connects to the ttys0 serial port of the VM or virtual machine scale set instance, providing access to it independent of the network or operating system state. The serial console can only be accessed by using the Azure portal and is allowed only for those users who have an access role of Contributor or higher to the VM or virtual machine scale set.
Serial Console works in the same manner for VMs and virtual machine scale set instances. In this doc, all mentions to VMs will implicitly include virtual machine scale set instances unless otherwise stated.
Serial Console is generally available in global Azure regions and in public preview in Azure Government. It is not yet available in the Azure China cloud.
For Serial Console documentation for Windows, see Serial Console for Windows.
Serial Console is compatible with a managed boot diagnostics storage account.
Your VM or virtual machine scale set instance must use the resource management deployment model. Classic deployments aren't supported.
Your VM or virtual machine scale set instance must have a password-based user. You can create one with the reset password function of the VM access extension. Select Reset password from the Help section.
Your VM or virtual machine scale set instance must have boot diagnostics enabled.
For settings specific to Linux distributions, see Serial console Linux distribution availability.
Your VM or virtual machine scale set instance must be configured for serial output on
ttys0. This is the default for Azure images, but you will want to double check this on custom images. Details below.
The serial console requires a local user with a configured password. VMs or virtual machine scale sets configured only with an SSH public key won't be able to sign in to the serial console. To create a local user with a password, use the VMAccess Extension, which is available in the portal by selecting Reset password in the Azure portal, and create a local user with a password. You can also reset the administrator password in your account by using GRUB to boot into single user mode.
Serial Console Linux distribution availability
For the serial console to function properly, the guest operating system must be configured to read and write console messages to the serial port. Most Endorsed Azure Linux distributions have the serial console configured by default. Selecting Serial console in the Help section of the Azure portal provides access to the serial console.
If you are not seeing anything in the serial console, make sure that boot diagnostics is enabled on your VM. Hitting Enter will often fix issues where nothing is showing up in the serial console.
|Distribution||Serial console access|
|Red Hat Enterprise Linux||Serial console access enabled by default.|
|CentOS||Serial console access enabled by default.|
|Debian||Serial console access enabled by default.|
|Ubuntu||Serial console access enabled by default.|
|CoreOS||Serial console access enabled by default.|
|SUSE||Newer SLES images available on Azure have serial console access enabled by default. If you're using older versions (10 or earlier) of SLES on Azure, see the KB article to enable serial console.|
|Oracle Linux||Serial console access enabled by default.|
Custom Linux images
To enable the serial console for your custom Linux VM image, enable console access in the file /etc/inittab to run a terminal on
ttyS0. For example:
S0:12345:respawn:/sbin/agetty -L 115200 console vt102. You may also need to spawn a getty on ttyS0. This can be done with
systemctl start serial-getty@ttyS0.service.
You will also want to add ttys0 as the destination for serial output. For more information on configuring a custom image to work with the serial console, see the general system requirements at Create and upload a Linux VHD in Azure.
If you're building a custom kernel, consider enabling these kernel flags:
CONFIG_MAGIC_SYSRQ_SERIAL=y. The configuration file is typically located in the /boot/ path.
Common scenarios for accessing the Serial Console
|Scenario||Actions in the Serial Console|
|Broken FSTAB file||Press the Enter key to continue and use a text editor to fix the FSTAB file. You might need to be in single user mode to do so. For more information, see the serial console section of How to fix fstab issues and Use serial console to access GRUB and single user mode.|
|Incorrect firewall rules||If you have configured iptables to block SSH connectivity, you can use serial console to interact with your VM without needing SSH. More details can be found at the iptables man page.
Similarly, if your firewalld is blocking SSH access, you can access the VM through serial console and reconfigure firewalld. More details can be found in the firewalld documentation.
|Filesystem corruption/check||Please see the serial console section of Azure Linux VM cannot start because of file system errors for more details on troubleshooting corrupted file systems using the serial console.|
|SSH configuration issues||Access the serial console and change the settings. Serial console can be used regardless of the SSH configuration of a VM as it does not require the VM to have network connectivity to work. A troubleshooting guide is available at Troubleshoot SSH connections to an Azure Linux VM that fails, errors out, or is refused. More details are available at Detailed SSH troubleshooting steps for issues connecting to a Linux VM in Azure|
|Interacting with bootloader||Restart your VM from within the serial console blade to access GRUB on your Linux VM. For more details and distro-specific information, see Use serial console to access GRUB and single user mode.|
Disable the Serial Console
By default, all subscriptions have serial console access enabled. You can disable the serial console at either the subscription level or VM/virtual machine scale set level. For detailed instructions, visit Enable and disable the Azure Serial Console.
Serial Console security
Use Serial Console with custom boot diagnostics storage account firewall enabled
Serial Console uses the storage account configured for boot diagnostics in its connection workflow. When a firewall is enabled on this storage account, the Serial Console service IPs must be added as exclusions. To do this, follow these steps:
Navigate to the settings of the custom boot diagnostics storage account firewall you have enabled.
To determine which storage account is enabled for your VM, from the Support + troubleshooting section, select Boot diagnostics > Settings.
Add Serial Console service IPs as firewall exclusions based on the VM's geography.
The following table lists the IPs that need to be permitted as firewall exclusions based on the region or geography where the VM is located. This is a subset of the complete list of Serial Console IP addresses under processing for inclusion in service tags.
IP Address Regions Geography 188.8.131.52 East Asia, Southeast Asia AsiaPacific 184.108.40.206 East Asia, Southeast Asia AsiaPacific 220.127.116.11 Australia Central, Australia Central 2, Australia East, Australia Southeast Australia 18.104.22.168 Australia Central, Australia Central 2, Australia East, Australia Southeast Australia 22.214.171.124 Brazil South, Brazil Southeast Brazil 126.96.36.199 Brazil South, Brazil Southeast Brazil 188.8.131.52 Canada Central, Canada East Canada 184.108.40.206 Canada Central, Canada East Canada 220.127.116.11 Canary (EUAP) 18.104.22.168 Canary (EUAP) 22.214.171.124 North Europe, West Europe Europe 126.96.36.199 North Europe, West Europe Europe 188.8.131.52 France Central, France South France 184.108.40.206 France Central, France South France 220.127.116.11 Germany North, Germany West Central Germany 18.104.22.168 Germany North, Germany West Central Germany 22.214.171.124 Central India, South India, West India India 126.96.36.199 Central India, South India, West India India 188.8.131.52 Japan East, Japan West Japan 184.108.40.206 Japan East, Japan West Japan 220.127.116.11 Korea Central, Korea South Korea 18.104.22.168 Korea Central, Korea South Korea 22.214.171.124 Norway West, Norway East Norway 126.96.36.199 Norway West, Norway East Norway 188.8.131.52 Switzerland North, Switzerland West Switzerland 184.108.40.206 Switzerland North, Switzerland West Switzerland 220.127.116.11 UAE Central, UAE North UAE 18.104.22.168 UAE Central, UAE North UAE 22.214.171.124 UK South, UK West UnitedKingdom 126.96.36.199 UK South, UK West UnitedKingdom 188.8.131.52 Sweden Central, Sweden South Sweden 184.108.40.206 Sweden Central, Sweden South Sweden 220.127.116.11 Central US, East US 2, East US, North Central US, South Central US, West US 2, West US 3, West Central US, West US UnitedStates 18.104.22.168 Central US, East US 2, East US, North Central US, South Central US, West US 2, West US 3, West Central US, West US UnitedStates 22.214.171.124 Central US, East US 2, East US, North Central US, South Central US, West US 2, West US 3, West Central US, West US UnitedStates 126.96.36.199 United States 188.8.131.52 All US Government cloud regions UsGov 184.108.40.206 All US Government cloud regions UsGov
- The IPs that need to be permitted are specific to the region where the VM is located. For example, a virtual machine deployed in the North Europe region needs to add the following IP exclusions to the storage account firewall for the Europe geography: 220.127.116.11 and 18.104.22.168. View the table above to find the correct IPs for your region and geography.
- In the current serial console operation, the web socket is opened to an endpoint like
<region>.gateway.serialconsole.azure.com. Ensure the endpoint
serialconsole.azure.comis allowed for browser clients in your organization. In the US Government (Fairfax) cloud, the endpoint suffix is
For more information about how to add IPs to the storage account firewall, see Configure Azure Storage firewalls and virtual networks: Managing IP network rules.
After the IP addresses are successfully added to the storage account firewall, retry the Serial Console connection to the VM. If you still have connection problems, verify that the correct IP addresses are excluded from the storage account firewall for the region of the VM.
Access to the serial console is limited to users who have an access role of Virtual Machine Contributor or higher to the virtual machine. If your Azure Active Directory tenant requires multi-factor authentication (MFA), then access to the serial console will also need MFA because the serial console's access is through the Azure portal.
All data that is sent back and forth is encrypted in transit with TLS 1.2 or a later version.
Data storage and encryption
Azure Serial Console doesn't review, inspect, or store any data that's transmitted in and out of the virtual machine serial port. Therefore, there's no data to encrypt at rest.
To ensure that any in-memory data that's paged to disks by virtual machines running Azure Serial Console is encrypted, use the host-based encryption. The host-based encryption is enabled by default for all Azure Serial Console connections.
The Azure portal or Azure CLI act as remote terminals to the virtual machine serial port. As these terminals can't directly connect to the servers which host the virtual machine over the network, an intermediate service gateway is used to proxy the terminal traffic. Azure Serial Console doesn't store or process this customer data. The intermediate service gateway that transfers the data will reside in the geography of the virtual machine.
All access to the serial console is currently logged in the boot diagnostics logs of the virtual machine. Access to these logs is owned and controlled by the Azure virtual machine administrator.
No access passwords for the console are logged. However, if commands run within the console contain or output passwords, secrets, user names, or any other form of personally identifiable information (PII), those will be written to the VM boot diagnostics logs. They will be written along with all other visible text as part of the implementation of the serial console's scroll back function. These logs are circular, and only individuals with read permissions to the diagnostics storage account have access to them. If you are inputting any data or commands that contain secrets or PII, we would recommend using SSH unless the serial console is absolutely necessary.
If a user is connected to the serial console and another user successfully requests access to that same virtual machine, the first user will be disconnected and the second user connected to the same session.
This means that a user who's disconnected won't be logged out. The ability to enforce a logout upon disconnect (by using SIGHUP or a similar mechanism) is still on the roadmap. For Windows, there is an automatic timeout enabled in Special Administrative Console (SAC); however, for Linux, you can configure the terminal timeout setting. To do so, add
export TMOUT=600 in your .bash_profile or .profile file for the user you use to sign in to the console. This setting will time out the session after 10 minutes.
Accessibility is a key focus for the Azure Serial Console. To that end, we've ensured that the serial console is fully accessible.
Use the Tab key on your keyboard to navigate to the serial console interface from the Azure portal. Your location will be highlighted on the screen. To leave the focus of the serial console window, press Ctrl+F6 on your keyboard.
Use Serial Console with a screen reader
The serial console has screen reader support built in. Navigating around with a screen reader turned on will allow the alt text for the currently selected button to be read aloud by the screen reader.
We're aware of some issues with the serial console and the VM's operating system. Here's a list of these issues and steps for mitigation for Linux VMs. These issues and mitigations apply to both VMs and virtual machine scale set instances. If these don't match the error you're seeing, see the common serial console service errors at Common Serial Console errors.
|Pressing Enter after the connection banner does not cause a sign-in prompt to be displayed.||GRUB may not be configured correctly. Run the following commands:
|Serial console text only takes up a portion of the screen size (often after using a text editor).||Serial consoles do not support negotiating about window size (RFC 1073), which means that there will be no SIGWINCH signal sent to update screen size, and the VM will have no knowledge of your terminal's size. Install xterm or a similar utility to provide you with the
|Pasting long strings doesn't work.||The serial console limits the length of strings pasted into the terminal to 2048 characters to prevent overloading the serial port bandwidth.|
|Erratic keyboard input in SLES BYOS images. Keyboard input is only sporadically recognized.||This is an issue with the Plymouth package. Plymouth should not be run in Azure as you don't need a splash screen, and Plymouth interferes with the platform's ability to use Serial Console. Remove Plymouth with
Frequently asked questions
Q. How can I send feedback?
A. Provide feedback by creating a GitHub issue at https://aka.ms/serialconsolefeedback. Alternatively (less preferred), you can send feedback via firstname.lastname@example.org or in the virtual machine category of https://feedback.azure.com.
Q. Does the serial console support copy/paste?
A. Yes. Use Ctrl+Shift+C and Ctrl+Shift+V to copy and paste into the terminal.
Q. Can I use serial console instead of an SSH connection?
A. While this usage may seem technically possible, the serial console is intended to be used primarily as a troubleshooting tool in situations where connectivity via SSH isn't possible. We recommend against using the serial console as an SSH replacement for the following reasons:
- The serial console doesn't have as much bandwidth as SSH. Because it's a text-only connection, more GUI-heavy interactions are difficult.
- Serial console access is currently possible only by using a username and password. Because SSH keys are far more secure than username/password combinations, from a sign-in security perspective, we recommend SSH over serial console.
Q. Who can enable or disable serial console for my subscription?
A. To enable or disable the serial console at a subscription-wide level, you must have write permissions to the subscription. Roles that have write permission include administrator or owner roles. Custom roles can also have write permissions.
Q. Who can access the serial console for my VM/virtual machine scale set?
A. You must have the Virtual Machine Contributor role or higher for a VM or virtual machine scale set to access the serial console.
Q. My serial console isn't displaying anything, what do I do?
A. Your image is likely misconfigured for serial console access. For information about configuring your image to enable the serial console, see Serial console Linux distribution availability.
Q. Is the serial console available for virtual machine scale sets?
A. Yes, it is! See Get started with Serial Console.
Q. If I set up my VM or virtual machine scale set by using only SSH key authentication, can I still use the serial console to connect to my VM/virtual machine scale set instance?
A. Yes. Because the serial console doesn't require SSH keys, you only need to set up a username/password combination. You can do so by selecting Reset password in the Azure portal and using those credentials to sign in to the serial console.
- Use the serial console to access GRUB and single user mode.
- Use the serial console for NMI and SysRq calls.
- Learn how to use the serial console to enable GRUB in various distros
- The serial console is also available for Windows VMs.
- Learn more about boot diagnostics.
Contact us for help
Submit and view feedback for