Azure Verified Modules
Azure Verified Modules (AVM) is a Microsoft-led initiative to define and deliver consistent, high-quality Infrastructure-as-Code modules for Azure. AVM sets the standards for what a good IaC module looks like, then publishes modules across languages — Bicep and Terraform — that align to those standards and are available from their respective registries.
AVM modules codify Microsoft guidance, including the Well-Architected Framework, with best-practice configurations built in. They act as composable building blocks for deploying Azure resources and reusable architectural patterns — accelerating consistent solution development for cloud-native and migrated workloads alike.
Connection to CCC
CCC catalogs define the controls and assessment requirements for cloud services. Microsoft is currently testing to see how well AVM modules meet the CCC controls via our behavioural testing suite and also work mapping Azure Policy.
Example: a CCC-aligned private AKS cluster
The AVM Terraform module for Azure Kubernetes Service includes a finos-ccc example. It deploys a private AKS cluster configured against the CCC Kubernetes catalog and the CCC Core controls it imports. The supporting resources come from other published AVM modules: networking, identities, a private Key Vault with KMS keys, a private container registry, Azure Policy assignments and logging.
Each Terraform block is annotated with the CCC assessment requirements it enforces. The example's README maps every requirement to how it is met: Terraform-managed Azure configuration, Azure Policy at admission, Kubernetes objects, or a remaining operational process. It is a reference configuration, not a CCC attestation. Run the behavioural tests against a deployed cluster to check the results.