How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

update-avm-modules-in-bicep - Skill

Imported from github/awesome-copilot (skills/update-avm-modules-in-bicep/SKILL.md) via skills.sh. Install upstream with npx skills add github/awesome-copilot --skill update-avm-modules-in-bicep. Copyright stays with the author.

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.

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:

| Module | Current | Latest | Status | Action | Docs |
|--------|---------|--------|--------|--------|------|
| avm/res/compute/vm | 0.1.0 | 0.2.0 | 🔄 | Updated | [📖](link) |
| avm/res/storage/account | 0.3.0 | 0.3.0 | ✅ | Current | [📖](link) |

### Summary of Updates

Describe updates made, any manual reviews needed or issues encountered.

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

Install update-avm-modules-in-bicep and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

update-avm-modules-in-bicep

About

Update Azure Verified Modules in Bicep Files

Process

Tool Usage

Breaking Change Policy

Output Format

Icons

Requirements

Install update-avm-modules-in-bicep and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews