

Traffic Manager doesn't see the HTTP(S) traffic. The browser connects directly to the endpoint. Traffic Manager resolves DNS queries based on a choice of six routing methods. The public endpoints of the AppGWs serve as the backend endpoints of Traffic Manager. Traffic Manager resolves DNS queries for the application to the public IP addresses of the Application Gateway (AppGW) endpoints. WorkflowĪzure Traffic Manager uses DNS-based routing to load balance incoming traffic across the two regions. Architectureĭownload a Visio file of this architecture. It features DNS-based global load balancing, two forms of regional load balancing, and global virtual network peering to create a high availability architecture that can withstand a regional outage. This architecture is for global, internet-facing applications that use HTTP(S) and TCP protocols.
