Using Azure Key Vault on .Net Core 3.1

Tram Ho

One fine day you have a .NET Core 3.1 project that needs to run Key Vault. But if you keep reading the document and don’t understand, then read this article.

What is Azure Key Vault

Azure Key Vault is a service that stores keys and configs for websites. To increase security, often only keys with a key or password can be used, and its cost is not cheap. To use it is also very simple if you understand how it works.

Azure Key Vault does not have a config for you to integrate directly into the project, to use you must create an App Registration, and in Azure Key Vault you proceed to grant the App Registration permission to use. You use the App Registration config to configure the project.

The content of my article just gives how it works, but in terms of details and images, people click on the original link at the bottom of the post.

Sign up for Azure Key Vault

In Azure Portable -> Find Azure key vault proceed to fill in the required information to initialize.

Register app for keyvault

Look for ” App Registration ” in the list of apps for Azure. Proceed to create the App name, after success you will get the Application (client) ID ( This is the Client ID used for the keyvault later ) Go to Certificates & secrets to create the Client secret used for keyvault.

Generate secret keys for Azure Key Vault

In Azure Keyvault go to the Secrets tab , create the desired secrect keys, note if hierarchical type

You create the key under: RedisCache – ConnectionString , for each nested level, you add – before each config name. When needed, you can go here to update the new config.

Attach Azure Key Vault to the App

Normally, Azure Keyvault does not have a config for you to configure in your project, but you must assign permission to another App to use Key Vault and use Client Id, and Secret key from that app to configure in project. On Azure Keyvault -> Access policies -> Add Access Policy

  1. Conduct additional permissions for the App Usually set is: get, set, list, delete In the principal proceed to select the App you created in App Registration above.

Configure Azure Key Vault on .NET Core 3.1

Install packages for .NET Core 3.1 project

Install the packages above to allow Project to load Azure keyvault

  • Microsoft.Azure.KeyVault
  • Microsoft.Extensions.Configuration.AzureKeyVault

Create config on appsettings.json

Look at the keyvault’s config with the following information:

  • Vault: The name of the Keyvault name in Azure Keyvault
  • ClientID: The Client Id of the application associated with the keyvault ( App Registration )
  • ClientID: Client secrect of the application associated with the keyvault ( App Registration )

Write load data from key vault for project

Note the paragraph:

This paragraph will load the config of Azure Keyvault for you to use. When you need to call a used config key, the system will check that the keyvault will not be returned, otherwise the system will load from appsettings.json for you.

Each time config calls use IConfiguration to get the corresponding key.


  • Using Azure Keyvault is not difficult, but you have not envisioned the configuration to get Client ID, Client Secret for the system.
  • Not every key you use keyvault, that will make too many unnecessary keys, difficult to remember. Only used for keys related to encryption, passwords, important tokens.
  • Azure Keyvault costs, for an individual user I recommend not to use because of the cost. If you try it out, don’t forget to delete the project if the test is complete, otherwise it will be charged.

Reference link: I have read through many tutorials or videos, I see the link below is full of information and easy to understand for your config. I have used the content in the link below

Share the news now

Source : Viblo