azure-verified-modules

Azure Verified Modules certification requires pinned registry sources, allowed azurerm and azapi provider ranges, required terraform.tf and required_providers blocks, and strict variable, output, and documentation standards for Terraform compliance.

To pass AVM compliance checks, ensure your Terraform module satisfies naming conventions, applies feature toggles for safe changes, generates documentation via Terraform Docs, and adheres to required provider and version constraints outlined in the certification checklist.

Yes, Azure Verified Modules requires specific provider version constraints, including allowed ranges for azurerm and azapi providers, alongside mandatory required_providers blocks to ensure module stability and reduce review churn.

The best way to manage breaking changes in Azure Verified Modules is to use feature toggles for safe changes and follow strict breaking-change discipline, ensuring module consistency and minimizing disruptions during internal reviews.

Yes, you can apply Azure Verified Modules guidance when developing or auditing both Resource and Pattern modules intended for certification, ensuring consistent internal reviews and compliance checks across large teams.