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 1. Scan : Extract AVM modules and current versions from ${file} 1. Identify : List all unique AVM modules used by matching avm/res/{service}/{resource} using search tool 1. 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 1. Compare : Parse semantic versions to identify AVM modules needing update 1. Review : For breaking changes, use fetch tool to get docs from: https://github.com/Azure/bicep registry modules/tree/main/avm/res/{service}/{resource} 1. Update : Apply version updates and parameter changes using editFiles tool 1. Validate : Run bicep lint and bicep build using runCommands tool to ensure compliance. 1. Output : Summarize changes in a table format with summary of updates below. Tool Usage Always use tools search , searchResults , fetch , editFiles , runCommands , todos if available. Avoid writing code to perform tasks. Breaking Change Policy ⚠️ PAUSE for approval if updates involve: Incompatible parameter changes Security/compliance modifications Behavioral changes Output Format Only display results in table with icons: Icons 🔄 Updated ✅ Current ⚠️ Manual review required ❌ Failed 📖 Documentation Requirements Use MCR tags API only for version discovery Parse JSON tags array and sort by semantic versioning Maintain Bicep file validity and linting compliance

update-avm-modules-in-bicep