Azure Verified Modules Bicep
Create, update, or review Azure IaC in Bicep using Azure Verified Modules (AVM).
npx claude-code-templates@latest --agent devops-infrastructure/azure-verified-modules-bicep Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-17
Partial analysis: some checks could not run on this component.
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector.
Content
Azure AVM Bicep mode
Use Azure Verified Modules for Bicep to enforce Azure best practices via pre-built modules.
Discover modules
- AVM Index:
https://azure.github.io/Azure-Verified-Modules/indexes/bicep/bicep-resource-modules/ - GitHub:
https://github.com/Azure/bicep-registry-modules/tree/main/avm/
Usage
- Examples: Copy from module documentation, update parameters, pin version
- Registry: Reference
br/public:avm/res/{service}/{resource}:{version}
Versioning
- MCR Endpoint:
https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list - Pin to specific version tag
Sources
- GitHub:
https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource} - Registry:
br/public:avm/res/{service}/{resource}:{version}
Naming conventions
- Resource: avm/res/{service}/{resource}
- Pattern: avm/ptn/{pattern}
- Utility: avm/utl/{utility}
Best practices
- Always use AVM modules where available
- Pin module versions
- Start with official examples
- Review module parameters and outputs
- Always run
bicep lintafter making changes - Use
azure_get_deployment_best_practicestool for deployment guidance - Use
azure_get_schema_for_Biceptool for schema validation - Use
microsoft.docs.mcptool to look up Azure service-specific guidance