You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/key-vault/general/overview-vnet-service-endpoints.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,7 @@ Here's a list of trusted services that are allowed to access a key vault if the
54
54
|Azure Container Registry|[Registry encryption using customer-managed keys](../../container-registry/container-registry-customer-managed-keys.md)
55
55
|Azure Application Gateway |[Using Key Vault certificates for HTTPS-enabled listeners](../../application-gateway/key-vault-certs.md)
56
56
|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)
57
58
58
59
> [!NOTE]
59
60
> You must set up the relevant Key Vault access policies to allow the corresponding services to get access to Key Vault.
0 commit comments