Tutorial: Use a Windows 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. 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 Windows 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 Managed Service Identity on a Windows 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 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 https://portal.azure.com.

Create a Windows virtual machine in a new resource group

For this tutorial, we create a new Windows 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 Windows Server 2016 Datacenter.
  3. Enter the virtual machine information. The Username and Password created here is the credentials you use to login to the virtual machine.
  4. Choose the proper Subscription for the virtual machine in the dropdown.
  5. To select a new Resource Group you would like to 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 blade, keep the defaults and click OK.

    Alt image text

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. Enabling MSI tells Azure to create a managed identity for your Virtual Machine. Under the covers, enabling MSI does two things: registers your VM with Azure Active Directory to create its managed identity, and configures the identity on 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

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 AD 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 identity and use it to retrieve the secret from the Key Vault

If you don’t have PowerShell 4.3.1 or greater installed, you'll need to download and install the latest version.

First, we use the VM’s MSI to get an access token to authenticate to Key Vault:

  1. In the portal, navigate to Virtual Machines and go to your Windows virtual machine and in the Overview, click Connect.
  2. Enter in your Username and Password for which you added when you created the Windows VM.
  3. Now that you have created a Remote Desktop Connection with the virtual machine, open PowerShell in the remote session.
  4. In PowerShell, invoke the web request on the tenant to get the token for the local host in the specific port for the VM.

    The PowerShell request:

    $response = Invoke-WebRequest -Uri '' -Method GET -Headers @{Metadata="true"} 

    Next, extract the full response which is stored as a JavaScript Object Notation (JSON) formatted string in the $response object.

    $content = $response.Content | ConvertFrom-Json 

    Next, extract the access token from the response.

    $KeyVaultToken = $content.access_token 

    Finally, use PowerShell’s Invoke-WebRequest command to retrieve the secret you created earlier in the Key Vault, passing the access token in the Authorization header. You’ll need the URL of your Key Vault, which is in the Essentials section of the Overview page of the Key Vault.

    (Invoke-WebRequest -Uri https://<your-key-vault-URL>/secrets/<secret-name>?api-version=2016-10-01 -Method GET -Headers @{Authorization="Bearer $KeyVaultToken"}).content 

    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.

Next steps

In this tutorial, you learned how to create a Managed Service Identity to access Azure Key Vault. To learn more about Azure Key Vault see: