Azure Verified Modules
Azure Verified Modules (AVM) requirements and best practices for developing certified...
Install
npx skills add hashicorp/agent-skills --skill azure-verified-modules -g -a claude-code -y- Repository
- hashicorp/agent-skills911
- Category
- DevOps
- Updated
- 7d ago
- License
- MPL-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Azure Verified Modules (AVM) requirements and best practices for developing certified Azure Terraform modules. Use when creating or reviewing Azure modules that need AVM certification.
Azure Verified Modules (AVM) Requirements
This guide covers the mandatory requirements for Azure Verified Modules certification. These requirements ensure consistency, quality, and maintainability across Azure Terraform modules.
References:
Table of Contents
- Module Cross-Referencing
- Azure Provider Requirements
- Code Style Standards
- Variable Requirements
- Output Requirements
- Local Values Standards
- Terraform Configuration Requirements
- Testing Requirements
- Documentation Requirements
- Breaking Changes & Feature Management
- Contribution Standards
- Compliance Checklist
Module Cross-Referencing
Severity: MUST | Requirement: TFFR1
When building Resource or Pattern modules, module owners MAY cross-reference other modules. However:
- Modules MUST be referenced using HashiCorp Terraform registry reference to a pinned version
- Example:
source = "Azure/xxx/azurerm"withversion = "1.2.3"
- Example:
- Modules MUST NOT use git references (e.g.,
git::https://xxx.yyy/xxx.gitorgithub.com/xxx/yyy) - Modules MUST NOT contain references to non-AVM modules
Azure Provider Requirements
Severity: MUST | Requirement: TFFR3
Authors MUST only use the following Azure providers:
| Provider | Min Version | Max Version |
|---|---|---|
| azapi | >= 2.0 | < 3.0 |
| azurerm | >= 4.0 | < 5.0 |
Requirements:
