Use a Linux VM Managed Service Identity (MSI) to access Azure Key Vault

Managed Service Identity (MSI) is a public preview feature of Azure Active Directory. Make sure you review the known issues before you begin. If you would like to be considered for enrollment in the private preview, visit our sign-up page. For more information about previews, see Supplemental Terms of Use for Microsoft Azure Previews.

This tutorial shows you how to enable Managed Service Identity (MSI) for a Linux Virtual Machine, then use that identity to access Azure Key Vault. Serving as a bootstrap, Key Vault makes it possible for your client application to then use the secret to access resources not secured by Azure Active Directory (AD). Managed Service Identities are automatically managed by Azure and enable you to authenticate to services that support Azure AD authentication, without needing to insert credentials into your code.

You learn how to:

  • Enable MSI on a Linux Virtual Machine
  • Grant your VM access to a secret stored in a Key Vault
  • Get an access token using the VM identity and use it to retrieve the secret from the Key Vault


If you're unfamiliar with MSI, check out the Managed Service Identity overview. If you don't already have an Azure account, sign up for a free account before continuing.

To perform the required resource creation and role management, your account needs "Owner" permissions at the appropriate scope (your subscription or resource group). If you need assistance with role assignment, see Use Role-Based Access Control to manage access to your Azure subscription resources.

Sign in to Azure

Sign in to the Azure portal at

Create a Linux Virtual Machine in a new Resource Group

For this tutorial, we create a new Linux VM. You can also enable MSI on an existing VM.

  1. Click the Create a resource button found on the upper left-hand corner of the Azure portal.
  2. Select Compute, and then select Ubuntu Server 16.04 LTS.
  3. Enter the virtual machine information. For Authentication type, select SSH public key or Password. The created credentials allow you to log in to the VM.

    Alt image text

  4. Choose a Subscription for the virtual machine in the dropdown.

  5. To select a new Resource Group you would like the virtual machine to be created in, choose Create New. When complete, click OK.
  6. Select the size for the VM. To see more sizes, select View all or change the Supported disk type filter. On the settings page, keep the defaults and click OK.

Enable MSI on your VM

A Virtual Machine MSI enables you to get access tokens from Azure AD without you needing to put credentials into your code. Under the covers, enabling MSI does two things: it installs the MSI VM extension on your VM and it enables MSI for the VM.

  1. Select the Virtual Machine that you want to enable MSI on.
  2. On the left navigation bar click Configuration.
  3. You see Managed Service Identity. To register and enable the MSI, select Yes, if you wish to disable it, choose No.
  4. Ensure you click Save to save the configuration.

    Alt image text

  5. If you wish to check which extensions are on this Linux VM, click Extensions. If MSI is enabled, the ManagedIdentityExtensionforLinux appears on the list.

    Alt image text

Grant your VM access to a Secret stored in a Key Vault

Using MSI your code can get access tokens to authenticate to resources that support Azure Active Directory authentication. However, not all Azure services support Azure AD authentication. To use MSI with those services, store the service credentials in Azure Key Vault, and use MSI to access Key Vault to retrieve the credentials.

First, we need to create a Key Vault and grant our VM’s identity access to the Key Vault.  

  1. At the top of the left navigation bar, select Create a resource > Security + Identity > Key Vault.
  2. Provide a Name for the new Key Vault.
  3. Locate the Key Vault in the same subscription and resource group as the VM you created earlier.
  4. Select Access policies and click Add new.
  5. In Configure from template, select Secret Management.
  6. Choose Select Principal, and in the search field enter the name of the VM you created earlier. Select the VM in the result list and click Select.
  7. Click OK to finishing adding the new access policy, and OK to finish access policy selection.
  8. Click Create to finish creating the Key Vault.

    Alt image text

Next, add a secret to the Key Vault, so that later you can retrieve the secret using code running in your VM:

  1. Select All Resources, and find and select the Key Vault you created.
  2. Select Secrets, and click Add.
  3. Select Manual, from Upload options.
  4. Enter a name and value for the secret. The value can be anything you want.
  5. Leave the activation date and expiration date clear, and leave Enabled as Yes.
  6. Click Create to create the secret.

Get an access token using the VM's identity and use it to retrieve the secret from the Key Vault

To complete these steps, you need an SSH client. If you are using Windows, you can use the SSH client in the Windows Subsystem for Linux. If you need assistance configuring your SSH client's keys, see How to Use SSH keys with Windows on Azure, or How to create and use an SSH public and private key pair for Linux VMs in Azure.

  1. In the portal, navigate to your Linux VM and in the Overview, click Connect.
  2. Connect to the VM with the SSH client of your choice.
  3. In the terminal window, using CURL, make a request to the local MSI endpoint to get an access token for Azure Key Vault.

    The CURL request for the access token is below.

    curl http://localhost:50342/oauth2/token --data "resource=" -H Metadata:true  

    The response includes the access token you need to access Resource Manager.



    You can use this access token to authenticate to Azure Key Vault. The next CURL request shows how to read a secret from Key Vault using CURL and the Key Vault REST API. You’ll need the URL of your Key Vault, which is in the Essentials section of the Overview page of the Key Vault. You will also need the access token you obtained on the previous call.

    curl https://<YOUR-KEY-VAULT-URL>/secrets/<secret-name>?api-version=2016-10-01 -H "Authorization: Bearer <ACCESS TOKEN>" 

    The response will look like this:


Once you’ve retrieved the secret from the Key Vault, you can use it to authenticate to a service that requires a name and password.

Use the following comments section to provide feedback and help us refine and shape our content.