Traffic Manager pricing

Geo-route incoming traffic to your app for better performance and availability

Traffic Manager billing is based on the following pricing dimensions:

  1. The number of DNS queries received, with a discount for services receiving more than 1 billion monthly queries.
  2. The number of monitored endpoints. The rate depends on (1) whether it’s an Azure or external service and (2) how frequently you want Traffic Manager to monitor the endpoint.
  3. The number of real user measurements received by the Traffic Manager service.
  4. The number of data points used to generate Traffic View outputs.

Pricing details

Traffic Manager billing is based on the number of DNS queries received, with a discount for services receiving more than 1 billion monthly queries. We also charge for each monitored endpoint (the rate depends on whether it’s an Azure or external service).

First 1 billion DNS queries/month $- per million queries
Over 1 billion DNS queries/month $- per million queries
Basic Health Checks
Basic health checks (Azure) $- per Azure endpoint/month
Fast interval health checks add-on (Azure)1 $- per Azure endpoint/month
Basic health checks (external) $- per external endpoint/month
Fast interval health checks add-on (external)1 $- per external endpoint/month
1Fast endpoint health checks need to be purchased as an add-on to basic endpoint health checks.
Real User Measurements
Measuring Azure Regions2 $- per million measurements
1Ingestion of Real User Measurements needs to be enabled by the customer. 2Traffic Manager Real User Measurements currently supports measuring only Azure regions.
Traffic View
Data points2 processed $- per million data points processed
1Traffic View needs to be enabled by the customer. 2Currently, the only data point types used are the queries received by Azure Traffic Manager service.

Support & SLA

  • Technical support for all Azure services released to general availability, including Traffic Manager, is available through Azure Support, starting at $29/month. Billing and subscription management support is provided at no cost. Technical support is also available free of charge through community forums.
  • We guarantee that DNS queries will receive a valid response from at least one of our Azure Traffic Manager name server clusters at least 99.99 percent of the time. Availability is calculated over a monthly billing cycle. Learn more about our SLA.

Frequently asked questions

  • Whenever a user accesses your application, a DNS query is used to map the name of your service to its IP address. By providing different responses to different DNS queries, Traffic Manager allows you to route incoming traffic across multiple hosted Azure services whether they're running in the same datacenter or across different datacenters around the world.

    Traffic Manager provides you with a choice of traffic routing methods, including performance, failover, and round-robin. By using these to effectively manage your traffic, you can ensure high performance, availability, and resiliency of your applications.

  • Traffic Manager enables you to improve the availability of your critical applications by monitoring your hosted Azure service endpoints and providing automatic failover capabilities when a service goes down.

    To do this, Traffic Manager continually monitors the health of each service endpoint. When these “Health Checks” detect that a service has gone down, Traffic Manager re-routes traffic to the other services.

  • Yes, the prices for DNS queries and health checks are the same irrespective of the traffic routing method used.

  • When a user's PC makes a DNS query, it doesn't contact the Traffic Manager name servers directly. Instead, these queries are sent via recursive DNS servers run by enterprises and ISPs. These servers cache the DNS responses, so that other users' queries can be processed more quickly. Since these cached responses don't reach the Traffic Manager name servers, they don't incur a charge.

    The caching duration is determined by the "TTL" parameter in the original DNS response. This parameter is configurable in Traffic Manager—the default is 300 seconds, and the minimum is 30 seconds.

    By using a larger TTL, you can increase the amount of caching done by recursive DNS servers and thereby reduce your DNS query charges. However, increased caching will also impact how quickly changes in endpoint status are picked up by users, for example, your user failover times in the event of an endpoint failure will become longer. For this reason, we don't recommend using very large TTL values.

    Likewise, a shorter TTL gives more rapid failover times, but since caching is reduced the query counts against the Traffic Manage name servers will be higher.

    By allowing you to configure the TTL value, Traffic Manager enables you to make the best choice of TTL based on your application's business needs.


Estimate your monthly costs for Azure services

Review Azure pricing frequently asked questions

Learn more about Traffic Manager

Review technical tutorials, videos, and more resources

Added to estimate. Press 'v' to view on calculator

Talk to a sales specialist for a walk-through of Azure pricing. Understand pricing for your cloud solution.

Boost your application performance and availability today