Connect to a Windows Azure virtual machine with RDP or SSH
Updated: November 27, 2013
This article is a short summary of using Remote Desktop Protocol (RDP) or a Secure Shell (SSH) client to log on to a Windows Azure virtual machine. It also has requirements and troubleshooting tips, with links to detailed instructions.
To log on to a virtual machine, you use Remote Desktop for Windows operating systems, or a Secure Shell (SSH) client for Linux operating systems. From the Windows Azure Management Portal, after you’ve selected the virtual machine, click Connect at the bottom of the screen to start a remote session. For more instructions on logging on, see How to Log on to a Virtual Machine Running Windows Server or How to Log on to a Virtual Machine Running Linux.
To be able to log on, you’ll need the following:
The password of the account you set up for administrative access. This account was set up when the virtual machine was created, with the password that was specified.
An endpoint to allow access from the client to the virtual machine through the specified port and protocol. This is usually done for you automatically when you create a virtual machine in the Management Portal. If you use the Quick Create option, the appropriate endpoint is set up automatically. If you choose the From Gallery option, an endpoint is set up for Remote Desktop or SSH unless you remove the endpoint while you’re configuring the virtual machine.
The firewall of the guest operating system configured to allow access. This is done automatically if you use an image provided by Windows Azure to create the virtual machine. If you use an image you’ve uploaded, make sure to configure it for remote access before you upload it.
Tips for troubleshooting connection problems
The following tips give you an overview of what you can try if you have problems connecting. For detailed instructions on troubleshooting, see Troubleshooting Endpoint Connectivity.
Try to start the connection again. When you’re prompted for password, look at the domain information that’s added to the user account. If it’s not the correct domain for the user account on the virtual machine, specify the correct domain. For example, in Remote Desktop Connection, you can select Other User, add a backslash before user name and then type the password.
Restart the virtual machine.
Delete and then recreate the endpoint that for Remote Desktop or SSH. When you recreate the endpoint, use the default values.
Try to connect using a different network. For example, if you are using a corporate network, try a network that’s separate from the corporate network. If that works, it indicates that the corporate network doesn’t allow that type of connection. For example, the connection might be blocked by the corporate firewall. Contact your corporate network administrator for help.
If none of those tips work, you might need to resize or recreate the virtual machine. The detailed instructions noted above provide more information.