AzureAzure Traffic ManagerNetworking

azurerm_traffic_manager_profile cost estimation

DNS-based global load balancing billed per million DNS queries plus per monitored endpoint. 10M queries with 2 endpoints is ~$6/month.

An azurerm_traffic_manager_profile provides DNS-based global traffic routing — directing users to endpoints by performance, priority, weighting, or geography. Because it works at the DNS layer (not in the data path), it's inexpensive: cost is per million DNS queries (~$0.54/million for the first billion) plus a small per-monitored-endpoint health-check fee (Azure endpoints are cheaper to monitor than external ones). 10M queries with 2 Azure endpoints is ~$6/month.

The key cost property is that Traffic Manager doesn't process your traffic — it only answers DNS queries telling clients which endpoint to use. So cost scales with DNS query volume (driven by client count and DNS TTL, not data throughput) and the number of endpoints you health-check, both of which are modest for typical deployments.

The levers are minor: a sensible DNS TTL reduces query volume (clients cache the answer longer), and you only pay health-check fees for endpoints you actually monitor. There's rarely much to optimize — it's one of the cheaper ways to do global routing, far less than data-path global load balancers like Front Door.

c3x prices the profile from query volume and endpoint count as usage, so projected cost can be modelled.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "azurerm_traffic_manager_profile" "global" {
  name                   = "global-routing"
  resource_group_name    = azurerm_resource_group.main.name
  traffic_routing_method = "Performance"

  dns_config {
    relative_name = "myapp"
    ttl           = 60
  }

  monitor_config {
    protocol = "HTTPS"
    port     = 443
    path     = "/health"
  }
}

Pricing dimensions

What you actually pay for when you provision azurerm_traffic_manager_profile.

DimensionUnitWhat's being charged
DNS queriesper millionDNS queries answered, ~$0.54/million (first billion). Scales with client count and DNS TTL, not data throughput.
~$0.54/million → 10M queries ≈ $5.40/month
Monitored endpointsper endpoint-monthHealth-check fee per monitored endpoint; Azure endpoints are cheaper to monitor than external ones.

Sample C3X output

10M DNS queries + 2 Azure endpoints monitored in a month:

azurerm_traffic_manager_profile.global
├─ DNS queries (10M)        10 × 1M       $5.40
└─ Monitored endpoints (2)  2 endpoints   $0.72
                            Monthly       $6.12

Optimization tips

Common ways to reduce azurerm_traffic_manager_profile cost without changing the workload.

Use a sensible DNS TTL

Proportional to query reduction

Query volume is driven by how often clients re-resolve, which the DNS TTL controls. A longer TTL means clients cache the answer longer and query less — lowering query cost — at the cost of slower failover reaction. Balance the two.

Monitor only the endpoints you need

Per endpoint not monitored

Each monitored endpoint carries a small health-check fee, and external (non-Azure) endpoints cost more to monitor. Health-check the endpoints in your routing, not extras.

Prefer Traffic Manager for DNS-level routing

Large vs a data-path load balancer

If you only need global routing/failover at the DNS layer, Traffic Manager is far cheaper than a data-path global load balancer like Front Door (which adds base fees plus per-request and egress charges). Use Front Door only when you need its L7/CDN/WAF features.

FAQ

How is Azure Traffic Manager billed?

Per million DNS queries (~$0.54/million for the first billion) plus a small per-monitored-endpoint health-check fee. It routes at the DNS layer and doesn't process your traffic, so it's cheap — 10M queries with 2 endpoints is ~$6/month.

Why is Traffic Manager so much cheaper than Front Door?

Traffic Manager works at DNS — it just tells clients which endpoint to use, then steps out of the data path. Front Door is an inline global load balancer (L7 routing, WAF, CDN) that processes every request and charges base fees plus per-request and egress. Use Traffic Manager for pure routing/failover.

How does c3x estimate the cost?

Traffic Manager is usage-driven, so c3x models it from DNS query volume and monitored-endpoint count in c3x-usage.yml. There's no standing data-path fee.

Related resources

Azure
azurerm_dns_zone

DNS hosting that pairs with Traffic Manager routing

Estimate this resource in your own Terraform

Free, open source, no API key. C3X parses your Terraform and shows line-item cost for every resource, including azurerm_traffic_manager_profile.

Get StartedStar on GitHub
← Browse all Azure resources