Skip to content

Commit a7f5337

Browse files
alexwolfmsftalexwolfmsft
committed
passwordless updates
1 parent 46fe6fe commit a7f5337

File tree

3 files changed

+22
-20
lines changed

3 files changed

+22
-20
lines changed

‎articles/key-vault/certificates/quick-create-net.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
---
2-
title: Quickstart - Azure Key Vault certificates client library for .NET (version 4)
3-
description: Learn how to create, retrieve, and delete certificates from an Azure key vault using the .NET client library (version 4)
2+
title: Quickstart - Azure Key Vault certificates client library for .NET
3+
description: Learn how to create, retrieve, and delete certificates from an Azure key vault using the .NET client library
44
author: msmbaldwin
55
ms.author: mbaldwin
66
ms.date: 11/14/2022
77
ms.service: key-vault
88
ms.subservice: certificates
99
ms.topic: quickstart
1010
ms.devlang: csharp
11-
ms.custom: devx-track-csharp, mode-api
11+
ms.custom: devx-track-csharp, mode-api, passwordless-dotnet
1212
---
1313

14-
# Quickstart: Azure Key Vault certificate client library for .NET (SDK v4)
14+
# Quickstart: Azure Key Vault certificate client library for .NET
1515

1616
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
1717

@@ -131,9 +131,11 @@ using Azure.Security.KeyVault.Certificates;
131131

132132
### Authenticate and create a client
133133

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.
135135

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).
137139

138140
```csharp
139141
string keyVaultName = Environment.GetEnvironmentVariable("KEY_VAULT_NAME");

‎articles/key-vault/keys/quick-create-net.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
---
2-
title: Quickstart - Azure Key Vault keys client library for .NET (version 4)
3-
description: Learn how to create, retrieve, and delete keys from an Azure key vault using the .NET client library (version 4)
2+
title: Quickstart - Azure Key Vault keys client library for .NET
3+
description: Learn how to create, retrieve, and delete keys from an Azure key vault using the .NET client library
44
author: msmbaldwin
55
ms.author: mbaldwin
66
ms.date: 01/04/2023
77
ms.service: key-vault
88
ms.subservice: keys
99
ms.topic: quickstart
1010
ms.devlang: csharp
11-
ms.custom: devx-track-csharp, devx-track-azurepowershell, mode-api
11+
ms.custom: devx-track-csharp, devx-track-azurepowershell, mode-api, passwordless-dotnet
1212
---
1313

14-
# Quickstart: Azure Key Vault key client library for .NET (SDK v4)
14+
# Quickstart: Azure Key Vault key client library for .NET
1515

1616
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
1717

@@ -131,11 +131,9 @@ using Azure.Security.KeyVault.Keys;
131131

132132
### Authenticate and create a client
133133

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.
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.
135135

136-
Some Azure services also allow you to authorize requests using passwords, connection strings, or other credentials directly. However, these options should be used with caution. Developers must be diligent to never expose these secrets in an unsecure location. Anyone who gains access to the password or secret key is able to authenticate. `DefaultAzureCredential` offers improved management and security benefits to allow passwordless authentication and avoid these types of issues.
137-
138-
`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. 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).
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).
139137

140138
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).
141139

‎articles/key-vault/secrets/quick-create-net.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
---
2-
title: Quickstart - Azure Key Vault secrets client library for .NET (version 4)
3-
description: Learn how to create, retrieve, and delete secrets from an Azure key vault using the .NET client library (version 4)
2+
title: Quickstart - Azure Key Vault secrets client library for .NET
3+
description: Learn how to create, retrieve, and delete secrets from an Azure key vault using the .NET client library
44
author: msmbaldwin
55
ms.author: mbaldwin
66
ms.date: 09/23/2020
77
ms.service: key-vault
88
ms.subservice: secrets
99
ms.topic: quickstart
1010
ms.devlang: csharp
11-
ms.custom: devx-track-csharp, mode-api
11+
ms.custom: devx-track-csharp, mode-api, passwordless-dotnet
1212
---
1313

14-
# Quickstart: Azure Key Vault secret client library for .NET (SDK v4)
14+
# Quickstart: Azure Key Vault secret client library for .NET
1515

1616
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
1717

@@ -158,9 +158,11 @@ Add the following directives to the top of *Program.cs*:
158158

159159
### Authenticate and create a client
160160

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).
161+
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.
162162

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).
163+
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).
164+
165+
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).
164166

165167
[!code-csharp[](~/samples-key-vault-dotnet-quickstart/key-vault-console-app/Program.cs?name=authenticate)]
166168

0 commit comments

Comments
 (0)