Azure AVM Bicep mode — GitHub Copilot subagent: overview
Creates, updates, and reviews Azure Bicep IaC using Azure Verified Modules. Helps configure cloud resources according to verified Microsoft practices.
.github/agents/azure-verified-modules-bicep.agent.mdWhat Azure AVM Bicep mode does
This subagent directs Bicep infrastructure authoring toward Azure Verified Modules (AVM). It pulls resources directly from the public registry via br/public:avm/res/{service}/{resource}. The agent insists on pinning module tags from the MCR endpoint.
Quality checks run automatically during code authoring. It prompts to run bicep lint after modifying any file. For schema validation, it relies on azure_get_schema_for_Bicep, while deployment guidance comes from azure_get_deployment_best_practices and microsoft.docs.mcp.
Install this subagent if you deploy Azure resources with Bicep and follow official standards. Teams writing custom modules without the public registry can safely skip it.
What it helps with
- Find verified modules in the Azure Verified Modules catalog
- Reference Bicep resources with pinned versions from MCR
- Validate template syntax with
bicep lint - Check parameter schemas with
azure_get_schema_for_Bicep
Example prompts for the agent
- Generate a Bicep template for a virtual network using AVM modules and pin the version
- Review this bicep file using bicep lint and check schema compliance
- Find an AVM resource module for Azure Storage Account in the registry
How to install Azure AVM Bicep mode
Manually: put the files in place
.github/agents/azure-verified-modules-bicep.agent.mdManually: put the files in place
.claude/agents/azure-verified-modules-bicep.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code
Manually: put the files in place
.codex/agents/azure-verified-modules-bicep.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/azure-verified-modules-bicep.mdCursor also reads .claude/agents/
From the same set554
The whole set →Similar
Questions about Azure AVM Bicep mode
How to install Azure AVM Bicep mode in GitHub Copilot?
Add the agent file to your project at .cursor/agents/azure-verified-modules-bicep.md, .claude/agents/azure-verified-modules-bicep.md, or .codex/agents/azure-verified-modules-bicep.md. This configuration activates the Bicep module workflow.
What does Azure AVM Bicep mode do?
The subagent guides the creation and review of Bicep code using Azure Verified Modules. It pulls official examples and enforces version pinning for every module.
Which tools does the subagent use to validate code?
It relies on azure_get_schema_for_Bicep for schema validation and azure_get_deployment_best_practices for deployment guidance. It also triggers bicep lint after modifying templates.
Source text
azure-verified-modules-bicep.agent.md · MIT
---
description: "Create, update, or review Azure IaC in Bicep using Azure Verified Modules (AVM)."
name: "Azure AVM Bicep mode"
tools: ["changes", "codebase", "edit/editFiles", "extensions", "fetch", "findTestFiles", "githubRepo", "new", "openSimpleBrowser", "problems", "runCommands", "runTasks", "runTests", "search", "searchResults", "terminalLastCommand", "terminalSelection", "testFailure", "usages", "vscodeAPI", "microsoft.docs.mcp", "azure_get_deployment_best_practices", "azure_get_schema_for_Bicep"]
---
# Azure AVM Bicep mode
Use Azure Verified Modules for Bicep to enforce Azure best practices via pre-built modules.
## Discover modules
- AVM Index: `https://azure.github.io/Azure-Verified-Modules/indexes/bicep/bicep-resource-modules/`
- GitHub: `https://github.com/Azure/bicep-registry-modules/tree/main/avm/`
## Usage
- **Examples**: Copy from module documentation, update parameters, pin version
- **Registry**: Reference `br/public:avm/res/{service}/{resource}:{version}`
## Versioning
- MCR Endpoint: `https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list`
- Pin to specific version tag
## Sources
- GitHub: `https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}`
- Registry: `br/public:avm/res/{service}/{resource}:{version}`
## Naming conventions
- Resource: avm/res/{service}/{resource}
- Pattern: avm/ptn/{pattern}
- Utility: avm/utl/{utility}
## Best practices
- Always use AVM modules where available
- Pin module versions
- Start with official examples
- Review module parameters and outputs
- Always run `bicep lint` after making changes
- Use `azure_get_deployment_best_practices` tool for deployment guidance
- Use `azure_get_schema_for_Bicep` tool for schema validation
- Use `microsoft.docs.mcp` tool to look up Azure service-specific guidance
© github · MIT · github/awesome-copilot