Skip to main content
Azure Traffic Manager

Azure Traffic Manager


What is Azure Traffic Manager?

Microsoft's Azure Traffic Manager operates at the DNS layer to quickly and efficiently direct incoming DNS requests based on the routing method of your choice.

Read more
Recent Reviews
Read all reviews


Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation


View all pricing

What is Azure Traffic Manager?

Microsoft's Azure Traffic Manager operates at the DNS layer to quickly and efficiently direct incoming DNS requests based on the routing method of your choice.

Entry-level set up fee?

  • No setup fee


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

1 person also want pricing

Alternatives Pricing

What is Azure Load Balancer?

Microsoft's Azure Load Balancer provides built-in load balancing for cloud services and virtual machines, so the user can create highly-available and scalable applications in minutes.

Return to navigation

Product Details

What is Azure Traffic Manager?

Azure Traffic Manager Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings



(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Score 10 out of 10
Vetted Review
Verified User
Azure Traffic Manager is our primary site availability and performance solution for all services we provide to our employees. We have a complex setup with multi-sites and a cloud region, and inbound traffic hit multiple locations, we have multiple [Azure Traffic Manager] configuration for numerous services, for example, for services offered from multiple locations, we have region-based configuration that returns the nearest endpoint for clients. Additionally, we use [Azure Traffic Manager] to provide High Availability across multiple regions, downtime hits 30 seconds in case of a failure with a connected client, which is considered minimal for us, users are then directed to the next healthy endpoint. [Azure Traffic Manager] is considered an essential part of our setup, without it, many of our business services will be affected and many more complex technologies would be required
  • Performance DNS Load Balancing for Lowest Latency Endpoint to Clients
  • Priority-Based DNS Load Balancing to ensure maximum up time for a service
  • Geographic-based DNS Load Balancing to force certain clients in certain regions to connect to specific endpoints
  • Traffic View is a great feature, but doesn't work very well, sometimes it gets stuck and stops loading traffic view data
  • Automatic probing for endpoints sometimes gets stuck too, I would recommend a technique to test the endpoint in real time from Azure Portal
  • Traffic View heatmap is buggy and doesn't point correctly to locations
  • Traffic View portal doesn't show source countries (Shows coordinates) it would be much more helpful to have coordinates auto-translated to geolocations/countries
Azure Traffic Manager is a great product, if you have multiple sites hosting similar services (Primary and DR), and you want to ensure that users are directed to the DR in case of a primary datacenter failure, [Azure] Traffic Manager does this very nicely. If you have a service hosted across multiple regions/datacenters and you want to balance the inbound load between the regions, [Azure] Traffic Manager does this very well, of course such scenario would require a database replication or something like Cosmos-DB in the backend [Azure Traffic Manager] is also well suited for inbound traffic with multiple IPs, you can fail-over traffic from one inbound IP to another based on its availability, or if you have multiple internet connections that you want to balance the load across, it does this pretty nicely too.
  • Performance DNS Load Balancing
  • High Availability for Services across Multiple Datacenters
  • High Availability & Load Balancing for Inbound Traffic Across Multiple Internet Links
  • Service cost is exceptionally low
  • Overall, this product saves a lot of money for the value it provides and it isn't expensive
  • It's around half a dollar per million queries, which is truly peanuts, extras may be required if you do advanced configuration
  • I can't see any reason why any business wouldn't be using this product, very low investment for a very high return and savings
Amazon Route 53 Traffic Flow does what [Azure] Traffic Manager does, however, in Azure Configuration is separated between Azure DNS Zones (For DNS Zone Management) and [Azure] Traffic Manager for DNS Traffic Management and Load Balancing, Route 53 in a unified product for DNS Traffic Management using Traffic Flow and DNS Zone Management. Route 53 does a great job, however, we found it to be a little bit more complex to setup than [Azure] Traffic Manager, Setting up traffic manager is pretty easy even for the first time, and getting the best out of it is relatively simple.
Return to navigation