An Azure service that provides a hybrid, multi-cloud management platform for APIs.
No. For a multi-region internal-mode API Management deployment, each region’s network must be configured independently, and the connectivity requirements in an added region are generally the same as in the primary region. For NSG rules, the documented requirement for port 3443 is the ApiManagement service tag for management traffic, and for multi-region deployments the guidance on regional service tags says each region’s NSG should allow traffic to the service tags for that region and the primary region.
Applied to gateway regions:
- Keep the inbound NSG rule allowing
ApiManagementto destination port3443. - In a multi-region deployment, do not rely on only the primary region’s regional service tag in secondary/gateway regions.
- If regional service tags are used as a best practice, the NSG in each secondary region should allow the relevant service tags for:
- the secondary region itself, and
- the primary region.
Also, in multi-region virtual network deployments, a public virtual IP address exists in every region and in internal VNet mode that public IP is used for management traffic on port 3443. That is another reason the gateway region must be independently reachable for management traffic.
So the safe supported configuration is not “primary region tag only” on gateway regions. The supported pattern is region-by-region NSG configuration, including the secondary region and the primary region where regional tags are used.