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
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/use-key-vault-references-dotnet-core.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,8 +51,8 @@ To do this tutorial, install the [.NET Core SDK](https://dotnet.microsoft.com/do
51
51
3. From the results list, select **Key Vault**.
52
52
4. In the **Key Vault** section, select **Create**.
53
53
5. In the **Create key vault** section, provide the following information:
54
-
-**Name**: A unique name is required. For this quickstart, enter **Contoso-vault2**.
55
-
-**Subscription**: Choose a subscription.
54
+
- A unique name is required. In the **Name** box, enter **Contoso-vault2**.
55
+
-In **Subscription**, choose a subscription.
56
56
- Under **Resource Group**, select **Create new** and enter a resource group name.
57
57
- In the **Location** drop-down menu, choose a location.
58
58
- Leave the other options with their default values.
@@ -64,11 +64,12 @@ At this point, your Azure account is the only one authorized to access this new
64
64
65
65
## Add a secret to Key Vault
66
66
67
-
To add a secret to the vault, you just need to take a couple of additional steps. In this case, add a message that you can use to test Key Vault retrieval. The message is called **Message** and we store the value of **Hello from Key Vault** in it.
67
+
To add a secret to the vault, you just need to take a couple of additional steps. In this case, add a message that you can use to test Key Vault retrieval. The message is called **Message** and you store the value of **Hello from Key Vault** in it.
68
68
69
69
1. On the **Key Vault** properties pages, select **Secrets**.
70
70
1. Select **Generate/Import**.
71
71
1. In the **Create a secret** window, enter the following values:
72
+
-**Upload options**: Enter **manual**.
72
73
-**Name**: Enter **Message**.
73
74
-**Value**: Enter **Hello from Key Vault**.
74
75
1. Leave the other properties with their default values.
@@ -136,7 +137,7 @@ To add a secret to the vault, you just need to take a couple of additional steps
136
137
using Microsoft.IdentityModel.Clients.ActiveDirectory;
137
138
```
138
139
139
-
1. Update the **CreateWebHostBuilder** method to use App Configuration by calling the **config.AddAzureAppConfiguration** method. Include the **UseAzureKeyVault** option, passing in a new **KeyVaultClient** reference to your Key Vault.
140
+
1. Update the `CreateWebHostBuilder` method to use App Configuration by calling the `config.AddAzureAppConfiguration` method. Include the `UseAzureKeyVault` option, passing in a new `KeyVaultClient` reference to your Key Vault.
140
141
141
142
```csharp
142
143
public static IWebHostBuilder CreateWebHostBuilder(string[] args) =>
@@ -159,7 +160,7 @@ To add a secret to the vault, you just need to take a couple of additional steps
159
160
.UseStartup<Startup>();
160
161
```
161
162
162
-
1. After you've passed the **KeyVaultClient** reference to the **UseAzureKeyVault** method when initializing the connection to App Configuration, you can access the values of Key Vault references in the same way you access the values of regular App Configuration keys. To see this process in action, open *Index.cshtml* in the **Views** > **Home** directory. Replace its content with the following code:
163
+
1. After you've passed the `KeyVaultClient` reference to the `UseAzureKeyVault` method when initializing the connection to App Configuration, you can access the values of Key Vault references in the same way you access the values of regular App Configuration keys. To see this process in action, open *Index.cshtml* in the **Views** > **Home** directory. Replace its contents with the following code:
163
164
164
165
```html
165
166
@using Microsoft.Extensions.Configuration
@@ -210,4 +211,3 @@ In this tutorial, you added an Azure managed service identity to streamline acce
0 commit comments