Azure Traffic Manager, What It Does and How It's Different From Load Balancer

Every couple of months someone asks me whether they need Traffic Manager or Load Balancer for a setup that already runs fine out of one region. Most of the time the honest answer is neither. But when you actually do need one, it helps to understand they are not doing the same job at all, even though the names sound similar.

What Traffic Manager actually does

Load Balancer works inside a region, at the network level. It spreads traffic across VMs or instances that are already up and reachable on the same virtual network. Traffic Manager works at the DNS level, across regions or even across clouds. When someone types your domain into a browser, Traffic Manager decides which endpoint's IP address to hand back, before any connection is even made.

That distinction matters because Traffic Manager cannot inspect the actual request. It is not looking at HTTP headers or paths. It is answering a DNS query, so the routing decision happens once, and the client caches that answer for a while based on the DNS time to live you set.

The routing methods worth knowing

Traffic Manager gives you a handful of routing methods, and picking the right one is most of the work:

Priority routing sends everyone to your primary region and only fails over to a backup if health checks fail. This is the simplest disaster recovery setup you can build.

Performance routing sends users to whichever endpoint gives the lowest latency based on where their DNS query came from. Good for a genuinely global audience.

Weighted routing splits traffic by percentage across endpoints, useful for a staged rollout of a new region or a new App Service plan.

Geographic routing sends users to a specific endpoint based on their location, which comes up more often than you would expect for data residency requirements.

Where it fits next to Front Door

If you already read about Azure Front Door, you might wonder why both exist. Front Door works at Layer 7, terminates HTTPS, can look at the actual request path, and adds a web application firewall. Traffic Manager only ever does DNS. If your app needs URL based routing or WAF rules, Front Door is the better fit. If you just need failover or geo routing between a handful of regional deployments and do not need to inspect traffic, Traffic Manager is lighter weight and cheaper.

For most small setups running out of one region, none of this matters yet. It becomes worth setting up once downtime in a single region would actually cost you something.