update-avm-modules-in-bicep

To update Azure Verified Modules in Bicep files, this skill scans your files for AVM usage, checks the Microsoft Container Registry for the newest semantic versions, and applies the updates automatically.

Breaking change detection for Bicep AVM modules works by fetching module documentation during the update process, allowing you to identify potential breaking changes that require manual parameter adjustments before applying new versions.

Yes, you can validate Bicep files automatically after updating AVM module versions by running `bicep lint` and `bicep build` commands to ensure code integrity and outputting a summary table of all modifications.

The best way to automate Azure Verified Module version checks is using a skill that scans Bicep files, queries MCR for available updates, and modifies the files directly to incorporate the latest security patches and features.

You may need to manually adjust Bicep parameters when upgrading to a newer AVM release if the skill detects breaking changes in the module documentation, though it attempts to apply necessary parameter adjustments automatically.