// the find
Azure/Azure-Verified-Modules
Azure Verified Modules (AVM) is an initiative to consolidate and set the standards for what a good Infrastructure-as-Code module looks like. Modules will then align to these standards, across languages (Bicep, Terraform etc.) and will then be classified as AVMs and available from their respective language specific registries.
This is the governance and documentation hub for Azure Verified Modules, Microsoft's effort to standardize what a 'good' Bicep or Terraform module looks like. It does not contain the modules themselves — those live in separate per-language registries — this repo holds the specs, contribution process, and issue tracking that keep those modules consistent.
The spec definitions are genuinely rigorous: functional and non-functional requirements are broken out by module type (resource, pattern, utility) and by language, each with a stable ID (RMFR1, BCPNFR12, TFNFR27, etc.) that can be cited in reviews. There's real CI automation behind the standard, not just paperwork — workflows that regenerate module registry tables, mirror MAR files, and diff against AzAdvertizer on a schedule. Issue triage is automated too, with a documented bot flow rather than manual labeling.
Zero actual module code lives here, which trips people up — the README has to explicitly redirect you to aka.ms/AVM and the per-language indexes, so this repo is an easy place to land by mistake if you're searching for a module to consume. The listed language (PowerShell) is a red herring; it reflects tooling scripts, not anything a consumer would touch. The spec/contribution docs are dense and bureaucratic — dozens of separate FR/NFR markdown files split across resource/pattern/utility and Bicep/Terraform — which is a lot of surface area to read before you can contribute a single module.