Tutorial: Use a Linux VM system-assigned managed identity to access Azure Key Vault

Managed identities for Azure resources is a feature of Microsoft Entra ID. Each of the Azure services that support managed identities for Azure resources are subject to their own timeline. Make sure you review the availability status of managed identities for your resource and known issues before you begin.

This tutorial shows you how a Linux virtual machine (VM) can use a system-assigned managed identity to access Azure Key Vault. Key Vault makes it possible for your client application to then use a secret to access resources not secured by Microsoft Entra ID. Managed Service Identities are automatically managed by Azure and enable you to authenticate to services that support Microsoft Entra authentication, without including authentication information in your code.

You learn how to:

  • Grant your VM access to a secret stored in a Key Vault
  • Get an access token using the VM's identity and use it to retrieve the secret from the Key Vault  


Create a Key Vault  


Steps in this article might vary slightly based on the portal you start from.

This section shows how to grant your VM access to a secret stored in a Key Vault. Using managed identities for Azure resources, your code can get access tokens to authenticate to resources that support Microsoft Entra authentication.  However, not all Azure services support Microsoft Entra authentication. To use managed identities for Azure resources with those services, store the service credentials in Azure Key Vault, and use the VM's managed identity to access Key Vault to retrieve the credentials.

First, we need to create a Key Vault and grant our VM's system-assigned managed identity access to the Key Vault.

  1. Sign in to the Azure portal.

  2. At the top of the left navigation bar, select Create a resource.

  3. In the Search the Marketplace box type in Key Vault and hit Enter.

  4. Select Key Vault from the results.

  5. Select Create.

  6. Provide a Name for the new key vault.

    Screenshot showing the Azure Key vault creation screen.

  7. Fill out all required information making sure that you choose the subscription and resource group where you created the virtual machine that you are using for this tutorial.

  8. Select Review+ create

  9. Select Create

Create a secret

Next, add a secret to the Key Vault, so you can retrieve it later using code running in your VM. In this tutorial, we are using PowerShell but the same concepts apply to any code executing in this virtual machine.

  1. Navigate to your newly created Key Vault.

  2. Select Secrets, and select Add.

  3. Select Generate/Import

  4. In the Create a secret screen from Upload options leave Manual selected.

  5. Enter a name and value for the secret.  The value can be anything you want. 

  6. Leave the activation date and expiration date clear, and leave Enabled as Yes

  7. Select Create to create the secret.

    Screenshot showing secret creation.

Grant access

The managed identity used by the virtual machine needs access to read the secret stored in Key Vault.

  1. Navigate to your newly created Key Vault

  2. Select Access Policy from the menu on the left side.

  3. Select Add Access Policy

    Screenshot of the key vault create access policy screen.

  4. In the Add access policy section under Configure from template (optional) choose Secret Management from the pull-down menu.

  5. 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 choose Select.

  6. Select Add

  7. Select Save.

Access data

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.


All Azure SDKs support the Azure.Identity library that makes it easy to acquire Microsoft Entra tokens to access target services. Learn more about Azure SDKs and leverage the Azure.Identity library.

  1. In the portal, navigate to your Linux VM and in the Overview, select Connect

  2. Connect to the VM with the SSH client of your choice. 

  3. In the terminal window, use CURL to make a request to the local managed identities for Azure resources endpoint to get an access token for Azure Key Vault.    

    The CURL request for the access token is below.  

    curl '' -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 need the URL of your Key Vault, which is in the Essentials section of the Overview page of the Key Vault.  You 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 looks like this: 


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

Clean up resources

When you want to clean up the resources, sign in to the Azure portal, select Resource groups, locate, and select the resource group that was created in the process of this tutorial (such as mi-test), and then use the Delete resource group command.

Alternatively you can also do this via PowerShell or the CLI.

Next steps

In this tutorial, you learned how to use a Linux VM system-assigned managed identity to access Azure Key Vault. To learn more about Azure Key Vault see: