Skip to content

Commit 97fdf62

Browse files
Clarifying verbiage
Clarifying verbiage
1 parent 1d746b5 commit 97fdf62

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/key-vault-certs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ When you're using a restricted Key Vault, use the following steps to configure A
8181
> Steps 1-3 are not required if your Key Vault has a Private Endpoint enabled. The application gateway can access the Key Vault using the private IP address.
8282
8383
> [!Note]
84-
> If using Private Endpoints, you must associate the privatelink.vaultcore.azure.net private DNS zone to the virtual network containing Application Gateway. Custom DNS may be used on the virtual network instead of Azure DNS provided resolvers, however the private dns zone will need to remain associated to the virtual network as well.
84+
> If using Private Endpoints to access Key Vault, you must associate the privatelink.vaultcore.azure.net private DNS zone, containing the corresponding record to the referenced Key Vault, to the virtual network containing Application Gateway. Custom DNS servers may continue to be used on the virtual network instead of the Azure DNS provided resolvers, however the private dns zone will need to remain associated to the virtual network as well.
8585
8686
1. In the Azure portal, in your Key Vault, select **Networking**.
8787
1. On the **Firewalls and virtual networks** tab, select **Selected networks**.

0 commit comments

Comments
 (0)