Azure Traffic Manager cost: DNS queries plus health checks

Quick answer

Traffic Manager bills per million DNS queries (around $0.54 per million for the first billion) plus a small monthly fee per monitored endpoint, with external (non-Azure) endpoints costing more to health-check. It is a cheap DNS-based global router; cost grows mainly with query volume and the number of monitored endpoints, so consolidate endpoints and rely on caching.

Azure Traffic Manager is a DNS-based global traffic router: it directs clients to the best endpoint using routing methods like performance, priority, or geographic, by answering DNS queries. Because it works at the DNS layer, its pricing is DNS queries plus endpoint health monitoring, and it is inexpensive.

Queries and endpoint monitoring

Dimension	Rate (approximate)
DNS queries	~$0.54 / million (first billion)
Azure endpoint health check	Small monthly fee per endpoint
External endpoint health check	Higher monthly fee per endpoint

You pay per million DNS queries answered, tiered down at high volume, plus a monthly fee for each endpoint Traffic Manager health-checks. Monitoring external (non-Azure) endpoints costs more per endpoint than Azure ones.

Where cost hides

For most deployments Traffic Manager is a few dollars a month. Cost grows with very high query volume, which longer DNS TTLs reduce by letting resolvers cache the answer so fewer queries reach Traffic Manager, and with a large number of monitored endpoints, each carrying a monthly health-check fee. Consolidating endpoints and setting sensible TTLs keeps it lean.

Traffic Manager vs Front Door

Traffic Manager routes at DNS and does not sit in the data path, so it is cheap but cannot do layer-7 features like caching, WAF, or TLS termination. Azure Front Door does those at higher cost by proxying traffic. For simple global DNS routing, Traffic Manager is the cheaper choice; for edge acceleration and layer-7 features, Front Door is the tool, the tradeoff in Front Door versus CDN.

FAQ

How is Azure Traffic Manager priced?

Per million DNS queries answered (around $0.54 per million for the first billion, tiered down above) plus a small monthly fee per monitored endpoint, with external non-Azure endpoints costing more to health-check than Azure ones. For most deployments it is a few dollars a month.

How do I reduce Traffic Manager cost?

Set sensible DNS TTLs so resolvers cache answers and fewer queries reach Traffic Manager, consolidate the number of monitored endpoints since each carries a monthly health-check fee, and prefer Azure endpoints over external ones where possible, as external checks cost more.

Does Traffic Manager charge per endpoint?

Yes, a small monthly fee for each endpoint it health-checks, with external (non-Azure) endpoints costing more than Azure ones. A large number of monitored endpoints is one of the two things (along with high query volume) that grows the bill.

Traffic Manager or Front Door?

Traffic Manager routes at the DNS layer and does not sit in the data path, so it is cheap but cannot cache, terminate TLS, or run a WAF. Front Door proxies traffic and adds those layer-7 features at higher cost. Use Traffic Manager for simple global DNS routing, Front Door for edge acceleration.

How do longer TTLs reduce Traffic Manager cost?

A longer DNS TTL lets resolvers cache Traffic Manager's answer for longer, so they route from cache instead of re-querying, reducing the number of billed DNS queries. Raise TTLs where fast failover or routing changes are not required.

Does C3X estimate Traffic Manager cost?

C3X prices the azurerm_traffic_manager_profile and its endpoints from your Terraform, so the endpoint monitoring fees appear before deploy. DNS query volume is a usage assumption you provide, and it is usually a small part of the bill.

What to do next

Price your global routing before you deploy. C3X reads your Terraform and prices Traffic Manager and the rest of your stack against a live catalog. Start with the quickstart.