Virtual network configuration reference: API Management
For VNet connectivity options, requirements, and considerations, see Using a virtual network with Azure API Management.
Control inbound and outbound traffic into the subnet in which API Management is deployed by using network security group rules. If certain ports are unavailable, API Management may not operate properly and may become inaccessible.
When an API Management service instance is hosted in a VNet, the ports in the following table are used. Some requirements differ depending on the version (
stv1) of the compute platform hosting your API Management instance.
Bold items in the Purpose column indicate port configurations required for successful deployment and operation of the API Management service. Configurations labeled "optional" enable specific features, as noted. They are not required for the overall health of the service.
We recommend using service tags instead of IP addresses in NSG rules to specify network sources and destinations. Service tags prevent downtime when infrastructure improvements necessitate IP address changes.
stv2, it is required to assign a Network Security Group to your VNet in order for the Azure Load Balancer to work. Learn more in the Azure Load Balancer documentation.
|Source / Destination Port(s)||Direction||Transport protocol||Service tags
Source / Destination
|* / , 443||Inbound||TCP||Internet / VirtualNetwork||Client communication to API Management||External only|
|* / 3443||Inbound||TCP||ApiManagement / VirtualNetwork||Management endpoint for Azure portal and PowerShell||External & Internal|
|* / 443||Outbound||TCP||VirtualNetwork / Storage||Dependency on Azure Storage||External & Internal|
|* / 443||Outbound||TCP||VirtualNetwork / AzureActiveDirectory||Azure Active Directory and Azure Key Vault dependency (optional)||External & Internal|
|* / 443||Outbound||TCP||VirtualNetwork / AzureConnectors||Authorizations dependency (optional)||External & Internal|
|* / 1433||Outbound||TCP||VirtualNetwork / Sql||Access to Azure SQL endpoints||External & Internal|
|* / 443||Outbound||TCP||VirtualNetwork / AzureKeyVault||Access to Azure Key Vault||External & Internal|
|* / 5671, 5672, 443||Outbound||TCP||VirtualNetwork / EventHub||Dependency for Log to Azure Event Hubs policy and Azure Monitor (optional)||External & Internal|
|* / 445||Outbound||TCP||VirtualNetwork / Storage||Dependency on Azure File Share for GIT (optional)||External & Internal|
|* / 1886, 443||Outbound||TCP||VirtualNetwork / AzureMonitor||Publish Diagnostics Logs and Metrics, Resource Health, and Application Insights (optional)||External & Internal|
|* / 6380||Inbound & Outbound||TCP||VirtualNetwork / VirtualNetwork||Access external Azure Cache for Redis service for caching policies between machines (optional)||External & Internal|
|* / 6381 - 6383||Inbound & Outbound||TCP||VirtualNetwork / VirtualNetwork||Access internal Azure Cache for Redis service for caching policies between machines (optional)||External & Internal|
|* / 4290||Inbound & Outbound||UDP||VirtualNetwork / VirtualNetwork||Sync Counters for Rate Limit policies between machines (optional)||External & Internal|
|* / 6390||Inbound||TCP||AzureLoadBalancer / VirtualNetwork||Azure Infrastructure Load Balancer||External & Internal|
Regional service tags
NSG rules allowing outbound connectivity to Storage, SQL, and Azure Event Hubs service tags may use the regional versions of those tags corresponding to the region containing the API Management instance (for example, Storage.WestUS for an API Management instance in the West US region). In multi-region deployments, the NSG in each region should allow traffic to the service tags for that region and the primary region.
To enable TLS/SSL certificate chain building and validation, the API Management service needs outbound network connectivity on ports
csp.digicert.com. This dependency is not required if any certificate you upload to API Management contains the full chain to the CA root.
Outbound access on port
53 is required for communication with DNS servers. If a custom DNS server exists on the other end of a VPN gateway, the DNS server must be reachable from the subnet hosting API Management.
Azure Active Directory integration
To operate properly, the API Management service needs outbound connectivity on port 443 to the following endpoints associated with Azure Active Directory:
Metrics and health monitoring
Outbound network connectivity to Azure Monitoring endpoints, which resolve under the following domains, are represented under the AzureMonitor service tag for use with Network Security Groups.
|Microsoft Azure operated by 21Vianet||
Developer portal CAPTCHA
Allow outbound network connectivity for the developer portal's CAPTCHA, which resolves under the hosts
Publishing the developer portal
Enable publishing the developer portal for an API Management instance in a VNet by allowing outbound connectivity to blob storage in the West US region. For example, use the Storage.WestUS service tag in an NSG rule. Currently, connectivity to blob storage in the West US region is required to publish the developer portal for any API Management instance.
Azure portal diagnostics
When using the API Management diagnostics extension from inside a VNet, outbound access to
dc.services.visualstudio.com on port
443 is required to enable the flow of diagnostic logs from Azure portal. This access helps in troubleshooting issues you might face when using the extension.
Azure load balancer
You're not required to allow inbound requests from service tag
AzureLoadBalancer for the Developer SKU, since only one compute unit is deployed behind it. However, inbound connectivity from
AzureLoadBalancer becomes critical when scaling to a higher SKU, such as Premium, because failure of the health probe from load balancer then blocks all inbound access to the control plane and data plane.
When adding virtual machines running Windows to the VNet, allow outbound connectivity on port
1688 to the KMS endpoint in your cloud. This configuration routes Windows VM traffic to the Azure Key Management Services (KMS) server to complete Windows activation.
Internal infrastructure and diagnostics
The following settings and FQDNs are required to maintain and diagnose API Management's internal compute infrastructure.
- Allow outbound UDP access on port
- Allow outbound TCP access on port
- Allow outbound access on port
443to the following endpoints for internal diagnostics:
- Allow outbound access on port
443to the following endpoint for internal PKI:
- Allow outbound access on ports
443to the following endpoints for Windows Update:
- Allow outbound access on ports
443to the endpoint
- Allow outbound access on port
443to the following endpoints for Windows Defender:
Control plane IP addresses
The following IP addresses are divided by Azure Environment and Region. In some cases, two IP addresses are listed. Permit both IP addresses.
Control plane IP addresses should be configured for network access rules only when needed in certain networking scenarios. We recommend using the ApiManagement service tag instead of control plane IP addresses to prevent downtime when infrastructure improvements necessitate IP address changes.
|Azure Environment||Region||IP address|
|Azure Public||Australia Central||22.214.171.124|
|Azure Public||Australia Central 2||126.96.36.199|
|Azure Public||Australia East||188.8.131.52|
|Azure Public||Australia Southeast||184.108.40.206|
|Azure Public||Brazil South||220.127.116.11, 18.104.22.168|
|Azure Public||Brazil Southeast||22.214.171.124|
|Azure Public||Canada Central||126.96.36.199, 188.8.131.52|
|Azure Public||Canada East||184.108.40.206|
|Azure Public||Central India||220.127.116.11, 18.104.22.168|
|Azure Public||Central US||22.214.171.124|
|Azure Public||Central US EUAP||126.96.36.199|
|Azure Public||East Asia||188.8.131.52|
|Azure Public||East US||184.108.40.206|
|Azure Public||East US 2||220.127.116.11|
|Azure Public||East US 2 EUAP||18.104.22.168|
|Azure Public||France Central||22.214.171.124|
|Azure Public||France South||126.96.36.199|
|Azure Public||Germany North||188.8.131.52|
|Azure Public||Germany West Central||184.108.40.206, 220.127.116.11|
|Azure Public||Japan East||18.104.22.168|
|Azure Public||Japan West||22.214.171.124|
|Azure Public||India Central||126.96.36.199|
|Azure Public||India West||188.8.131.52|
|Azure Public||Korea Central||184.108.40.206, 220.127.116.11|
|Azure Public||Korea South||18.104.22.168|
|Azure Public||North Central US||22.214.171.124|
|Azure Public||North Europe||126.96.36.199|
|Azure Public||Norway East||188.8.131.52|
|Azure Public||Norway West||184.108.40.206|
|Azure Public||South Africa North||220.127.116.11, 18.104.22.168|
|Azure Public||South Africa West||22.214.171.124|
|Azure Public||South Central US||126.96.36.199, 188.8.131.52|
|Azure Public||South India||184.108.40.206|
|Azure Public||Southeast Asia||220.127.116.11|
|Azure Public||Switzerland North||18.104.22.168, 22.214.171.124|
|Azure Public||Switzerland West||126.96.36.199|
|Azure Public||UAE Central||188.8.131.52|
|Azure Public||UAE North||184.108.40.206|
|Azure Public||UK South||220.127.116.11|
|Azure Public||UK West||18.104.22.168|
|Azure Public||West Central US||22.214.171.124|
|Azure Public||West Europe||126.96.36.199|
|Azure Public||West India||188.8.131.52|
|Azure Public||West US||184.108.40.206|
|Azure Public||West US 2||220.127.116.11|
|Azure Public||West US 3||18.104.22.168|
|Microsoft Azure operated by 21Vianet||China North (Global)||22.214.171.124|
|Microsoft Azure operated by 21Vianet||China East (Global)||126.96.36.199|
|Microsoft Azure operated by 21Vianet||China North||188.8.131.52|
|Microsoft Azure operated by 21Vianet||China East||184.108.40.206|
|Microsoft Azure operated by 21Vianet||China North 2||220.127.116.11|
|Microsoft Azure operated by 21Vianet||China East 2||18.104.22.168|
|Azure Government||USGov Virginia (Global)||22.214.171.124|
|Azure Government||USGov Texas (Global)||126.96.36.199|
|Azure Government||USGov Virginia||188.8.131.52|
|Azure Government||USGov Iowa||184.108.40.206|
|Azure Government||USGov Arizona||220.127.116.11|
|Azure Government||USGov Texas||18.104.22.168|
|Azure Government||USDoD Central||22.214.171.124|
|Azure Government||USDoD East||126.96.36.199|
Learn more about: