azure-verified-modules

A reference guide encoding the mandatory and recommended requirements for Azure Verified Modules (AVM) certification of Azure Terraform modules. It consolidates the AVM specification into an actionable checklist of numbered requirements (for example TFFR1, TFFR3, and the TFNFR series), each labeled with a severity of MUST, SHOULD, or MAY, so authors can tell hard rules apart from advisory guidance while building or reviewing a module.

Coverage spans the full surface of a compliant module: cross-referencing other modules only via pinned HashiCorp registry sources (never git or non-AVM references); allowed Azure providers and their version bounds (azapi >= 2.0 < 3.0, azurerm >= 4.0 < 5.0) enforced through required_providers with pessimistic constraints; and code-style rules such as lower snake_casing for locals, variables, outputs, resources, and modules. It also details resource and block internal ordering (meta-arguments like count and for_each first, arguments alphabetized, depends_on and lifecycle last), count-versus-for_each usage with static-literal keys, dynamic blocks for optional nested objects, unquoted ignore_changes, and coalesce or try patterns for defaults. Variable requirements cover mandatory types, precise descriptions, sensitive-data handling, non-nullable collection defaults, and the prohibition of module-wide toggles like enabled or module_depends_on.

Reach for it when creating a new Azure Terraform module intended for AVM certification, or when auditing an existing module against the standard before submission. Because each rule carries a requirement ID and severity, it doubles as a review rubric: walk the listed sections, confirm MUST items are satisfied, and treat SHOULD items as strong defaults. The document references the official AVM site and the Terraform specification for the authoritative source.