Merge pull request #219702 from ghogen/main

Update Visual Studio Key Vault article for VS 2022

Author: v-shils

articles/key-vault/general/vs-key-vault-add-connected-service.md

@@ -7,121 +7,51 @@ manager: jillfra
 ms.service: key-vault
 ms.custom: "vs-azure, devx-track-csharp"
 ms.topic: how-to
-ms.date: 08/07/2019
+ms.date: 11/14/2022
 ms.author: ghogen
 ---
 # Add Key Vault to your web application by using Visual Studio Connected Services
 
 In this tutorial, you will learn how to easily add everything you need to start using Azure Key Vault to manage your secrets for web projects in Visual Studio, whether you are using ASP.NET Core or any type of ASP.NET project. By using the Connected Services feature in Visual Studio, you can have Visual Studio automatically add all the NuGet packages and configuration settings you need to connect to Key Vault in Azure.
 
-For details on the changes that Connected Services makes in your project to enable Key Vault, see [Key Vault Connected Service - What happened to my ASP.NET 4.7.1 project](#how-your-aspnet-framework-project-is-modified) or [Key Vault Connected Service - What happened to my ASP.NET Core project](#how-your-aspnet-core-project-is-modified).
+For details on the changes that Connected Services makes in your project to enable Key Vault, see [Key Vault Connected Service - What happened to my ASP.NET project](#how-your-aspnet-framework-project-is-modified) or [Key Vault Connected Service - What happened to my ASP.NET Core project](#how-your-aspnet-core-project-is-modified).
 
 ## Prerequisites
 
 - **An Azure subscription**. If you don't have a subscription, sign up for a [free account](https://azure.microsoft.com/pricing/free-trial/).
 - **Visual Studio 2019 version 16.3** or later [Download it now](https://aka.ms/vsdownload?utm_source=mscom&utm_campaign=msdocs).
 
-
 ## Add Key Vault support to your project
 
-Before you begin, make sure that you're signed into Visual Studio. Sign in with the same account that you use for your Azure subscription. Then open an ASP.NET 4.7.1 or later, or ASP.NET Core 2.0 web project, and do the follow steps:
+Before you begin, make sure that you're signed into Visual Studio. Sign in with the same account that you use for your Azure subscription. Then open an ASP.NET 4.7.1 or later, or ASP.NET Core web project, and do the following steps. The steps shown are for Visual Studio 2022 version 17.4. The flow might be slightly different for other versions of Visual Studio.
 
-1. In **Solution Explorer**, right-click the project that you want to add the Key Vault support to, and choose **Add** > **Connected Service** > **Add**.
+1. In **Solution Explorer**, right-click the project that you want to add the Key Vault support to, and choose **Add** > **Connected Service**. Under **Service Dependencies**, choose the **+** icon.
    The Connected Service page appears with services you can add to your project.
 1. In the menu of available services, choose **Azure Key Vault** and click **Next**.
 
    ![Choose "Azure Key Vault"](../media/vs-key-vault-add-connected-service/key-vault-connected-service.png)
 
-1. Select the subscription you want to use, and then choose a existing Key Vault and click **Finish**. 
-
-   ![Select your subscription](../media/vs-key-vault-add-connected-service/key-vault-connected-service-select-vault.png)
-
-Now, connection to Key Vault is established and you can access your secrets in code. The next steps are different depending on whether you are using ASP.NET 4.7.1 or ASP.NET Core.
-
-## Access your secrets in code (ASP.NET Core)
-
-1. Open one of the page files, such as *Index.cshtml.cs* and write the following code:
-   1. Include a reference to `Microsoft.Extensions.Configuration` by this using directive:
-
-       ```csharp
-       using Microsoft.Extensions.Configuration;
-       ```
-
-   1. Add the configuration variable.
-
-      ```csharp
-      private static IConfiguration _configuration;
-      ```
-
-   1. Add this constructor or replace the existing constructor with this:
-
-       ```csharp
-       public IndexModel(IConfiguration configuration)
-       {
-           _configuration = configuration;
-       }
-       ```
-
-   1. Update the `OnGet` method. Update the placeholder value shown here with the secret name you created in the above commands.
-
-       ```csharp
-       public void OnGet()
-       {
-           ViewData["Message"] = "My key val = " + _configuration["<YourSecretNameStoredInKeyVault>"];
-       }
-       ```
-
-   1. To confirm the value at runtime, add code to display `ViewData["Message"]` to the *.cshtml* file to display the secret in a message.
-
-      ```cshtml
-          <p>@ViewData["Message"]</p>
-      ```
-
-You can run the app locally to verify that the secret is obtained successfully from the Key Vault.
-
-## Access your secrets (ASP.NET)
-You can set up the configuration so that the web.config file has a dummy value in the `appSettings` element that is replaced by the true value at runtime. You can then access this via the `ConfigurationManager.AppSettings` data structure.
-
-1. In Solution Explorer, right-click on your project, and select Manage NuGet Packages. In the Browse tab, locate and install [Microsoft.Configuration.ConfigurationBuilders.Azure](https://www.nuget.org/packages/Microsoft.Configuration.ConfigurationBuilders.Azure/)
- 
-1. Open your web.config file, and write the following code:
-    1. Add `configSections` and `configBuilders`:
-        ```xml
-         <configSections>
-            <section
-                name="configBuilders"
-                type="System.Configuration.ConfigurationBuildersSection, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
-                restartOnExternalChanges="false"
-                requirePermission="false" />
-         </configSections>
-         <configBuilders>
-            <builders>
-            <add
-                    name="AzureKeyVault"
-                    vaultName="vaultname"
-                    type="Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder, Microsoft.Configuration.ConfigurationBuilders.Azure, Version=1.0.0.0, Culture=neutral"
-                    vaultUri="https://vaultname.vault.azure.net" />
-            </builders>
-         </configBuilders>
-        ```
-    1. Find the appSettings tag, add an attribute `configBuilders="AzureKeyVault"`, and add a line:
-        ```xml
-         <add key="<secretNameInYourKeyVault>" value="dummy"/>
-        ```
-
-1. Edit the `About` method in *HomeController.cs*, to display the value for confirmation.
-
-   ```csharp
-   public ActionResult About()
-   {
-       ViewBag.Message = "Key vault value = " + ConfigurationManager.AppSettings["<secretNameInYourKeyVault>"];
-   }
-   ```
-1. Run the app locally under the debugger, switch to the **About** tab, and verify that the value from the Key Vault is displayed.
+1. Select the subscription you want to use, and then if you already have a Key Vault you want to use, select it and click **Next**.
+
+   ![Screenshot Select your subscription](../media/vs-key-vault-add-connected-service/key-vault-connected-service-select-vault.png)
+
+1. If you don't have an existing Key Vault, click on **Create new Key Vault**. You'll be asked to provide the resource group, location, and SKU.
+
+   ![Screenshot of "Create Azure Key Vault" screen](../media/vs-key-vault-add-connected-service/create-new-key-vault.png)
+
+1. In the **Configure Key Vault** screen, you can change the name of the environment variable.
+
+   ![Screenshot of Connect to Azure Key Vault screen.](../media/vs-key-vault-add-connected-service/connect-to-azure-key-vault.png)
+
+1. Click **Next** to review a summary of the changes and then **Finish**.
+
+Now, connection to Key Vault is established and you can access your secrets in code. If you just created a new key vault, test it by creating a secret that you can reference in code. You can create a secret by using the [Azure portal](../secrets/quick-create-portal.md), [PowerShell](../secrets/quick-create-powershell.md), or the [Azure CLI](../secrets/quick-create-cli.md).
+
+See code examples of working with secrets at [Azure Key Vault Secrets client library for .NET - Code examples](../secrets/quick-create-net.md?tabs=azure-cli#code-examples).
 
 ## Troubleshooting
 
-If your Key Vault is running on an different Microsoft account than the one you're logged in to Visual Studio (for example, the Key Vault is running on your work account, but Visual Studio is using your private account) you get an error in your Program.cs file, that Visual Studio can't get access to the Key Vault. To fix this issue:
+If your Key Vault is running on a different Microsoft account than the one you're logged in to Visual Studio (for example, the Key Vault is running on your work account, but Visual Studio is using your private account) you get an error in your Program.cs file, that Visual Studio can't get access to the Key Vault. To fix this issue:
 
 1. Go to the [Azure portal](https://portal.azure.com) and open your Key Vault.
 
@@ -200,4 +130,4 @@ Affects the project file .NET references and `packages.config` (NuGet references
 
 If you followed this tutorial, your Key Vault permissions are set up to run with your own Azure subscription, but that might not be desirable for a production scenario. You can create a managed identity to manage Key Vault access for your app. See [How to Authenticate to Key Vault](./authentication.md) and [Assign a Key Vault access policy](./assign-access-policy-portal.md).
 
-Learn more about Key Vault development by reading the [Key Vault Developer's Guide](developers-guide.md).
+Learn more about Key Vault development by reading the [Key Vault Developer's Guide](developers-guide.md).