Azure Traffic Manager Profile
Does ZopNight manage Azure Traffic Manager Profile?
Traffic Manager bills per million DNS queries plus a charge for each health-checked endpoint, and a profile whose endpoints were retired keeps probing them indefinitely. ZopNight reads endpoint state through Resource Graph, so profiles pointing at degraded or deleted targets surface as cleanup candidates instead of billing quietly forever.
Rules that fire on Azure Traffic Manager Profile
No active rule family targets Azure Traffic Manager Profile today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery and cost visibility only. |
Traffic Manager provides DNS-based global traffic routing, billed per million queries plus health checks. Profiles for retired endpoints keep running health probes indefinitely.
DNS queries and health probes on the meter
Traffic Manager charges for the DNS queries it answers, metered per million, and separately for the health checks it runs against each monitored endpoint, with external and fast-interval checks costing more than basic Azure-endpoint monitoring. The probe meter is the persistent one. Query volume falls to nothing when users stop resolving the profile’s name, but health checks are initiated by Traffic Manager itself on a fixed cadence, against every configured endpoint, whether those endpoints answer or not. A profile can therefore sustain a steady monthly charge probing services that were switched off during a migration two quarters ago.
Endpoint state drives the cleanup signal
Discovered via Azure Resource Graph with endpoint state, supporting cleanup of profiles whose endpoints are degraded or deleted. As a DNS-layer construct, Traffic Manager has no stop or pause action for ZopNight to schedule (the routing either exists or it does not), so endpoint state stands in as the health-of-purpose signal. A profile where every endpoint reports degraded, or where endpoints reference resources that no longer exist, is doing paid monitoring of a graveyard, and ZopNight raises it for deletion rather than letting it hide among healthy profiles.
Profiles that outlive their endpoints
Typical leftovers include failover profiles built for a DR design that was later replaced by Front Door or DNS-level failover elsewhere; blue-green cutover profiles kept “temporarily” after the green environment became permanent; and geo-routing profiles for regional deployments that were consolidated into one region, leaving probes firing at deregistered hostnames. None of these breaks anything, which is precisely why they persist.
Traffic Manager housekeeping in the portal
Azure portal → Traffic Manager profiles shows each profile with its routing method and monitor status. Open a profile’s Endpoints blade: rows showing degraded or stopped targets, combined with a near-zero query count on the Metrics blade, identify the profiles to delete.