Skip to main content

Traffic Manager pricing

Route incoming traffic for high performance and availability

Geo-route incoming traffic to your app for better performance and availability. No upfront cost, no termination fees, and pay only for what you use.

Explore pricing options

Apply filters to customise pricing options to your needs.

Prices are estimates only and are not intended as actual price quotes. Actual pricing may vary depending on the type of agreement entered with Microsoft, date of purchase, and the currency exchange rate. Prices are calculated based on US dollars and converted using London closing spot rates that are captured in the two business days prior to the last business day of the previous month end. If the two business days prior to the end of the month autumn on a bank holiday in major markets, the rate setting day is generally the day immediately preceding the two business days. This rate applies to all transactions during the forthcoming month. Sign in to the Azure pricing calculator to see pricing based on your current programme/offer with Microsoft. Contact an Azure sales specialist for more information on pricing or to request a price quote. See frequently asked questions about Azure pricing.

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 Measurements2
Measuring Azure Regions3 $- per million measurements
2Ingestion of Real User Measurements needs to be enabled by the customer. 3Traffic Manager Real User Measurements currently supports measuring only Azure regions.
Traffic View4
Data points5 processed $- per million data points processed
4Traffic View needs to be enabled by the customer. 5Currently, the only data point types used are the queries received by Azure Traffic Manager service.

Azure pricing and purchasing options

Connect with us directly

Get a walkthrough of Azure pricing. Understand pricing for your cloud solution, learn about cost optimisation and request a customised proposal.

Talk to a sales specialist

See ways to purchase

Purchase Azure services through the Azure website, a Microsoft representative or an Azure partner.

Explore your options

Additional resources

Traffic Manager

Learn more about Traffic Manager features and capabilities.

Pricing calculator

Estimate your expected monthly costs for using any combination of Azure products.


Review the Service Level Agreement for Traffic Manager.


Review technical tutorials, videos, and more Traffic Manager resources.

  • 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 datacentre or across different datacentres 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.

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

Get free cloud services and a $200 credit to explore Azure for 30 days.

Added to estimate. Press 'v' to view on calculator
Can we help you?