DNS Providers

Latency Global + Azure Traffic Manager

Connect Azure Traffic Manager to Latency Global for monitoring-driven traffic routing. Use real-time data from 70+ global probes to inform Azure's traffic management decisions.

Available on: Pro plan and above

How to Set Up

1

Set up a Traffic Manager profile in Azure

2

Create a service principal with Traffic Manager permissions

3

In Latency Global, add Azure Traffic Manager as a DNS provider

4

Enter your Azure credentials (tenant ID, client ID, client secret)

5

Create DNS policies linking monitors to Traffic Manager endpoints

Use Cases

Performance-Based Routing

Route traffic based on real latency data from Latency Global's 70+ probes, not just Azure's own health checks.

Multi-Cloud Failover

Monitor endpoints across AWS, GCP, and Azure, with Traffic Manager handling the failover routing.

Hybrid Infrastructure

Monitor on-premise and cloud endpoints together. When an on-premise server goes down, Traffic Manager automatically routes to your Azure backup.

Other Integrations

Frequently Asked Questions

The service principal needs Contributor access to the Traffic Manager profile resource.

The integration targets Traffic Manager specifically. For Azure Front Door, you can use webhook alerts to trigger Azure Functions that update Front Door configuration.

It complements them. Latency Global monitors from 70+ global locations with more check types (HTTP, ping, DNS, traceroute), giving you broader visibility than Azure's native probes alone.

Get started with Azure Traffic Manager

Set up Azure Traffic Manager integration in minutes. Plans from $5/month with all integrations included.

5 monitors included • All 70+ locations (+40 more soon) • No contracts