internal vnet routing options

[nagendramishr]

[Enter feedback here]

The article indicates that there are solutions for routing with traffic manager and application gateway when using internal vnet, however it should be updated to clarify that in a purely internal setup, there are no options for multi-region routing and that customers need to find a third-party solution for that scenario. Traffic manager does not support private endpoints, and application gateway cannot be used to route to lowest latency backend.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: d7b2624c-40ea-c23c-3af5-79953d4cb549
• Version Independent ID: 0bf60c10-7ae4-476a-6cbd-4a189a97000f
• Content: Deploy Azure API Management instance to multiple Azure regions - Azure API Management
• Content Source: articles/api-management/api-management-howto-deploy-multi-region.md
• Service: api-management
• GitHub Login: @dlepow
• Microsoft Alias: danlep

[TPavanBalaji]

@nagendramishr Thanks for your feedback! We will investigate and update as appropriate.

[dlepow]

@nagendramishr - Thanks for the feedback and raising the issue. We have a work item planned in an upcoming doc sprint to point out this limitation in the internal mode. According to our usual process, I'll now proceed to close this issue. Thanks again!

please-close