AzureStatic-verified

A Firewall that Blocks rather than Narrates

Every security feature on this service defaults to telling you, not to stopping it: threat_intelligence_mode defaults to Alert, which logs traffic to known-malicious destinations and forwards it, and intrusion detection does the same. Deny for both here, with the DNS proxy on so FQDN rules and the client agree on an answer.

terraformAzureazure
azure-firewallvizier v1.2.0

Verification

Static-verified

Passed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).

Conformance

  • Static validation (fmt · validate · tflint)
  • Security scan clean (Checkov)
  • Plan tests (mocked: validation rules · outputs)

Provenance

  • SHA-256 checksum
  • Signature (pending)

Functional

  • Live test pending (no cloud run yet)

Last verified 2026-09-13 · how we verify

Use it from the registry

terraform · opentofu
module "firewall" {
  source  = "www.iac-bazaar.com/iac-bazaar/azure-firewall/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.

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-firewall

An Azure Firewall that blocks rather than narrates. Works with Terraform and OpenTofu (>= 1.6), azurerm provider >= 4.0, < 5.0.

Every security feature on this service defaults to telling you, not to stopping it. threat_intelligence_mode defaults to Alert: traffic to addresses and domains on Microsoft's malicious-infrastructure feed is logged and then forwarded. Intrusion detection defaults to Alert as well: the signature fires, the alert is written, the packet is delivered. In both cases the portal shows the feature as enabled and the dashboards fill with detections, while nothing is prevented. Deny for both here, with blocks_known_malicious_traffic and blocks_intrusion_signatures as outputs.

IDPS and TLS inspection exist only on the Premium SKU. On Standard, setting an intrusion detection mode is accepted by Terraform and does nothing - the worst of both worlds, since you pay for neither and believe you have one. A precondition refuses that combination.

FQDN rules in network rule collections need the DNS proxy. Without dns_proxy_enabled, the firewall resolves the name when it evaluates the rule and the client resolves it separately - and a round-robin or geo-routed record can hand them different answers, so the address the client actually reaches is not the address the rule allowed. On here.

Azure Firewall records nothing by itself. An allow or deny that was never written down cannot be reviewed, which removes the only evidence that any of the above did what it claims.

Smaller things: the subnet must be named exactly AzureFirewallSubnet and Azure's error when it is not does not say so, so a precondition checks the name; and three availability zones by default, because every route in the virtual network points at this firewall by design and a single-zone deployment is a single point of failure for all of them.

Verification

Static validation runs tofu fmt, init, validate, tflint and checkov. This module has not yet had a live test, so it is published as statically validated with its live test pending and does not carry the live-tested mark.

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

Related modules