Azure Traffic Manager Profile
Global, DNS-based load balancing with a Traffic Manager profile and map-driven external endpoints — Performance, Priority, Weighted, Geographic, Subnet or MultiValue routing with an HTTPS health probe.
Verification
Live-testedReally deployed, verified, idempotent and destroyed in a cloud sandbox.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live-tested — applied, verified, destroyed
Last verified 2026-06-30 · how we verify
Documentation
azure-traffic-manager
Global, DNS-based load balancing with Azure Traffic Manager: a profile
(azurerm_traffic_manager_profile) plus map-driven external endpoints
(azurerm_traffic_manager_external_endpoint). Steer clients across regions or
providers by Performance (lowest latency), Priority (failover),
Weighted, Geographic, Subnet or MultiValue routing, with a single
health monitor. Secure-by-default: the health probe is HTTPS/443, and
Traffic View analytics (extra cost + client-network telemetry) is off.
Consumes an existing resource group (Traffic Manager is a global resource). Works
with Terraform and OpenTofu (>= 1.6), azurerm provider >= 4.0, < 5.0.
Requirements
| Requirement | Version |
|---|---|
| Terraform / OpenTofu | >= 1.6 |
hashicorp/azurerm | >= 4.0, < 5.0 |
Verification
Static-validated (fmt, validate, tflint). Live apply/destroy testing pending cloud sandbox availability — see catalog status.
License
Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).
Usage code & full reference unlock after purchase
The complete copy-paste usage, the full input/output reference, and operational notes ship with your licence — shown here and bundled in the download.
- Usage
- Inputs
- Outputs
- Notes — the routing toggles that trip people up