Merge pull request #218560 from cljung/cljung-vc-post-ga-08

Correction of errors on permissions and key vault

Author: prmerger-automator[bot]

articles/active-directory/verifiable-credentials/verifiable-credentials-configure-issuer.md

@@ -144,9 +144,6 @@ Now that you have a new credential, you're going to gather some information abou
 
 1. Copy your **Tenant ID**, and record it for later. The Tenant ID is the guid in the manifest URL highlighted in red above.
 
-    >[!NOTE]
-    > When setting up access policies for Azure Key Vault, you must add the access policies for both **Verifiable Credentials Service Request** and **Verifiable Credentials Service**.
-
 ## Download the sample code
 
 The sample application is available in .NET, and the code is maintained in a GitHub repository. Download the sample code from [GitHub](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet), or clone the repository to your local machine:

articles/active-directory/verifiable-credentials/verifiable-credentials-configure-tenant.md

@@ -137,7 +137,7 @@ To add the required permissions, follow these steps:
 
 1. Select **APIs my organization uses**.
 
-1. Search for the **Verifiable Credentials Service Request** and **Verifiable Credentials Service** service principals, and select them.
+1. Search for the **Verifiable Credentials Service Request** service principal and select it.
 
     :::image type="content" source="media/verifiable-credentials-configure-tenant/add-app-api-permissions-select-service-principal.png" alt-text="Screenshot that shows how to select the service principal.":::
 
@@ -159,14 +159,15 @@ You can choose to grant issuance and presentation permissions separately if you
 1. Navigate to the Verified ID service in the Azure portal.  
 1. Select **Registration**.
 1. Notice that there are two sections:
-    1. Website ID registration
-    1. Domain verification.
+    1. DID registration
+    1. Domain ownership verification.
 1. Select on each section and download the JSON file under each.
 1. Create a website that you can use to distribute the files. If you specified **https://contoso.com** as your domain, the URLs for each of the files would look as shown below:
     - `https://contoso.com/.well-known/did.json`
     - `https://contoso.com/.well-known/did-configuration.json`
 
 Once that you have successfully completed the verification steps, you are ready to continue to the next tutorial.
+If you have selected ION as the trust system, you will not see the DID registration section as it is not applicable for ION and you only have to distribute the did-configuration.json file. 
 
 ## Next steps