Skip to content

Commit c0f383e

Browse files
authored
Merge pull request #112211 from PoojithaJujjavarapu/patch-1
Update api-management-multi-region-concepts.md
2 parents e7437b7 + d5cdb5d commit c0f383e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

includes/api-management-multi-region-concepts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.author: danlep
1111

1212
* Gateway configurations such as APIs and policy definitions are regularly synchronized between the primary and secondary regions you add. Multi-region deployment provides availability of the API gateway in more than one region and provides service availability if one region goes offline.
1313

14-
* When API Management receives public HTTP requests to the primary gateway endpoint, traffic is routed to a regional gateway based on lowest latency, which can reduce latency experienced by geographically distributed API consumers.
14+
* When API Management receives public HTTP requests to the traffic manager endpoint (applies for the external VNet and non-networked modes of API Management), traffic is routed to a regional gateway based on lowest latency, which can reduce latency experienced by geographically distributed API consumers.
1515

1616
* If a region goes offline, API requests are automatically routed around the failed region to the next closest gateway.
1717

0 commit comments

Comments
 (0)