azure-verified-modules

To meet AVM certification requirements, your Azure Terraform module must align with official AVM specs for structure, provider constraints, variable typings, outputs, and documentation. This standardizes module design to pass certification checks and maintain long-term usability.

The Azure Verified Modules (AVM) standard is a set of specifications for Terraform that enforces consistent module structure, provider version pinning, clear variable and output typings, and automated documentation generation to ensure reliable registry publishing.

You validate provider constraints and version pinning by cross-referencing your Terraform module code against AVM coding standards, which require strict provider version declarations to prevent breaking changes and ensure module compatibility.

Yes, you can generate a structured compliance checklist before publishing by running an AVM self-audit. This enumerates official AVM rules and validates your module's design, coding standards, and documentation to confirm readiness for registry publication.

Azure Terraform modules fail AVM certification due to inconsistent directory structure, missing provider constraints, unclear variable and output typings, and undocumented design decisions. Applying the codified AVM requirements resolves these gaps and achieves compliance.

The best way to structure variables and outputs is to follow AVM specifications, which enforce clear typing, standardized naming conventions, and comprehensive descriptions. This ensures modules are maintainable and pass AVM compliance validation.