Traffic manager in Azure

Traffic manager in Azure

Azure Traffic Manager

Microsoft Azure Traffic Manager enables you to control how user traffic is distributed to application endpoints hosted across multiple datacenters worldwide. It helps improve availability, performance, and resilience by intelligently directing users to the most appropriate service endpoint.

How Azure Traffic Manager Works

Azure Traffic Manager operates at the DNS level:

  • It uses DNS responses to direct end-user requests to the optimal endpoint.

  • Supported endpoints include:

    • Azure Virtual Machines

    • Azure App Services

    • Azure Cloud Services

    • External, non-Azure endpoints

  • After Traffic Manager selects an endpoint, clients connect directly to that service.

  • Continuous health monitoring ensures traffic is routed only to healthy endpoints.

  • Automatic failover protects applications even during a full regional outage.


Benefits of Azure Traffic Manager

Improve application availability

Traffic Manager continuously monitors endpoint health and automatically redirects traffic when an endpoint becomes unavailable, ensuring high availability for critical workloads.

Improve application performance

By routing users to the endpoint with the lowest network latency, Traffic Manager reduces response times and improves the overall user experience for global applications.

Perform maintenance without downtime

You can redirect traffic away from endpoints during upgrades or planned maintenance, allowing seamless updates with no user disruption.

Support hybrid and multi-cloud architectures

Traffic Manager supports external endpoints, making it ideal for hybrid cloud and on-premises deployments.

Support large and complex deployments

Using nested Traffic Manager profiles, you can combine multiple routing methods to build advanced and flexible traffic distribution strategies.


Traffic Manager Routing Methods

Priority Routing

  • Endpoints are ordered by priority.

  • All traffic is sent to the primary endpoint.

  • If the primary endpoint becomes unavailable, traffic automatically fails over to the next endpoint.

  • Ideal for active/passive disaster recovery scenarios.


Performance Routing

  • Routes users to the endpoint with the lowest network latency.

  • Latency is measured using Azure’s Internet Latency Table, not physical distance.

  • Best suited for global, performance-sensitive applications.


Geographic Routing

  • Traffic is routed based on the geographic location of the user.

  • Each geographic region can be assigned to only one endpoint.

  • Useful for:

    • Regulatory compliance

    • Data residency requirements

    • Region-specific content delivery


Weighted Routing

  • Traffic is distributed according to assigned weights (1–1000).

  • Higher weight = higher percentage of traffic.

  • Commonly used for:

    • A/B testing

    • Gradual rollouts

    • Load distribution across endpoints


Additional Routing Methods

  • MultiValue routing: Returns multiple healthy IPv4 and IPv6 endpoints.

  • Subnet routing: Routes traffic based on source IP address ranges.


Comparing Azure Traffic Distribution Services

Service Azure Load Balancer Application Gateway Traffic Manager
Technology Layer 4 (Transport) Layer 7 (Application) DNS-based
Protocols TCP, UDP HTTP, HTTPS, HTTP/2, WebSockets DNS
Backends VMs, VM Scale Sets VMs, VM Scale Sets, App Services, IPs, Hostnames Cloud Services, App Services, App Service Slots, Public IPs
Connectivity Internal & External Internal & External External only

Key Takeaway

Azure Traffic Manager is a global traffic distribution solution that complements Azure Load Balancer and Application Gateway. While Load Balancer and Application Gateway manage traffic within a region, Traffic Manager directs traffic across regions using intelligent DNS routing.