Merge pull request #100054 from CawaMS/master

address feedback https://github.com/MicrosoftDocs/azure-docs/issues/4…

Author: PRMerger7

articles/key-vault/vs-secure-secret-appsettings.md

@@ -39,17 +39,18 @@ If you are developing a project and need to share source code securely, use [Azu
     ![Create Azure Key Vault](./media/vs-secure-secret-appsettings/create-keyvault.PNG)
 
 2. Grant you and your team members access to the Key Vault. If you have a large team, you can create an [Azure Active Directory group](../active-directory/active-directory-groups-create-azure-portal.md) and add that security group access to the Key Vault. In the *Secret Permissions* dropdown, check *Get* and *List* under *Secret Management Operations*.
+If you already have your web app created, grant the web app access to the Key Vault so it can access the key vault without storing secret configuration in App Settings or files. Search for your web app by its name and add it the same way you grant users access.
 
     ![Add Key Vault access policy](./media/vs-secure-secret-appsettings/add-keyvault-access-policy.png)
 
 3. Add your secret to Key Vault on the Azure portal. For nested configuration settings, replace ':' with '--' so the Key Vault secret name is valid. ':' is not allowed to be in the name of a Key Vault secret.
 
     ![Add Key Vault secret](./media/vs-secure-secret-appsettings/add-keyvault-secret.png)
 
-    > [!NOTE] 
+    > [!NOTE]
     > Prior to Visual Studio 2017 V15.6 we used to recommend installing the Azure Services Authentication extension for Visual Studio. But it is deprecated now as the functionality is integrated within the Visual Studio . Hence if you are on an older version of visual Studio 2017 , we suggest you to update to at least VS 2017 15.6 or up so that you can use this functionality natively and access the Key-vault from using the Visual Studio sign-in Identity itself.
     >
- 
+
 4. Add the following NuGet packages to your project:
 
     ```