Azure Traffic Manager Profile Builder

About This Tool

The Azure Traffic Manager Profile Builder helps you configure Traffic Manager DNS-based load balancing profiles. Traffic Manager distributes traffic across Azure regions or external endpoints using routing methods like priority, weighted, performance, geographic, and multivalue. This tool guides you through selecting routing methods, configuring endpoints, setting health check parameters, and generating the profile definition for deployment.

When to Use This Tool

• •Build a priority-based failover profile that routes traffic to a primary region and fails over to a secondary when health checks fail.
• •Configure weighted routing to gradually shift traffic between regions during a blue-green deployment or migration.
• •Design geographic routing profiles that direct users to the nearest regional deployment for compliance or latency requirements.
• •Create performance-based profiles that route each user to the endpoint with the lowest network latency.

Frequently Asked Questions

How does Traffic Manager differ from Azure Front Door and Load Balancer?

Traffic Manager is DNS-based, operating at the DNS layer to direct clients to the best endpoint. Azure Front Door is a Layer 7 (HTTP) global load balancer with CDN, WAF, and SSL offload. Azure Load Balancer is Layer 4 (TCP/UDP) for distributing traffic within a region. Use Traffic Manager for DNS-level global routing and Front Door for HTTP-level global routing with advanced features.

What health check protocols does Traffic Manager support?

Traffic Manager supports HTTP, HTTPS, and TCP health checks. For HTTP/HTTPS, you specify a path and expected status code. Health checks run from multiple global locations. An endpoint is marked degraded when it fails checks from a configurable number of locations.