Skip to content

Commit f3b9442

Browse files
authored
Update api-management-howto-ip-addresses.md
Clarify public IP in internal VNet
1 parent 1d339a1 commit f3b9442

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
@@ -51,7 +51,7 @@ In [multi-regional deployments](api-management-howto-deploy-multi-region.md), ea
5151

5252
If your API Management service is inside a virtual network, it will have two types of IP addresses: public and private.
5353

54-
* 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.
54+
* 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. In the *internal* VNet configuration, public IP addresses are only used for Azure internal management operations and don't expose your instance to the internet.
5555

5656
* Private virtual IP (VIP) addresses, available **only** in the [internal VNet mode](api-management-using-with-internal-vnet.md), 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.
5757

0 commit comments

Comments
 (0)