Azure Front Door (Std/Premium) + WAF
Global entry point: Front Door profile, endpoints, origin groups, custom domains with managed TLS and WAF policy.
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan test superseded by live test
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-08-04 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o azure-front-door-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/azure-front-door/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle azure-front-door-1.0.0.sigstore.json \
azure-front-door-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "2c1d6a0acf26005fb3dc6539e6ef29f3b668d06a99510c7e06d566df3419f455 azure-front-door-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "front_door" {
source = "www.iac-bazaar.com/iac-bazaar/azure-front-door/azure"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/azure-front-door?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Azure Front Door (Std/Premium) + WAF](https://www.iac-bazaar.com/catalog/azure-front-door?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "front_door" {
source = "www.iac-bazaar.com/iac-bazaar/azure-front-door/azure"
version = "1.0.0"
}
```Preview:
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
azure-front-door
Cost and prerequisites: a Front Door profile runs about $35/month base plus traffic. Custom domain validation needs control of a real DNS zone, and managed-TLS issuance is asynchronous, so a domain is not servable the moment the apply returns.
Global L7 entry point built on Azure Front Door (Standard/Premium): one
profile, a managed endpoint, origin groups + origins, routes, optional custom
domains with Front Door-managed TLS, and a Web Application Firewall policy
bound to every fronted domain. Works with Terraform and OpenTofu (>= 1.6),
azurerm provider >= 4.0, < 5.0.
The Front Door object graph is a set of cross-referencing resources (profile →
endpoint/origin-group → origin → route, plus a separate firewall-policy →
security-policy chain). This module flattens origins into group/origin-keyed
instances, wires each route to the origin IDs it must depend on (Front Door
requires this for correct create/destroy ordering), and attaches the WAF to the
endpoint and all custom domains through one security policy.
Secure defaults
- WAF on by default in Prevention mode, bound to the endpoint and every custom domain via a security policy — nothing is fronted without the firewall.
- Premium SKU by default so the managed Microsoft DefaultRuleSet + BotManager rule sets are available (managed rules are Premium-only; on Standard only custom rules apply, enforced by a precondition).
- Routes forward HttpsOnly to origins and redirect HTTP → HTTPS.
- Origin certificate name checks on; custom domains use managed TLS 1.2+ (auto-renewing, no certificate material in state).
- Lock your origins to this profile using the
resource_guidoutput as theX-Azure-FDIDheader so the backend only accepts traffic from your Front Door.
License
Commercial — LicenseRef-IaCBazaar-Commercial
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
- Inputs
- Outputs
- Requirements & notes
Related modules
azure-application-gateway
Regional L7 load balancer with WAF v2 policy, TLS termination from Key Vault, autoscaling and health probes.
azure-load-balancer
An Azure Standard L4 load balancer with a self-created static public IP frontend, a backend address pool, health probes and load-balancing rules - Standard SKU throughout.
azure-traffic-manager
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.
tencent-cdn
A Tencent Cloud CDN domain in front of your COS bucket or origin hosts, serving outside mainland China unless an ICP-filed area is accepted by name, with the certificate from SSL Certificate Service, every HTTP request redirected, HSTS, HTTP/2, OCSP stapling, TLS 1.0 and 1.1 off, IPv6, and the origin fetched over HTTPS. The CNAME to point the domain at is exported.
huawei-cdn
A Huawei Cloud CDN domain in front of your OBS bucket or origin host, serving outside mainland China unless an ICP-filed area is accepted by name, with the certificate from Cloud Certificate Manager, every HTTP request redirected, HSTS, HTTP/2, OCSP stapling, TLS 1.0 and 1.1 off, IPv6, cache headers followed from the origin, and the origin fetched over HTTPS. The CNAME is exported.
alicloud-cdn
An Alibaba Cloud CDN domain in front of your OSS bucket or origin host, serving outside mainland China unless an ICP-filed scope is accepted by name, with the certificate from Certificate Management, every HTTP request redirected, HSTS, HTTP/2, TLS 1.0 and 1.1 off, IPv6, and the origin fetched over HTTPS. The CNAME to point the domain at is exported.