Skip to content

Commit f9094eb

Browse files
committed
APIM: expand on public IPs in VNET
1 parent 9f59c27 commit f9094eb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/api-management/api-management-howto-ip-addresses.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ In [multi-regional deployments](api-management-howto-deploy-multi-region.md), ea
5757

5858
If your API Management service is inside a virtual network, it will have two types of IP addresses - public and private.
5959

60-
Public IP addresses are used for internal communication on port `3443` - for managing configuration (for example, through Azure Resource Manager). Additionally, when a request is sent from API Management to a public-facing (Internet-facing) backend, a public IP address will be visible as the origin of the request.
60+
Public IP addresses are used for internal communication on port `3443` - for managing configuration (for example, through Azure Resource Manager). In the external VNET configuration, they are also used for runtime API traffic. When a request is sent from API Management to a public-facing (Internet-facing) backend, a public IP address will be visible as the origin of the request.
6161

6262
Private virtual IP (VIP) addresses are used to connect from within the network to API Management endpoints - gateways, the developer portal, and the management plane for direct API access. You can use them for setting up DNS records within the network.
6363

0 commit comments

Comments
 (0)