Azure Traffic Manager

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

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.