Tutorial: Use a managed identity to connect Key Vault to an Azure Web App with .NET

Azure Key Vault provides a way to securely store credentials and other secrets, but your code needs to authenticate to Key Vault to retrieve them. Managed identities for Azure resources overview helps to solve this problem by giving Azure services an automatically managed identity in Azure AD. You can use this identity to authenticate to any service that supports Azure AD authentication, including Key Vault, without having to display credentials in your code.

This tutorial uses a managed identity to authenticate an Azure Web App with an Azure Key Vault. Although the steps use the Azure Key Vault v4 client library for .NET and the Azure CLI, the same basic principles apply when using the development language of your choice, Azure PowerShell, and/or the Azure portal.


To complete this quickstart:

Create a resource group

A resource group is a logical container into which Azure resources are deployed and managed. Create a resource group to house both your key vault and your web app with the az group create command:

az group create --name "myResourceGroup" -l "EastUS"

Set up your key vault

You will now create a key vault and place a secret in it, for use later in this tutorial.

To create a key vault, use the az keyvault create command:


Each key vault must have a unique name. Replace with the name of your key vault in the following examples.

az keyvault create --name "<your-keyvault-name>" -g "myResourceGroup"

Make a note of the returned vaultUri, which will be in the format"https://.vault.azure.net/". It will be used in the Update the code step.

You can now place a secret in your key vault with the az keyvault secret set command. Set the name of your secret to "MySecret" and the value to "Success!".

az keyvault secret set --vault-name "<your-keyvault-name>" --name "MySecret" --value "Success!"

Create a .NET web app

Create a local app

In a terminal window on your machine, create a directory named akvwebapp and change the current directory to it.

mkdir akvwebapp
cd akvwebapp

Now create a new .NET Core app with the dotnet new web command:

dotnet new web

Run the application locally so that you see how it should look when you deploy it to Azure.

dotnet run

Open a web browser, and navigate to the app at http://localhost:5000.

You will see the Hello World message from the sample app displayed in the page.

Initialize the Git repository

In your terminal window, press Ctrl+C to exit the web server. Initialize a Git repository for the .NET Core project.

git init
git add .
git commit -m "first commit"

Configure a deployment user

FTP and local Git can deploy to an Azure web app by using a deployment user. Once you configure your deployment user, you can use it for all your Azure deployments. Your account-level deployment username and password are different from your Azure subscription credentials.

To configure the deployment user, run the az webapp deployment user set command. Choose a username and password that adheres to these guidelines:

  • The username must be unique within Azure, and for local Git pushes, must not contain the ‘@’ symbol.
  • The password must be at least eight characters long, with two of the following three elements: letters, numbers, and symbols.
az webapp deployment user set --user-name "<username>" --password "<password>"

The JSON output shows the password as null. If you get a 'Conflict'. Details: 409 error, change the username. If you get a 'Bad Request'. Details: 400 error, use a stronger password.

Record your username and password to use to deploy your web apps.

Create an app service plan

Create an App Service plan with the Azure CLI az appservice plan create command. This following example creates an App Service plan named myAppServicePlan in the Free pricing tier:

az appservice plan create --name myAppServicePlan --resource-group myResourceGroup --sku FREE

When the App Service plan has been created, the Azure CLI shows information similar to the following example:

  "adminSiteName": null,
  "appServicePlanName": "myAppServicePlan",
  "geoRegion": "West Europe",
  "hostingEnvironmentProfile": null,
  "id": "/subscriptions/0000-0000/resourceGroups/myResourceGroup/providers/Microsoft.Web/serverfarms/myAppServicePlan",
  "kind": "app",
  "location": "West Europe",
  "maximumNumberOfWorkers": 1,
  "name": "myAppServicePlan",
  < JSON data removed for brevity. >
  "targetWorkerSizeId": 0,
  "type": "Microsoft.Web/serverfarms",
  "workerTierName": null

Create a remote web app

Create an Azure web app in the myAppServicePlan App Service plan.


Similar to Key Vault, an Azure Web App must have a unique name. Replace <your-webapp-name> with the name of your web app the following examples.

az webapp create --resource-group "myResourceGroup" --plan "myAppServicePlan" --name "<your-webapp-name>" --deployment-local-git

When the web app has been created, the Azure CLI shows output similar to the following example:

Local git is configured with url of 'https://<username>@<your-webapp-name>.scm.azurewebsites.net/<ayour-webapp-name>.git'
  "availabilityState": "Normal",
  "clientAffinityEnabled": true,
  "clientCertEnabled": false,
  "clientCertExclusionPaths": null,
  "cloningInfo": null,
  "containerSize": 0,
  "dailyMemoryTimeQuota": 0,
  "defaultHostName": "<your-webapp-name>.azurewebsites.net",
  "deploymentLocalGitUrl": "https://<username>@<your-webapp-name>.scm.azurewebsites.net/<your-webapp-name>.git",
  "enabled": true,
  < JSON data removed for brevity. >

The URL of the Git remote is shown in the deploymentLocalGitUrl property, with the format https://<username>@<your-webapp-name>.scm.azurewebsites.net/<your-webapp-name>.git. Save this URL, as you need it later.

Browse to your newly created app. Replace <your-webapp-name> with your app name.


You will see the default webpage for a newly created Azure Web App.

Deploy your local app

Back in the local terminal window, add an Azure remote to your local Git repository, replacing <deploymentLocalGitUrl-from-create-step> with the URL of the Git remote that you saved from Create a remote web app step.

git remote add azure <deploymentLocalGitUrl-from-create-step>

Push to the Azure remote to deploy your app with the following command. When Git Credential Manager prompts you for credentials, use the credentials you created in Configure a deployment user step.

git push azure master

This command may take a few minutes to run. While running, it displays information similar to the following example:

Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 285 bytes | 95.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0), pack-reused 0
remote: Deploy Async
remote: Updating branch 'master'.
remote: Updating submodules.
remote: Preparing deployment for commit id 'd6b54472f7'.
remote: Repository path is /home/site/repository
remote: Running oryx build...
remote: Build orchestrated by Microsoft Oryx, https://github.com/Microsoft/Oryx
remote: You can report issues at https://github.com/Microsoft/Oryx/issues
remote: Oryx Version      : 0.2.20200114.13, Commit: 204922f30f8e8d41f5241b8c218425ef89106d1d, ReleaseTagName: 20200114.13
remote: Build Operation ID: |imoMY2y77/s=.40ca2a87_
remote: Repository Commit : d6b54472f7e8e9fd885ffafaa64522e74cf370e1
remote: Deployment successful.
remote: Deployment Logs : 'https://<your-webapp-name>.scm.azurewebsites.net/newui/jsonviewer?view_url=/api/deployments/d6b54472f7e8e9fd885ffafaa64522e74cf370e1/log'
To https://<your-webapp-name>.scm.azurewebsites.net:443/<your-webapp-name>.git
   d87e6ca..d6b5447  master -> master

Browse to (or refresh) the deployed application using your web browser.


You will see the "Hello World!" message you previously saw when visiting http://localhost:5000.

Create and assign a managed identity

In the Azure CLI, to create the identity for this application, run the az webapp-identity assign command:

az webapp identity assign --name "<your-webapp-name>" --resource-group "myResourceGroup"

The operation will return this JSON snippet:

  "principalId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "tenantId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "type": "SystemAssigned"

To give your web app permission to do get and list operations on your key vault, pass the principalID to the Azure CLI az keyvault set-policy command:

az keyvault set-policy --name "<your-keyvault-name>" --object-id "<principalId>" --secret-permissions get list

Modify the app to access your key vault

Install the packages

From the terminal window, install the Azure Key Vault client library for .NET packages:

dotnet add package Azure.Identity
dotnet add package Azure.Security.KeyVault.Secrets

Update the code

Find and open the Startup.cs file in your akvwebapp project.

Add these two lines to the header:

using Azure.Identity;
using Azure.Security.KeyVault.Secrets;
using Azure.Core;

Add these lines before the app.UseEndpoints call, updating the URI to reflect the vaultUri of your key vault. Below code is using 'DefaultAzureCredential()' for authentication to key vault, which is using token from application managed identity to authenticate. It is also using exponential backoff for retries in case of key vault is being throttled.

SecretClientOptions options = new SecretClientOptions()
        Retry =
            Delay= TimeSpan.FromSeconds(2),
            MaxDelay = TimeSpan.FromSeconds(16),
            MaxRetries = 5,
            Mode = RetryMode.Exponential
var client = new SecretClient(new Uri("https://<your-unique-key-vault-name>.vault.azure.net/"), new DefaultAzureCredential(),options);

KeyVaultSecret secret = client.GetSecret("mySecret");

string secretValue = secret.Value;

Update the line await context.Response.WriteAsync("Hello World!"); to read:

await context.Response.WriteAsync(secretValue);

Be certain to save your changes before proceeding to the next step.

Redeploy your web app

Having updated your code, you can redeploy it to Azure with the following Git commands:

git add .
git commit -m "Updated web app to access my key vault"
git push azure master

Visit your completed web app


Where before you saw Hello World, you should now see the value of your secret displayed: Success!

Next steps