Azure Traffic Manager is a DNS-based traffic load balancer that enables you to distribute traffic optimally to services across global Azure regions, while providing high availability and responsiveness.
Azure Traffic Manager provides globally aware DNS resolution to Azure services located in different regions using an intelligent set of processes based on specified configurations and the geographical location of the users local DNS server (LDNS). Traffic Manager uses DNS to direct client requests to the most appropriate service endpoint based on a traffic-routing method and the health of the endpoints. An endpoint is any Internet-facing service hosted inside or outside of Azure. Traffic Manager provides a range of traffic-routing methods and endpoint monitoring options to suit different application needs and automatic failover models. Traffic Manager is resilient to failure, including the failure of an entire Azure region.
Choose from flexible traffic routing options –
Azure Traffic Manager offers four types of DNS-based traffic routing: Failover, performance, geographic and weighted round-robin. Choose the one which is right for you or combine, using nested profiles.
Reduce application downtime –
Traffic Manager can improve the availability of important applications by monitoring your Azure services or external websites and services, automatically directing users to the next best location when there is a failure.
Improve app performance and content delivery –
Traffic Manager makes your applications more responsive and improves content delivery times by directing your customers to Azure end points or an external location with the lowest network latency.
Distribute user traffic over multiple locations –
Traffic Manager can direct your customer traffic and distribute it across multiple locations, such as multiple cloud services or multiple Azure web apps. Traffic Manager can also help you with your geofencing needs, using the geographic routing method.
Use with your on-premises datacenter –
Traffic Manager is a popular option for on-premises scenarios, including burst-to-cloud, migrate-to-cloud and failover-to-cloud. Use it to upgrade or perform maintenance on your on-site datacenter without inconveniencing customers.
Geographic fencing of your application users –
Traffic Manager provides you with Geographic routing capabilities to ensure content localisation and adherence to data sovereignty regulations. Applying geofencing allows users connecting from specific geographic regions to be routed to specific endpoints.
Obtain actionable insight about your users –
Use the Traffic View capability in Traffic Manager to see where your users are connecting from and the quality of their digital experience.
Azure Traffic Manager supports six traffic-routing methods to determine how to route network traffic to the various service endpoints. For any profile, Traffic Manager applies the traffic-routing method associated to it to each DNS query it receives. The traffic-routing method determines which endpoint is returned in the DNS response.
Select Priority when you want to use a primary service endpoint for all traffic and provide backups in case the primary or the backup endpoints are unavailable.
Select Weighted when you want to distribute traffic across a set of endpoints, either evenly or according to weights, which you define.
Select Performance when you have endpoints in different geographic locations and you want end users to use the “closest” endpoint in terms of the lowest network latency.
Select Geographic so that users are directed to specific endpoints (Azure, External, or Nested) based on which geographic location their DNS query originates from. This empowers Traffic Manager customers to enable scenarios where knowing a user’s geographic region and routing them based on that is important. Examples include complying with data sovereignty mandates, localization of content & user experience and measuring traffic from different regions.