Azure Traffic Manager is a DNS-based load balancer for distributing traffic globally across multiple Azure regions, other clouds, or on-premises locations.
What is Azure Traffic Manager?
Azure Traffic Manager is not a classic Layer 4/7 load balancer, but a DNS-level traffic router. When a client makes a DNS query, Traffic Manager responds with the IP address of the optimal endpoint based on the configured routing method. The client then connects directly to that endpoint — traffic itself does not flow through Traffic Manager.
Microsoft positions Traffic Manager as one of several load-balancing services in Azure: Application Gateway for Layer 7 load balancing within a region, Azure Load Balancer for Layer 4 load balancing within a region, Azure Front Door for global HTTP(S) routing with CDN/WAF, and Traffic Manager for global DNS-based routing. These services can be combined.
The service supports several routing methods, including Performance (routes to the region with lowest latency), Priority (active/passive failover), Weighted (proportional distribution, e.g. for canary deployments), Geographic (based on the client’s geographic location), Multivalue (returns multiple IPs for client-side selection), and Subnet (routing based on client IP range). Health checks continuously monitor all endpoints and automatically remove failed ones from DNS routing.
Core Features
- DNS-based global routing across multiple Azure regions, external endpoints, or on-premises infrastructure
- Multiple routing methods (Performance, Priority, Weighted, Geographic, Multivalue, Subnet), combinable via nested profiles
- Automatic endpoint health monitoring with HTTP, HTTPS, or TCP probes
- Support for non-Azure endpoints, enabling hybrid and multi-cloud scenarios
- Configurable DNS TTL to control failover speed
Typical Use Cases
Global High Availability with Automatic Failover
Priority routing with a primary region and one or more failover regions. Traffic Manager monitors endpoints via health checks and automatically routes to the next available region on failure.
Performance Optimization for Globally Distributed Users
Performance routing directs users to the region with the lowest measured network latency. Often combined with Azure Front Door for additional CDN capabilities.
Geographic Routing for Data Residency
Geographic routing can be used to direct users from specific regions to endpoints in specific countries or regions — for example, as part of data residency requirements. Whether this is sufficient for a particular use case needs to be assessed on a case-by-case legal basis.
Canary and Blue/Green Deployments
Weighted routing enables a gradual traffic shift between application versions, with the option for a fast rollback by adjusting the weighting.
Hybrid Cloud Scenarios
External endpoints allow routing to on-premises infrastructure or other cloud providers, for example for gradual migrations or backup scenarios.
Benefits
- Simple, cost-effective global routing without additional infrastructure components
- Works across providers via external endpoints
- Combinable with Azure Load Balancer, Application Gateway, and Azure Front Door for multi-layer architectures
- Automatic failover without manual intervention
Frequently Asked Questions about Azure Traffic Manager
What is the difference between Traffic Manager and Load Balancer?
Traffic Manager is DNS-based: it responds to DNS queries with the IP address of the optimal endpoint, and the client then connects directly. Azure Load Balancer and Application Gateway, by contrast, operate as a Layer 4 or Layer 7 proxy within a region, through which traffic actually flows. Traffic Manager is suited for global routing across regions, while Load Balancer/Application Gateway handle distribution within a region.
What does Azure Traffic Manager cost?
Traffic Manager is billed on a pay-per-use basis, based on the number of DNS queries and the number of monitored endpoints including health checks. Current exact pricing is available on the official Azure pricing page.
How fast is failover during an endpoint failure?
Failover time depends on the interplay of health check interval, configured DNS TTL, and client-side DNS caching, and typically ranges from seconds to a few minutes. For significantly faster failover, consider Azure Front Door.
Can Traffic Manager route traffic to other clouds?
Yes, via external endpoints Traffic Manager can also route to endpoints outside Azure, such as other cloud providers or on-premises infrastructure. Health checks also work for external endpoints.
Does Traffic Manager support HTTPS termination?
No, Traffic Manager is purely DNS-based and does not terminate application traffic. For HTTPS termination, WAF, or CDN capabilities, use Azure Front Door or Application Gateway in front of the actual endpoints.
How do I combine Traffic Manager with other Azure load-balancing services?
A common pattern is Traffic Manager as the top layer for global Geographic or Priority routing, directing traffic to regional Azure Front Door or Application Gateway instances, which in turn handle Layer 7 functions such as CDN, WAF, and load distribution within the region.
Integration with innFactory
As a Microsoft Solutions Partner, innFactory supports you in architecting globally available, highly available applications with Azure Traffic Manager. We help with selecting the right routing method, designing multi-region architectures and disaster recovery strategies, and integrating with Azure Front Door, Application Gateway, and Azure Load Balancer.
Contact us for a non-binding consultation on Azure Traffic Manager and Microsoft Azure.
Typical Use Cases
Note: All product information on this page has been compiled with care, but is provided without guarantee and may be outdated or incomplete. Cloud services evolve rapidly — features, pricing, SLAs, and availability change frequently. Authoritative and up-to-date information can only be found on the official product page of Azure (official documentation). This page does not represent an offer by Azure.
