Update Avm Modules In Bicep

Here's a skill that automates the tedious process of keeping Azure Verified Modules current in your Bicep infrastructure files. It scans your Bicep templates, checks the Microsoft Container Registry for latest AVM versions, and updates module references while running bicep lint and build validation to catch issues. The smart part is it only applies non-breaking updates automatically and pauses for approval when it detects parameter changes or security modifications that need human review. Saves you from manually tracking down version numbers and ensures your infrastructure code stays compliant with current AVM standards without breaking existing deployments.

skills.sh installs: 8.6K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill update-avm-modules-in-bicep --agent claude-code

Installs into .claude/skills of the current project.

Files

Update Azure Verified Modules in Bicep Files

Update Bicep file ${file} to use latest Azure Verified Module (AVM) versions. Limit progress updates to non-breaking changes. Don't output information other than the final output table and summary.

Process

Scan: Extract AVM modules and current versions from ${file}
Identify: List all unique AVM modules used by matching avm/res/{service}/{resource} using #search tool
Check: Use #fetch tool to get latest version of each AVM module from MCR: https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list
Compare: Parse semantic versions to identify AVM modules needing update
Review: For breaking changes, use #fetch tool to get docs from: https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}
Update: Apply version updates and parameter changes using #editFiles tool
Validate: Run bicep lint and bicep build using #runCommands tool to ensure compliance.
Output: Summarize changes in a table format with summary of updates below.