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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Verified User
C-Level Executive in Information Technology (201-500 employees employees)
Pros
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
Cons
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
Most Important Features
Performance DNS Load Balancing
High Availability for Services across Multiple Datacenters
High Availability & Load Balancing for Inbound Traffic Across Multiple Internet Links
Return on Investment
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