Direct answer: at Azure Traffic Manager public list prices on 11 November 2026 (USD, excluding tax and discounts), the first 1 billion DNS queries per month cost $0.54/million and queries above 1 billion cost $0.375/million; basic health checks are $0.36/Azure endpoint/month and $0.54/external endpoint/month; fast-probe add-ons are +$1/month (Azure) and +$2/month (external); HTTPS-check add-ons are +$1/month (Azure) and +$2/month (external); nested endpoints are $10 each/month; and Traffic View is $2/million data points (data points are queries). That makes 1 million queries + 3 Azure endpoints with basic checks = $1.62/month; 100 million queries + 10 Azure endpoints = $57.60/month; the same 10 endpoints with fast+HTTPS = $77.60/month; 100 million queries + 10 Azure endpoints with basic checks + Traffic View = $257.60/month (with fast+HTTPS, $277.60). Traffic Manager itself is cheap; the budget risks are Traffic View, per-endpoint fast/HTTPS checks, external endpoints and nested endpoints.
This guide is for architects, SRE, network/platform engineering, finance and procurement doing multi-region failover/geo-routing, comparing Traffic Manager with Front Door/Application Gateway/Load Balancer, or reacting to a Traffic View bill. It separates official prices, editorial calculations and exclusions, covering query tiers, endpoint checks, fast/HTTPS/nested/Traffic View, combined TCO, the Front Door boundary and a 90-day checklist. Prices come from the Traffic Manager pricing page, Azure Retail Prices API and Microsoft Learn overview/routing/monitoring docs (11 November 2026). This is not procurement advice.
(1) Traffic Manager bills DNS queries, not HTTP requests; client caching cuts queries, but a long TTL slows failover. (2) Checks and add-ons multiply by endpoint: 10 Azure endpoints with fast+HTTPS is $23.60/month, the same external endpoints are $45.40. (3) Traffic View is the biggest variable: $2/million data points is 3.7× the $0.54/million query fee; it turns 100M queries from $57.60 into $257.60 (or $277.60 with fast+HTTPS endpoints).
Billing model: queries, endpoints and add-ons
Traffic Manager is a DNS-level load balancer: it charges for incoming DNS queries plus a health-check fee per monitored endpoint; fast probes (10 seconds) and HTTPS checks are per-endpoint add-ons; nested endpoints (a Traffic Manager profile used as another profile's endpoint) are charged per endpoint; Traffic View charges per processed data point, which currently means queries. Azure and external endpoints have different prices: basic checks $0.36 vs $0.54, fast/HTTPS add-ons $1 vs $2. The price table has a first-1-billion and an over-1-billion query band; the page does not list a separate free query allowance.
| Item | Unit price | Billing unit | Note |
|---|---|---|---|
| DNS queries (first 1B/month) | $0.54 | Per million | Queries received by the profile |
| DNS queries (above 1B/month) | $0.375 | Per million | About 30.6% lower marginal price |
| Azure endpoint basic check | $0.36 | Per endpoint/month | 30-second default probe |
| External endpoint basic check | $0.54 | Per endpoint/month | Non-Azure Internet endpoint |
| Fast-probe add-on | $1 (Azure) / $2 (external) | Per endpoint/month | 10-second probe |
| HTTPS-check add-on | $1 (Azure) / $2 (external) | Per endpoint/month | Checks certificate presence, not validity |
| Nested endpoint | $10 | Each/month | Profile as another profile's endpoint |
| Traffic View | $2 | Per million data points | Data points are queries |
Sources: Traffic Manager pricing page and Retail API (11 November 2026). USD global service; excludes tax and discounts; fast probing must be bought on top of basic checks; Traffic View is customer-enabled.
Query tiers: from 1 million to 2 billion
Query fees are small: 1 million = $0.54, 10 million = $5.40, 100 million = $54, 1 billion = $540; above 1 billion the next band is $0.375/million, so 2 billion = $540 + $375 = $915. Endpoints and add-ons move the bill more: with 10 Azure endpoints and basic checks, endpoint fees are $3.60/month; the same 10 endpoints with fast+HTTPS become $23.60/month; external endpoints $45.40/month. At low query volume, endpoint fees can exceed query fees; at high volume, queries become the main line.
| Queries/month | Query fee | 10 Azure basic | 10 Azure full add-ons | 10 external full add-ons |
|---|---|---|---|---|
| 1M | $0.54 | $4.14 | $24.14 | $45.94 |
| 10M | $5.40 | $9.00 | $29.00 | $50.80 |
| 100M | $54.00 | $57.60 | $77.60 | $99.40 |
| 1B | $540.00 | $543.60 | $563.60 | $585.40 |
| 2B | $915.00 | $918.60 | $938.60 | $960.40 |
Editorial calculation: query fees cumulative across the two bands; endpoint fee = 10×(basic+add-ons); excludes Traffic View, nested endpoints, tax and discounts. External: basic $0.54, fast $2, HTTPS $2.
Endpoint checks: Azure vs external, basic vs fast/HTTPS
Health checks drive automatic failover: default probing is 30 seconds, tolerating 3 failures, with a 10-second timeout; fast probing is 10 seconds with a 9-second timeout and costs extra. Protocols are HTTP/HTTPS/TCP; HTTPS checks only confirm that a certificate is present, not that it is valid, so they are not certificate-expiry monitoring. Because checks bill per endpoint, many regions/endpoints add up: 10 Azure endpoints are $3.60/month basic, $23.60 with fast+HTTPS; external endpoints are $45.40 for the same configuration. Confirm each endpoint really needs its own check and fast probing.
| Endpoint type | Basic/month | Fast add-on/month | HTTPS add-on/month | 10 endpoints, all on |
|---|---|---|---|---|
| Azure | $0.36 | $1.00 | $1.00 | $23.60 |
| External | $0.54 | $2.00 | $2.00 | $45.40 |
| Nested endpoint | $10.00 each/month (plus the nested profile's own queries/checks) | $100.00 (10) | ||
Sources: Traffic Manager pricing page and monitoring doc (11 November 2026). Fast probing requires basic checks; HTTPS checks do not validate certificates; nested endpoints also incur their inner profile's queries/checks.
Traffic View: $2/million, easily larger than queries
Traffic View bills per processed data point, and the official footnote says data points are currently the queries Traffic Manager receives; at $2/million it is 3.7× the $0.54/million query fee. At 100 million queries: without Traffic View the bill is $57.60/month (10 Azure endpoints, basic checks); enabling it adds $200, for $257.60/month; with fast+HTTPS on all 10 endpoints it becomes $277.60/month. Traffic View suits troubleshooting/visibility periods; don't enable it by default for all traffic—turn it on on demand, narrow the scope, or put long-term visualization elsewhere.
| Scenario | Query fee | Endpoint fee | Traffic View | Total/month |
|---|---|---|---|---|
| 10M queries + 5 Azure basic | $5.40 | $1.80 | $0 | $7.20 |
| 10M queries + 5 Azure basic + View | $5.40 | $1.80 | $20.00 | $27.20 |
| 100M queries + 10 Azure basic | $54.00 | $3.60 | $0 | $57.60 |
| 100M queries + 10 Azure basic + View | $54.00 | $3.60 | $200.00 | $257.60 |
| 100M queries + 10 Azure full add-ons + View | $54.00 | $23.60 | $200.00 | $277.60 |
| 10 nested endpoints + 100M queries + 10 Azure basic | $54.00 | $3.60 + $100 | $0 | $157.60 |
Editorial calculation: Traffic View = queries × $2/million; nested endpoints $10 each; excludes the nested profiles' own queries/checks, tax and discounts; bills follow actual usage.
Traffic Manager vs Front Door/Application Gateway/Load Balancer
Traffic Manager only does DNS-level global routing; it does not proxy traffic, terminate TLS, provide WAF or act as a CDN. That makes it cheap, but failover depends on DNS TTL and client caching. For HTTP acceleration, WAF, SSL offload or path routing, use Front Door (global L7) or Application Gateway (regional L7); for regional L4, use Load Balancer. Traffic Manager's advantages are any protocol, Azure/external/on-premises endpoints and per-query billing; for plain multi-region DNS failover or geo-routing it is usually cheaper than Front Door's base fee + requests + egress. They can be combined: Front Door as the HTTP entry, Traffic Manager for an outer DNS failover layer.
| Option | Layer | Fit | Cost basis |
|---|---|---|---|
| Traffic Manager | Global DNS | Multi-region failover, geo/priority/weighted/performance routing, non-HTTP | Queries + endpoint checks + add-ons |
| Front Door | Global L7 | HTTP acceleration, WAF, SSL, path routing | Base fee + requests + egress |
| Application Gateway | Regional L7 | Regional HTTP entry, WAF, URL routing | Gateway hours + capacity units |
| Load Balancer | Regional L4 | TCP/UDP, internal/public L4 | Rules/hours + data processing |
Editorial summary, not a vendor recommendation; Front Door/Application Gateway/Load Balancer prices are covered in their own cost guides; Traffic Manager does not proxy data-plane traffic, so origin egress is separate.
Hidden costs and 90-day checklist
Eight hidden costs: Traffic View at $2/million (can exceed query fees), fast/HTTPS add-ons multiplied by endpoint, higher external-endpoint rates, $10 per nested endpoint, a long TTL slowing failover, a short TTL raising query volume, origin egress/bandwidth billed separately, and the need for Front Door/App Gateway when HTTP acceleration/WAF is required. 90 days: weeks 1–2 inventory profiles, endpoint types, monthly queries and TTL; weeks 2–3 decide which endpoints need fast/HTTPS checks; weeks 3–4 price queries + endpoints + add-ons and list Traffic View separately; weeks 4–6 run failover drills and measure switch time versus TTL/probe interval; weeks 6–8 compare Front Door/App Gateway HTTP capabilities and total price; weeks 8–10 remove idle endpoints/nested profiles and turn off unused Traffic View; weeks 10–12 reconcile the bill and set query/endpoint alerts.
| Scenario | First choice | Check first |
|---|---|---|
| Multi-region DNS failover | Traffic Manager | TTL, probe interval |
| Geo/priority/weighted routing | Traffic Manager | Routing method, endpoint count |
| Non-HTTP protocols | Traffic Manager | TCP checks |
| HTTP acceleration/WAF/SSL | Front Door or App Gateway | Base + requests + egress |
| Regional L4 | Load Balancer | Rules/data processing |
| Query visualization needed | Traffic View on demand | $2/M, don't default to all traffic |
| Many external/nested endpoints | Consolidate first | External $0.54+$2/$2; nested $10 |
Editorial summary, not a vendor recommendation; capabilities/prices follow official pages; excludes origins, bandwidth, WAF, certificates and labour.
FAQ
How is Traffic Manager billed?
DNS queries (first 1B $0.54/M, above $0.375/M) + a health check per endpoint (Azure $0.36/month, external $0.54/month) + optional add-ons (fast probe $1/$2, HTTPS $1/$2) + nested endpoints $10 each + Traffic View $2/million data points.
What does 1 million queries cost per month?
Queries are $0.54; with 3 Azure endpoints on basic checks add $1.08, for $1.62/month. The more endpoints and add-ons, the more endpoint fees can exceed query fees.
What is the gap between Azure and external endpoints?
Basic checks are $0.36 vs $0.54; fast-probe add-ons are $1 vs $2; HTTPS add-ons are $1 vs $2. With 10 endpoints all on, Azure is $23.60/month and external $45.40/month.
How much are fast probes and HTTPS checks?
Fast probing (10 seconds) adds $1 (Azure)/$2 (external) per endpoint on top of basic checks; HTTPS checks are the same $1/$2. HTTPS checks only confirm that a certificate is present, not that it is valid.
Why is Traffic View expensive?
Traffic View is $2/million data points, and data points are currently queries; queries themselves are $0.54/million, so View is 3.7× the query fee. At 100M queries it adds $200/month; enable it on demand.
How are nested endpoints billed?
Each nested endpoint is $10/month, plus the nested profile's own queries and checks. Ten nested endpoints cost $100/month, potentially more than 100M queries ($54); avoid deep hierarchies.
Is there a free query allowance?
The price table has first-1-billion and over-1-billion bands and does not list a separate free query allowance; Real User Measurements are currently listed at $0 but only support Azure regions and require enabling. Check the bill for the actual charge.
How do I reduce cost?
Five steps: (1) set TTL to balance caching and failover speed; (2) remove idle endpoints to cut per-endpoint fees; (3) enable fast/HTTPS add-ons only where needed; (4) turn on Traffic View on demand, not by default for all traffic; (5) compare Front Door/App Gateway when you need HTTP acceleration/WAF instead of forcing Traffic Manager to do it.
Research method and limitations
Official facts (pricing page, Retail API, Learn overview/routing/monitoring docs): two DNS-query bands, Azure/external endpoint checks, fast/HTTPS add-ons, nested endpoints, Traffic View data points = queries, six routing methods, 30/10-second probes, 3 tolerated failures, TTL's effect on failover, and HTTPS checks not validating certificates. Editorial calculations: cumulative query bands, endpoint fees × endpoints, add-ons × endpoints, Traffic View = queries × $2/million; query volume, endpoint count, add-ons and Traffic View usage are editorial assumptions.
Seven limitations: (1) USD list prices only, excluding tax/contract discounts/regional differences; (2) query volume, endpoint count, add-ons and Traffic View usage are editorial assumptions; (3) excludes origins/bandwidth/egress, DNS hosting, certificates, WAF and labour; (4) no real failover/probe-latency benchmark; (5) enterprise-agreement terms for Traffic Manager were not reviewed; (6) billing for add-ons such as Real User Measurements follows the bill; (7) prices/features change—recheck official pages and bills before purchase.
Sources and basis
- Microsoft Azure, Traffic Manager Pricing: azure.microsoft.com/en-us/pricing/details/traffic-manager. Two query bands, endpoint checks, fast/HTTPS add-ons, nested endpoints, Traffic View, Real User Measurements. Accessed 11 November 2026.
- Azure Retail Prices API (productName eq Traffic Manager): prices.azure.com/api/retail/prices. Queries $0.54/$0.375 per million, Azure checks $0.36, external $0.54, fast/HTTPS $1/$2, nested $10, Traffic View $2/million. Accessed 11 November 2026.
- Microsoft Learn, Azure Traffic Manager overview: traffic-manager-overview. DNS-level routing, endpoint types, boundary with Front Door/Application Gateway/Load Balancer. Accessed 11 November 2026.
- Microsoft Learn, Traffic Manager routing methods: traffic-manager-routing-methods. Priority/Weighted/Performance/Geographic/Multivalue/Subnet. Accessed 11 November 2026.
- Microsoft Learn, Traffic Manager endpoint monitoring: traffic-manager-monitoring. 30/10-second probes, 3 tolerated failures, TTL/failover, HTTPS checks not validating certificates. Accessed 11 November 2026.
Data cut-off 11 November 2026; prices/features follow Microsoft official pages and bills; this is not procurement, architecture or legal advice.