Azure Traffic Manager helps reduce downtime and improve responsiveness of important applications by routing incoming traffic across multiple deployments in different regions. Built-in health checks and automatic rerouting help ensure high availability if a service fails. Use Traffic Manager with Azure services including Web Apps, Cloud Services, and Virtual Machines—or combine it with on-premises services for hybrid deployments and smooth cloud migration.
The Australia Regions are available to customers with a business presence in Australia or New Zealand.
The India regions are currently available to volume licensing customers and partners with a local enrollment in India. For more information, contact your Microsoft India partner manager or account manager. The India regions will open to direct online Azure subscriptions in 2016.
Important: The price in R$ is merely a reference; this is an int'l transaction and the final price is subject to exchange rates and the inclusion of IOF taxes and an eNF will not be issued.
Traffic Manager is not available in the West US 2 region. Please select another region.
Traffic Manager is not available in the West Central US region. Please select another region.
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||$0.54 per million queries|
|Over 1 billion DNS queries / month||$0.375 per million queries|
|Health Checks (Azure)||$0.36 per Azure endpoint / month|
|Health Checks (External)||$0.54 per External endpoint / month|
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, fail-over 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 same irrespective of the traffic routing method being used.
When an end-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 end users, i.e. your end-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.