update-avm-modules

Update Azure Verified Modules in Bicep files to latest MCR versions.

1|Updated Mar 5, 2026

Search Tags:#azure #infrastructure as code #iac #avm #bicep #module updates

Ready to run

npx skills add https://github.com/PlagueHO/plagueho.os --skill update-avm-modules

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-avm-modules
Source: https://github.com/PlagueHO/plagueho.os/tree/main/.github/skills/update-avm-modules
Command: npx skills add https://github.com/PlagueHO/plagueho.os --skill update-avm-modules

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) within Bicep files, ensuring your infrastructure code uses the latest stable versions and reducing the risk of using outdated or vulnerable modules.

Core Features & Use Cases

Automated Version Scanning: Scans Bicep files for AVM module references.
Latest Version Detection: Queries the Microsoft Container Registry (MCR) for the newest module versions.
Breaking Change Review: Identifies and flags potential breaking changes for manual review before updates are applied.
Automated Updates: Applies approved version updates to Bicep files.
Validation: Runs Bicep linting to ensure updated files are valid.
Use Case: Regularly update all AVM modules in your Bicep IaC to the latest versions to incorporate new features and security patches, while being alerted to any breaking changes that require code adjustments.

Quick Start

Use the update-avm-modules skill to update all AVM modules in the 'infra/main.bicep' file.

Frequently Asked Questions about update-avm-modules

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 versions?▼

To update Azure Verified Modules in Bicep files, this Skill scans module references, queries the Microsoft Container Registry for the newest versions, compares them semantically, and applies the updates. It ensures your infrastructure code uses the latest stable module releases.

What is the best way to check for breaking changes when updating Bicep AVM modules?▼

Checking for breaking changes when updating Bicep AVM modules is handled automatically by identifying and flagging potential issues for manual review before any updates are applied. This prevents infrastructure deployment failures caused by incompatible module versions.

Do I need Azure CLI to update Azure Verified Modules in my Bicep infrastructure code?▼

Yes, you need the Azure CLI with the Bicep extension installed to update Azure Verified Modules. The Skill also requires network access to mcr.microsoft.com to query the Microsoft Container Registry for the latest available module versions.

How does Bicep linting validation work after applying AVM module updates?▼

Bicep linting validation runs after applying AVM module updates to ensure the modified Bicep files are structurally valid. This automated validation step confirms that the semantic version updates do not introduce syntax errors into your infrastructure code.

Can I automate scanning Bicep files for outdated Azure Verified Modules?▼

Yes, you can automate scanning Bicep files for outdated Azure Verified Modules. The Skill scans your files for AVM module references and queries the Microsoft Container Registry to detect when your infrastructure code is using older module versions.