Skip to content

Commit 5f698d2

Browse files
author
gitName
committed
review comment
1 parent 3618082 commit 5f698d2

File tree

2 files changed

+2
-18
lines changed

2 files changed

+2
-18
lines changed

articles/api-management/inject-vnet-v2.md

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -103,15 +103,7 @@ When you [create](get-started-create-service-instance.md) a Premium v2 instance
103103

104104
When a Premium v2 API Management instance is injected in a virtual network, you have to manage your own DNS to enable inbound access to API Management.
105105

106-
While you have the option to use a private or custom DNS server, we recommend:
107-
108-
1. Configure an Azure [DNS private zone](../dns/private-dns-overview.md).
109-
1. Link the Azure DNS private zone to the virtual network.
110-
111-
Learn how to [set up a private zone in Azure DNS](../dns/private-dns-getstarted-portal.md).
112-
113-
> [!NOTE]
114-
> When the instance is injected into a virtual network with a private or custom DNS resolver, you must ensure name resolution for Azure Key Vault endpoints (`*.vault.azure.net`). We recommend configuring an Azure private DNS zone, which doesn't require this additional configuration.
106+
[!INCLUDE [api-management-virtual-network-dns-resolver](../../includes/api-management-virtual-network-dns-resolver.md)]
115107

116108
### Endpoint access on default hostname
117109

articles/api-management/virtual-network-workspaces-resources.md

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -91,15 +91,7 @@ Configure other NSG rules to meet your organization's network access requirement
9191

9292
For virtual network injection, you have to manage your own DNS to enable inbound access to your workspace gateway.
9393

94-
While you have the option to use a private or custom DNS server, we recommend:
95-
96-
1. Configure an Azure [DNS private zone](../dns/private-dns-overview.md).
97-
1. Link the Azure DNS private zone to the virtual network into which you've deployed your workspace gateway.
98-
99-
Learn how to [set up a private zone in Azure DNS](../dns/private-dns-getstarted-portal.md).
100-
101-
> [!NOTE]
102-
> When the workspace gateway is injected into a virtual network with a private or custom DNS resolver, you must ensure name resolution for Azure Key Vault endpoints (`*.vault.azure.net`). We recommend configuring an Azure private DNS zone, which doesn't require this additional configuration.
94+
[!INCLUDE [api-management-virtual-network-dns-resolver](../../includes/api-management-virtual-network-dns-resolver.md)]
10395

10496
### Access on default hostname
10597

0 commit comments

Comments
 (0)