Use SSH on Windows to connect to Linux virtual machines or Docker Containers on Microsoft Azure from a Mac or Windows machine.

In this post I am going to describe how to create and use ssh-rsa and .pem format public and private key files on Windows that you can use to connect to your Linux VMs on Azure with the ssh command. If you already have .pem files created, you can use those to create Linux VMs to which you can connect using ssh. Several other commands use the SSH protocol and key files to perform work securely, notably scp or Secure Copy, which can securely copy files to and from computers that support SSH connections.

What SSH and key-creation programs do you need?

SSH — or secure shell — is an encrypted connection protocol that allows secure logins over unsecured connections. It is the default connection protocol for Linux VMs hosted in Azure unless you configure your Linux VMs to enable some other connection mechanism. Windows users can also connect to and manage Linux VMs in Azure using an ssh client implementation, but Windows computers do not typically come with an ssh client, so you will need to choose one.

Common clients you can install include:

If you’re feeling especially geeky, you can also try out the new port of the OpenSSH toolset to Windows. Be aware, however, that this is code that is currently in development, and you should review the codebase before you use it for production systems.


Azure has two different deployment models for creating and working with resources: Resource Manager and classic. This article covers using both models, but Microsoft recommends that most new deployments use the Resource Manager model.

Which key files do you need to create?

A basic SSH setup for Azure includes an ssh-rsa public and private key pair of 2048 bits (by default, ssh-keygen stores these files as ~/.ssh/id_rsa and ~/.ssh/ unless you change the defaults) as well as a .pem file generated from the id_rsa private key file for use with the classic deployment model of the classic portal.

Here are the deployment scenarios, and the types of files you use in each:

  1. ssh-rsa keys are required for any deployment using the Azure portal, regardless of the deployment model.
  2. .pem file are required to create VMs using the classic portal. .pem files are also supported in classic deployments that use the Azure CLI.

If you plan to manage service deployed with the classic deployment model, you may also want to create a .cer format file to upload to the portal — although this doesn’t involve ssh or connecting to Linux VMS, which is the subject of this article. To create those files on Windows, type:


Get ssh-keygen and openssl on Windows

This section above listed several utilities that include an ssh-keygen and openssl for Windows. A couple of examples are listed below:

Use Git for Windows

  1. Download and install Git for Windows from the following location:
  2. Run Git Bash from the Start Menu > All Apps > Git Shell

You may encounter the following error when running the openssl commands above:

Unable to load config info from /usr/local/ssl/openssl.cnf

The easiest way to resolve this is to set the OPENSSL_CONF environment variable. The process for setting this variable will vary depending on the shell that you have configured in Github:





Git Bash:


Use Cygwin

  1. Download and install Cygwin from the following location:
  2. Ensure that the OpenSSL package and all of its dependencies are installed.
  3. Run cygwin

Create a Private Key

  1. Follow one of the set of instructions above to be able to run openssl.exe
  2. Type in the following command:


Your screen should look like the following:


>>> Generating a 2048 bit RSA private key …………………………………+++ …………………..+++ writing new private key to ‘myPrivateKey.key’ —–

You are about to be asked to enter information that will be incorporated into your certificate request. What you are about to enter is what is called a Distinguished Name or a DN. There are quite a few fields but you can leave some blank For some fields there will be a default value, If you enter ‘.’, the field will be left blank. —– Country Name (2 letter code) [AU]:

  1. Answer the questions that are asked.
  2. It would have created two files: myPrivateKey.key and myCert.pem.
  3. If you are going to use the API directly, and not use the Management Portal, convert the myCert.pem to myCert.cer (DER encoded X509 certificate) using the following command:


Create a PPK for Putty

  1. Download and install Puttygen from the following location:
  2. Puttygen may not be able to read the private key that was created earlier (myPrivateKey.key). Run the following command to translate it into an RSA private key that Puttygen can understand:


    The command above should produce a new private key called myPrivateKey_rsa.

  3. Run puttygen.exe
  4. Click the menu: File > Load a Private Key
  5. Find your private key, which we named myPrivateKey_rsa above. You will need to change the file filter to show All Files (*.*)
  6. Click Open. You will receive a prompt which should look like this:

  7. Click OK
  8. Click Save Private Key, which is highlighted in the screenshot below:

  9. Save the file as a PPK

Use Putty to Connect to a Linux Machine

  1. Download and install putty from the following location:
  2. Run putty.exe
  3. Fill in the host name using the IP from the Management Portal:

  4. Before selecting Open, click the Connection > SSH > Auth tab to choose your private key. See the screenshot below for the field to fill in:

  5. Click Open to connect to your virtual machine

Leave a Reply

©2017 Luke Angel

Log in with your credentials

Forgot your details?

%d bloggers like this: