Azure.Security.KeyVault.Secrets 4.6.0

Prefix Reserved
dotnet add package Azure.Security.KeyVault.Secrets --version 4.6.0                
NuGet\Install-Package Azure.Security.KeyVault.Secrets -Version 4.6.0                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Azure.Security.KeyVault.Secrets" Version="4.6.0" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Azure.Security.KeyVault.Secrets --version 4.6.0                
#r "nuget: Azure.Security.KeyVault.Secrets, 4.6.0"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Azure.Security.KeyVault.Secrets as a Cake Addin
#addin nuget:?package=Azure.Security.KeyVault.Secrets&version=4.6.0

// Install Azure.Security.KeyVault.Secrets as a Cake Tool
#tool nuget:?package=Azure.Security.KeyVault.Secrets&version=4.6.0                

Azure Key Vault secret client library for .NET

Azure Key Vault is a cloud service that provides a secure storage of secrets, such as passwords and database connection strings.

The Azure Key Vault secrets client library allows you to securely store and control the access to tokens, passwords, API keys, and other secrets. This library offers operations to create, retrieve, update, delete, purge, backup, restore, and list the secrets and its versions.

Source code | Package (NuGet) | API reference documentation | Product documentation | Samples | Migration guide

Getting started

Install the package

Install the Azure Key Vault secrets client library for .NET with NuGet:

dotnet add package Azure.Security.KeyVault.Secrets


  • An Azure subscription.
  • An existing Azure Key Vault. If you need to create an Azure Key Vault, you can use the Azure Portal or Azure CLI.
  • Authorization to an existing Azure Key Vault using either RBAC (recommended) or access control.

If you use the Azure CLI, replace <your-resource-group-name> and <your-key-vault-name> with your own, unique names:

az keyvault create --resource-group <your-resource-group-name> --name <your-key-vault-name>

Authenticate the client

In order to interact with the Azure Key Vault service, you'll need to create an instance of the SecretClient class. You need a vault url, which you may see as "DNS Name" in the portal, and credentials to instantiate a client object.

The examples shown below use a DefaultAzureCredential, which is appropriate for most scenarios including local development and production environments. Additionally, we recommend using a managed identity for authentication in production environments. You can find more information on different ways of authenticating and their corresponding credential types in the Azure Identity documentation.

To use the DefaultAzureCredential provider shown below, or other credential providers provided with the Azure SDK, you must first install the Azure.Identity package:

dotnet add package Azure.Identity

Instantiate a DefaultAzureCredential to pass to the client. The same instance of a token credential can be used with multiple clients if they will be authenticating with the same identity.

// Create a new secret client using the default credential from Azure.Identity using environment variables previously set,
var client = new SecretClient(vaultUri: new Uri(vaultUrl), credential: new DefaultAzureCredential());

// Create a new secret using the secret client.
KeyVaultSecret secret = client.SetSecret("secret-name", "secret-value");

// Retrieve a secret using the secret client.
secret = client.GetSecret("secret-name");

Key concepts


A KeyVaultSecret is the fundamental resource within Azure Key Vault. From a developer's perspective, Azure Key Vault APIs accept and return secret values as strings.


A SecretClient provides both synchronous and asynchronous operations in the SDK allowing for selection of a client based on an application's use case. Once you've initialized a SecretClient, you can interact with secrets in Azure Key Vault.

Thread safety

We guarantee that all client instance methods are thread-safe and independent of each other (guideline). This ensures that the recommendation of reusing client instances is always safe, even across threads.

Additional concepts

Client options | Accessing the response | Long-running operations | Handling failures | Diagnostics | Mocking | Client lifetime


The Azure.Security.KeyVault.Secrets package supports synchronous and asynchronous APIs.

The following section provides several code snippets using the client created above, covering some of the most common Azure Key Vault secret service related tasks:

Sync examples

Async examples

Create a secret

SetSecret creates a KeyVaultSecret to be stored in the Azure Key Vault. If a secret with the same name already exists, then a new version of the secret is created.

KeyVaultSecret secret = client.SetSecret("secret-name", "secret-value");


Retrieve a secret

GetSecret retrieves a secret previously stored in the Azure Key Vault.

KeyVaultSecret secret = client.GetSecret("secret-name");


Update an existing secret

UpdateSecretProperties updates a secret previously stored in the Azure Key Vault. Only the attributes of the secret are updated. To update the value, call SecretClient.SetSecret on a secret with the same name.

KeyVaultSecret secret = client.GetSecret("secret-name");

// Clients may specify the content type of a secret to assist in interpreting the secret data when its retrieved.
secret.Properties.ContentType = "text/plain";

// You can specify additional application-specific metadata in the form of tags.
secret.Properties.Tags["foo"] = "updated tag";

SecretProperties updatedSecretProperties = client.UpdateSecretProperties(secret.Properties);


Delete a secret

StartDeleteSecret starts a long-running operation to delete a secret previously stored in the Azure Key Vault. You can retrieve the secret immediately without waiting for the operation to complete. When soft-delete is not enabled for the Azure Key Vault, this operation permanently deletes the secret.

DeleteSecretOperation operation = client.StartDeleteSecret("secret-name");

DeletedSecret secret = operation.Value;

Delete and purge a secret

You will need to wait for the long-running operation to complete before trying to purge or recover the secret. You can do this by calling UpdateStatus in a loop as shown below:

DeleteSecretOperation operation = client.StartDeleteSecret("secret-name");

// You only need to wait for completion if you want to purge or recover the secret.
// You should call `UpdateStatus` in another thread or after doing additional work like pumping messages.
while (!operation.HasCompleted)


DeletedSecret secret = operation.Value;

List secrets

This example lists all the secrets in the specified Azure Key Vault. The value is not returned when listing all secrets. You will need to call SecretClient.GetSecret to retrieve the value.

Pageable<SecretProperties> allSecrets = client.GetPropertiesOfSecrets();

foreach (SecretProperties secretProperties in allSecrets)

Create a secret asynchronously

The asynchronous APIs are identical to their synchronous counterparts, but return with the typical "Async" suffix for asynchronous methods and return a Task.

This example creates a secret in the Azure Key Vault with the specified optional arguments.

KeyVaultSecret secret = await client.SetSecretAsync("secret-name", "secret-value");


List secrets asynchronously

Listing secrets does not rely on awaiting the GetPropertiesOfSecretsAsync method, but returns an AsyncPageable<SecretProperties> that you can use with the await foreach statement:

AsyncPageable<SecretProperties> allSecrets = client.GetPropertiesOfSecretsAsync();

await foreach (SecretProperties secretProperties in allSecrets)

Delete a secret asynchronously

When deleting a secret asynchronously before you purge it, you can await the WaitForCompletionAsync method on the operation. By default, this loops indefinitely but you can cancel it by passing a CancellationToken.

DeleteSecretOperation operation = await client.StartDeleteSecretAsync("secret-name");

// You only need to wait for completion if you want to purge or recover the secret.
await operation.WaitForCompletionAsync();

DeletedSecret secret = operation.Value;
await client.PurgeDeletedSecretAsync(secret.Name);


See our troubleshooting guide for details on how to diagnose various failure scenarios.


When you interact with the Azure Key Vault secret client library using the .NET SDK, errors returned by the service correspond to the same HTTP status codes returned for REST API requests.

For example, if you try to retrieve a secret that doesn't exist in your Azure Key Vault, a 404 error is returned, indicating Not Found.

    KeyVaultSecret secret = client.GetSecret("some_secret");
catch (RequestFailedException ex)

You will notice that additional information is logged, like the Client Request ID of the operation.

    Azure.RequestFailedException : Service request failed.
    Status: 404 (Not Found)
    {"error":{"code":"SecretNotFound","message":"Secret not found: some_secret"}}

    Cache-Control: no-cache
    Pragma: no-cache
    Server: Microsoft-IIS/10.0
    x-ms-keyvault-region: westus
    x-ms-request-id: 625f870e-10ea-41e5-8380-282e5cf768f2
    x-ms-keyvault-network-info: addr=;act_addr_fam=InterNetwork;
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Strict-Transport-Security: max-age=31536000;includeSubDomains
    X-Content-Type-Options: nosniff
    Date: Tue, 18 Jun 2019 16:02:11 GMT
    Content-Length: 75
    Content-Type: application/json; charset=utf-8
    Expires: -1

Next steps

Several Azure Key Vault secrets client library samples are available to you in this GitHub repository. These samples provide example code for additional scenarios commonly encountered while working with Azure Key Vault:

  • - for working with Azure Key Vault, including:

    • Create a secret
    • Get an existing secret
    • Update an existing secret
    • Delete secret
  • - contains the code snippets working with Azure Key Vault secrets, including:

    • Backup and recover a secret
  • - example code for working with Azure Key Vault secrets, including:

    • Create secrets
    • List all secrets in the Key Vault
    • Update secrets in the Key Vault
    • List versions of a specified secret
    • Delete secrets from the Key Vault
    • List deleted secrets in the Key Vault

Additional Documentation


See the for details on building, testing, and contributing to these libraries.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (219)

Showing the top 5 NuGet packages that depend on Azure.Security.KeyVault.Secrets:

Package Downloads

Microsoft.Extensions.Configuration.AzureAppConfiguration is a configuration provider for the .NET Core framework that allows developers to use Microsoft Azure App Configuration service as a configuration source in their applications.


This package brings certificate management for MSAL.NET.


Azure Key Vault configuration provider implementation for Microsoft.Extensions.Configuration.


The AKEless Build System for C#/.NET Signed by from repository '' commit '011956b31c05f14f3233f6241cd6fbe038824d71' (see contained AppVeyorSettings.json file for build settings).


HealthChecks.AzureKeyVault is the health check package for Azure Key Vault secrets

GitHub repositories (37)

Showing the top 5 popular GitHub repositories that depend on Azure.Security.KeyVault.Secrets:

Repository Stars
Cloud Native application framework for .NET
This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at or our versioned developer docs at
Enterprise HealthChecks for ASP.NET Core Diagnostics Package
An opinionated, cloud ready stack for building observable, production ready, distributed applications in .NET
A self-hosted Fuzzing-As-A-Service platform
Version Downloads Last updated
4.6.0 7,872,304 2/15/2024
4.6.0-beta.2 73,657 11/13/2023
4.6.0-beta.1 3,738 11/10/2023
4.5.0 26,905,559 3/14/2023
4.5.0-beta.1 194,806 11/9/2022
4.4.0 12,228,997 9/20/2022
4.3.0 32,874,697 3/26/2022
4.3.0-beta.4 95,508 1/13/2022
4.3.0-beta.2 76,725 10/14/2021
4.3.0-beta.1 231,241 8/11/2021
4.2.0 48,115,623 6/16/2021
4.2.0-beta.5 46,830 5/12/2021
4.2.0-beta.4 267,412 2/11/2021
4.2.0-beta.3 169,875 11/13/2020
4.2.0-beta.2 9,243 10/7/2020
4.2.0-beta.1 31,853 9/9/2020
4.1.0 65,554,423 8/12/2020
4.1.0-preview.1 103,758 3/10/2020
4.0.3 2,996,536 4/4/2020
4.0.2 10,524,759 3/4/2020
4.0.1 32,016,529 1/9/2020
4.0.0 1,677,224 10/31/2019
4.0.0-preview.5 2,269 10/8/2019
4.0.0-preview.4 1,100 9/11/2019
4.0.0-preview.3 3,155 8/9/2019
4.0.0-preview.2 443 8/6/2019
4.0.0-preview.1 1,318 6/28/2019