Azure Front Door (Std/Premium) + WAF
Global entry point: Front Door profile, endpoints, origin groups, custom domains with managed TLS and WAF policy.
This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.
Provider drift
This module's own ceiling currently holds it below a release that has already shipped. It still applies exactly as before, against the newest version it allows. What it cannot reach is anything added in the newer major.
| Provider | This module allows | Newest it accepts | Newest released |
|---|---|---|---|
| hashicorp/azurerm | >= 4.0, < 5.0 | 4.81.0 | 5.3.0 |
Measured 2026-09-01 against the Terraform registry. The whole catalogue is on provider freshness.
What depends on this
No reference architecture names this module, so changing it affects only configurations that reference it directly.
Nearest alternatives
Same cloud, same category. These are what you would weigh against it without changing provider.
The same job on other clouds
CDN & Edge Delivery on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.
Installing it
module "azure_front_door" {
source = "www.iac-bazaar.com/iac-bazaar/azure-front-door/azure"
version = "1.1.0"
}A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.