update-avm-modules-in-bicep

Update Azure Verified Modules to latest versions in Bicep files.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill update-avm-modules-in-bicep-gabeujin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-avm-modules-in-bicep
Source: https://github.com/Gabeujin/workspace-init-mcp/tree/main/awesome/skills/update-avm-modules-in-bicep
Command: npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill update-avm-modules-in-bicep-gabeujin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of updating Azure Verified Modules (AVM) to their latest versions within Bicep files, ensuring your infrastructure code remains current and secure.

Core Features & Use Cases

  • Automated Version Updates: Scans Bicep files to identify and update AVM modules to the latest compatible versions.
  • Breaking Change Detection: Reviews potential breaking changes and pauses for manual approval when necessary.
  • Validation: Ensures updated files pass bicep lint and bicep build checks.
  • Use Case: Maintain a Bicep deployment for your Azure environment by regularly updating AVM modules like storage accounts or virtual machines to benefit from new features and security patches.

Quick Start

Update the Azure Verified Modules in the file 'main.bicep' to their latest versions.

Frequently Asked Questions about update-avm-modules-in-bicep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update Azure Verified Modules in Bicep files to the latest version?

Update Azure Verified Modules by scanning Bicep files to fetch the latest versions from MCR, comparing semantic versions, and applying updates while pausing for manual approval on breaking changes.

How does breaking change detection work when updating Bicep modules?

Breaking change detection reviews potential compatibility issues during AVM module updates and pauses the process for manual approval before applying changes that might break your infrastructure code.

Can I validate Bicep file integrity after updating Azure Verified Modules?

You validate Bicep file integrity after updating Azure Verified Modules by running `bicep lint` and `bicep build` checks to ensure the updated files pass without errors.

What is the best way to automate AVM module updates for Azure infrastructure as code?

Automating AVM module updates involves scanning Bicep files to identify AVM references, fetching the latest compatible versions from MCR, and validating the updated files using linting and build commands.

Why should I update Azure Verified Modules regularly in my Bicep deployments?

Updating Azure Verified Modules regularly in Bicep deployments ensures your infrastructure code remains current and secure by applying new features and security patches to resources like storage accounts or virtual machines.