You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Quickstart: Azure Key Vault certificate client library for .NET
15
15
16
16
Get started with the Azure Key Vault certificate client library for .NET. [Azure Key Vault](../general/overview.md) is a cloud service that provides a secure store for certificates. You can securely store keys, passwords, certificates, and other secrets. Azure key vaults may be created and managed through the Azure portal. In this quickstart, you learn how to create, retrieve, and delete certificates from an Azure key vault using the .NET client library
17
17
@@ -26,7 +26,7 @@ For more information about Key Vault and certificates, see:
26
26
## Prerequisites
27
27
28
28
* An Azure subscription - [create one for free](https://azure.microsoft.com/free/dotnet)
29
-
*[.NET Core 3.1 SDK or later](https://dotnet.microsoft.com/download/dotnet-core)
29
+
*[.NET 6 SDK or later](https://dotnet.microsoft.com/download)
30
30
*[Azure CLI](/cli/azure/install-azure-cli)
31
31
* A Key Vault - you can create one using [Azure portal](../general/quick-create-portal.md), [Azure CLI](../general/quick-create-cli.md), or [Azure PowerShell](../general/quick-create-powershell.md).
32
32
@@ -89,7 +89,7 @@ From the command shell, install the Azure Key Vault certificate client library f
For this quickstart, you'll also need to install the Azure SDK client library for Azure Identity:
92
+
For this quickstart, you'll also need to install the Azure Identity client library:
93
93
94
94
```dotnetcli
95
95
dotnet add package Azure.Identity
@@ -131,9 +131,11 @@ using Azure.Security.KeyVault.Certificates;
131
131
132
132
### Authenticate and create a client
133
133
134
-
In this quickstart, logged in user is used to authenticate to key vault, which is preferred method for local development. For applications deployed to Azure, managed identity should be assigned to App Service or Virtual Machine, for more information, see [Managed Identity Overview](../../active-directory/managed-identities-azure-resources/overview.md).
134
+
Application requests to most Azure services must be authorized. Using the [DefaultAzureCredential](/dotnet/azure/sdk/authentication#defaultazurecredential) class provided by the [Azure Identity client library](/dotnet/api/overview/azure/identity-readme)is the recommended approach for implementing passwordless connections to Azure services in your code. `DefaultAzureCredential` supports multiple authentication methods and determines which method should be used at runtime. This approach enables your app to use different authentication methods in different environments (local vs. production) without implementing environment-specific code.
135
135
136
-
In below example, the name of your key vault is expanded to the key vault URI, in the format "https://\<your-key-vault-name\>.vault.azure.net". This example is using ['DefaultAzureCredential()'](/dotnet/api/azure.identity.defaultazurecredential) class from [Azure Identity Library](/dotnet/api/overview/azure/identity-readme), which allows to use the same code across different environments with different options to provide identity. For more information about authenticating to key vault, see [Developer's Guide](../general/developers-guide.md#authenticate-to-key-vault-in-code).
136
+
In this quickstart, `DefaultAzureCredential` authenticates to key vault using the credentials of the local development user logged into the Azure CLI. When the application is deployed to Azure, the same `DefaultAzureCredential` code can automatically discover and use a managed identity that is assigned to an App Service, Virtual Machine, or other services. For more information, see [Managed Identity Overview](/azure/active-directory/managed-identities-azure-resources/overview).
137
+
138
+
In this example, the name of your key vault is expanded to the key vault URI, in the format `https://<your-key-vault-name>.vault.azure.net`. For more information about authenticating to key vault, see [Developer's Guide](/azure/key-vault/general/developers-guide#authenticate-to-key-vault-in-code).
# Quickstart: Azure Key Vault key client library for .NET
15
15
16
16
Get started with the Azure Key Vault key client library for .NET. [Azure Key Vault](../general/overview.md) is a cloud service that provides a secure store for cryptographic keys. You can securely store cryptographic keys, passwords, certificates, and other secrets. Azure key vaults may be created and managed through the Azure portal. In this quickstart, you learn how to create, retrieve, and delete keys from an Azure key vault using the .NET key client library
17
17
@@ -26,7 +26,7 @@ For more information about Key Vault and keys, see:
26
26
## Prerequisites
27
27
28
28
* An Azure subscription - [create one for free](https://azure.microsoft.com/free/dotnet)
29
-
*[.NET Core 3.1 SDK or later](https://dotnet.microsoft.com/download/dotnet-core)
29
+
*[.NET 6 SDK or later](https://dotnet.microsoft.com/download)
30
30
*[Azure CLI](/cli/azure/install-azure-cli)
31
31
* A Key Vault - you can create one using [Azure portal](../general/quick-create-portal.md), [Azure CLI](../general/quick-create-cli.md), or [Azure PowerShell](../general/quick-create-powershell.md).
32
32
@@ -89,7 +89,7 @@ From the command shell, install the Azure Key Vault key client library for .NET:
89
89
dotnet add package Azure.Security.KeyVault.Keys
90
90
```
91
91
92
-
For this quickstart, you'll also need to install the Azure SDK client library for Azure Identity:
92
+
For this quickstart, you'll also need to install the Azure Identity client library:
93
93
94
94
```dotnetcli
95
95
dotnet add package Azure.Identity
@@ -131,13 +131,15 @@ using Azure.Security.KeyVault.Keys;
131
131
132
132
### Authenticate and create a client
133
133
134
-
In this quickstart, logged in user is used to authenticate to key vault, which is preferred method for local development. For applications deployed to Azure, managed identity should be assigned to App Service or Virtual Machine, for more information, see [Managed Identity Overview](/azure/active-directory/managed-identities-azure-resources/overview).
134
+
Application requests to most Azure services must be authorized. Using the [DefaultAzureCredential](/dotnet/azure/sdk/authentication#defaultazurecredential) class provided by the [Azure Identity client library](/dotnet/api/overview/azure/identity-readme)is the recommended approach for implementing passwordless connections to Azure services in your code. `DefaultAzureCredential` supports multiple authentication methods and determines which method should be used at runtime. This approach enables your app to use different authentication methods in different environments (local vs. production) without implementing environment-specific code.
135
135
136
-
In this example, the name of your key vault is expanded to the key vault URI, in the format `https://<your-key-vault-name>.vault.azure.net`. This example is using ['DefaultAzureCredential()'](/dotnet/api/azure.identity.defaultazurecredential) class from [Azure Identity Library](/dotnet/api/overview/azure/identity-readme), which allows to use the same code across different environments with different options to provide identity. Fore more information about authenticating to key vault, see [Developer's Guide](/azure/key-vault/general/developers-guide#authenticate-to-key-vault-in-code).
136
+
In this quickstart, `DefaultAzureCredential` authenticates to key vault using the credentials of the local development user logged into the Azure CLI. When the application is deployed to Azure, the same `DefaultAzureCredential` code can automatically discover and use a managed identity that is assigned to an App Service, Virtual Machine, or other services. For more information, see [Managed Identity Overview](/azure/active-directory/managed-identities-azure-resources/overview).
137
+
138
+
In this example, the name of your key vault is expanded to the key vault URI, in the format `https://<your-key-vault-name>.vault.azure.net`. For more information about authenticating to key vault, see [Developer's Guide](/azure/key-vault/general/developers-guide#authenticate-to-key-vault-in-code).
# Quickstart: Azure Key Vault secret client library for .NET
15
15
16
16
Get started with the Azure Key Vault secret client library for .NET. [Azure Key Vault](../general/overview.md) is a cloud service that provides a secure store for secrets. You can securely store keys, passwords, certificates, and other secrets. Azure key vaults may be created and managed through the Azure portal. In this quickstart, you learn how to create, retrieve, and delete secrets from an Azure key vault using the .NET client library
17
17
@@ -26,10 +26,9 @@ For more information about Key Vault and secrets, see:
26
26
## Prerequisites
27
27
28
28
* An Azure subscription - [create one for free](https://azure.microsoft.com/free/dotnet)
29
-
*[.NET Core 3.1 SDK or later](https://dotnet.microsoft.com/download/dotnet-core)
* A Key Vault - you can create one using [Azure portal](../general/quick-create-portal.md)[Azure CLI](../general/quick-create-cli.md), or [Azure PowerShell](../general/quick-create-powershell.md)
29
+
*[.NET 6 SDK or later](https://dotnet.microsoft.com/download)
30
+
*[Azure CLI](/cli/azure/install-azure-cli) or [Azure PowerShell](/powershell/azure/install-az-ps)
31
+
* A Key Vault - you can create one using [Azure portal](../general/quick-create-portal.md), [Azure CLI](../general/quick-create-cli.md), or [Azure PowerShell](../general/quick-create-powershell.md)
33
32
34
33
This quickstart is using `dotnet` and Azure CLI or Azure PowerShell.
35
34
@@ -121,7 +120,7 @@ From the command shell, install the Azure Key Vault secret client library for .N
For this quickstart, you'll also need to install the Azure SDK client library for Azure Identity:
123
+
For this quickstart, you'll also need to install the Azure Identity client library:
125
124
126
125
```dotnetcli
127
126
dotnet add package Azure.Identity
@@ -158,9 +157,11 @@ Add the following directives to the top of *Program.cs*:
158
157
159
158
### Authenticate and create a client
160
159
161
-
In this quickstart, logged in user is used to authenticate to key vault, which is preferred method for local development. For applications deployed to Azure, managed identity should be assigned to App Service or Virtual Machine, for more information, see [Managed Identity Overview](../../active-directory/managed-identities-azure-resources/overview.md).
160
+
Application requests to most Azure services must be authorized. Using the [DefaultAzureCredential](/dotnet/azure/sdk/authentication#defaultazurecredential) class provided by the [Azure Identity client library](/dotnet/api/overview/azure/identity-readme)is the recommended approach for implementing passwordless connections to Azure services in your code. `DefaultAzureCredential` supports multiple authentication methods and determines which method should be used at runtime. This approach enables your app to use different authentication methods in different environments (local vs. production) without implementing environment-specific code.
162
161
163
-
In below example, the name of your key vault is expanded to the key vault URI, in the format "https://\<your-key-vault-name\>.vault.azure.net". This example is using ['DefaultAzureCredential()'](/dotnet/api/azure.identity.defaultazurecredential) class from [Azure Identity Library](/dotnet/api/overview/azure/identity-readme), which allows to use the same code across different environments with different options to provide identity. For more information about authenticating to key vault, see [Developer's Guide](../general/developers-guide.md#authenticate-to-key-vault-in-code).
162
+
In this quickstart, `DefaultAzureCredential` authenticates to key vault using the credentials of the local development user logged into the Azure CLI. When the application is deployed to Azure, the same `DefaultAzureCredential` code can automatically discover and use a managed identity that is assigned to an App Service, Virtual Machine, or other services. For more information, see [Managed Identity Overview](/azure/active-directory/managed-identities-azure-resources/overview).
163
+
164
+
In this example, the name of your key vault is expanded to the key vault URI, in the format `https://<your-key-vault-name>.vault.azure.net`. For more information about authenticating to key vault, see [Developer's Guide](/azure/key-vault/general/developers-guide#authenticate-to-key-vault-in-code).
0 commit comments