Skip to content

Commit f3ff2a5

Browse files
Merge pull request #221405 from dlepow/tmroute
[APIM] Traffic Manager routing method
2 parents 90b860e + beb305a commit f3ff2a5

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

articles/api-management/api-management-howto-deploy-multi-region.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,8 +100,13 @@ To take advantage of geographical distribution of your system, you should have b
100100
</policies>
101101
```
102102

103-
> [!TIP]
104-
> You may also front your backend services with [Azure Traffic Manager](https://azure.microsoft.com/services/traffic-manager/), direct the API calls to the Traffic Manager, and let it resolve the routing automatically.
103+
### Use Traffic Manager for routing to regional backends
104+
105+
You may also front your backend services with [Azure Traffic Manager](https://azure.microsoft.com/services/traffic-manager/), direct the API calls to the Traffic Manager, and let it resolve the routing automatically.
106+
107+
* For traffic distribution and failover, we recommend using Traffic Manager with the [**Geographic**](../traffic-manager/traffic-manager-routing-methods.md#geographic-traffic-routing-method) routing method. We don't recommend using Traffic Manager with the Weighted routing method with API Management backends.
108+
109+
* For traffic control during maintenance operations, we recommend using the Priority routing method.
105110

106111
## <a name="custom-routing"> </a>Use custom routing to API Management regional gateways
107112

0 commit comments

Comments
 (0)