Merge pull request #70392 from helizabethwhite/patch-1

[Purview] Updates instructions to include updated scope of req'd permissions

Author: ktoliver

articles/purview/manage-credentials.md

@@ -62,7 +62,7 @@ Before you can create a Credential, first associate one or more of your existing
 
 4. In the **Secrets permissions** dropdown, select **Get** and **List** permissions.
 
-5. For **Select principal**, choose the Purview managed identity.
+5. For **Select principal**, choose the Purview managed identity. You can search for the Purview MSI using either the Purview instance name **or** the managed identity application ID. We do not currently support compound identities (managed identity name + application ID).
 
    :::image type="content" source="media/manage-credentials/add-access-policy.png" alt-text="Add access policy":::
 

articles/purview/media/manage-credentials/add-access-policy.png

@@ -47,7 +47,10 @@ Verify that the correct permissions have been configured for the Purview managed
 To verify this, do the following steps:
 
 1. Navigate to your key vault and to the **Access policies** section
-1. Verify that your Purview managed identity shows under the *Current access policies* section with **get** and **list** permissions on secrets at least
+
+1. Verify that your Purview managed identity shows under the *Current access policies* section with at least **Get** and **List** permissions on Secrets
+
+   :::image type="content" source="./media/troubleshoot-connections/verify-minimum-permissions.png" alt-text="Image showing dropdown selection of both Get and List permission options":::
 
 If you don't see your Purview managed identity listed, then follow the steps in [Create and manage credentials for scans](manage-credentials.md) to add it.