Skip to content

Commit cbba5be

Browse files
authored
Merge pull request #88141 from ankanjan/patch-1
Add Azure Purview as a trusted service for Azure Key Vault
2 parents 67bc5a2 + 68fc331 commit cbba5be

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/key-vault/general/overview-vnet-service-endpoints.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,7 @@ Here's a list of trusted services that are allowed to access a key vault if the
5454
|Azure Container Registry|[Registry encryption using customer-managed keys](../../container-registry/container-registry-customer-managed-keys.md)
5555
|Azure Application Gateway |[Using Key Vault certificates for HTTPS-enabled listeners](../../application-gateway/key-vault-certs.md)
5656
|Azure Front Door|[Using Key Vault certificates for HTTPS](../../frontdoor/front-door-custom-domain-https.md#prepare-your-azure-key-vault-account-and-certificate)
57+
|Azure Purview|[Using credentials for source authentication in Azure Purview](../../purview/manage-credentials.md)
5758

5859
> [!NOTE]
5960
> You must set up the relevant Key Vault access policies to allow the corresponding services to get access to Key Vault.

0 commit comments

Comments
 (0)