Guide · Agent skill
How to use the Azure Developer CLI Helper agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Azure Developer CLI (azd) helper skill is a set of instructions and reference notes that an AI agent loads when you ask for help with an azd project. It covers azure.yaml, infrastructure code in Bicep or Terraform, azd environments and secrets, hooks, and CI/CD. This guide explains what the skill changes about the agent's behaviour, how to install it, how to ask for things in plain language, and what to check before letting it touch Azure.
Azure Developer CLI Helpergithub/awesome-copilot · MIT Download the skill Quick start
- 1Download and unzip. Download the skill ZIP from this page and unzip it so the azure-developer-cli folder with SKILL.md is in place.
- 2Choose the install location. Place the folder in ~/.claude/skills/ for personal use, in a project's .claude/skills/ folder, or upload it under Settings → Capabilities → Skills in the Claude apps.
- 3Install the prerequisites. Install the Azure Developer CLI and, depending on your IaC provider, the Azure CLI with Bicep tooling or Terraform.
- 4Ask a plain-language question. Open your azd project and describe the task, mentioning azd, azure.yaml or your IaC provider.
- 5Review the agent's plan. Read which files it will read and which azd commands it intends to run before approving anything.
- 6Approve named actions only. Confirm the environment, subscription and scope before any command that provisions, deploys or destroys resources.
What the skill makes the agent do
Without the skill, an agent answering an azd question relies on general knowledge. With the skill installed, the agent follows a defined workflow: it finds and reads azure.yaml and the configured infra path first, identifies whether the task is to create, migrate, review, deploy, or troubleshoot, and then reads the matching reference note before editing anything.
The skill also sets rules for safety. The agent is told never to commit .azure folders, environment .env files, or local Terraform state, and never to put literal secrets in azure.yaml or IaC files. It is told to prefer managed identities and RBAC, and to ask before running commands such as azd up, azd provision, azd deploy, azd down, or azd pipeline config unless you explicitly asked for that named action.
- Reads azure.yaml before inferring services or the IaC provider
- Keeps environments separate and uses azd env commands instead of editing .env files
- Adds hooks only for lifecycle gaps that declarative IaC does not cover
- Runs only the validation checks that apply to your repository
Install the skill from the ZIP download
Download the ZIP for this skill from this page and unzip it. The folder contains SKILL.md, a references folder, and an examples folder with azure.yaml. Place the folder in one of two locations depending on how you want to use it.
For a personal install available across your projects, unzip it into ~/.claude/skills/. To limit it to one project, unzip it into the .claude/skills/ folder inside that project. In the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/
- Single project: .claude/skills/ inside the project folder
- Claude apps: Settings → Capabilities → Skills
Trigger the skill with natural requests
You do not need a special command. Describe the azd task in plain language and mention azd, azure.yaml, Bicep, Terraform, environments, hooks, or pipelines so the agent recognises the topic. The skill's description lists these terms, which is what makes it load.
Be specific about the goal. A request to review a template before you deploy it gets a different workflow than a request to troubleshoot a failing hook.
- "Review this azd template's azure.yaml and infra folder before I deploy it."
- "Set up a dev environment for this azd project and tell me what to check first."
- "My azd hook fails on Windows but works on Linux. Find out why."
- "Add a GitHub Actions pipeline with azd pipeline config, but show me the changes first."
What you need before using it
The skill is guidance for an agent; the work still runs on your machine and your Azure account. Install the Azure Developer CLI (azd) to run azd commands. Install the Azure CLI and Bicep tooling for Bicep validation, or Terraform for Terraform checks. Most tasks that touch cloud resources need an Azure subscription and credentials.
The skill declares that it runs scripts and uses the network. Treat it like any other tool you add to an agent.
- Azure Developer CLI (azd)
- Azure CLI and Bicep tooling, or Terraform, depending on your IaC provider
- An Azure subscription and credentials for any command that touches cloud resources
Safety notes: scripts, network and cloud changes
The skill is documented as running scripts and using the network. Its validation steps can authenticate to Azure or read remote state. Before the agent runs a command that creates, changes or deletes resources, it should confirm the target environment, subscription, tenant, region and expected scope.
Approval is the main control. Explicit requests to deploy, provision, destroy or configure a pipeline count as approval only for that named action. A vague request such as "get this running" should not be treated that way. Read each proposed command before you confirm it.
- Check the environment name and subscription before approving azd up or azd down
- Review generated pipeline changes from azd pipeline config before committing them
- Keep Azure credentials out of prompts, files and command arguments
Tips for better results
Point the agent at the project root so it can find azure.yaml. Name the environment you mean, for example dev, so the agent uses -e or --environment explicitly. If you are migrating a template, say so, because the skill asks the agent to preserve existing conventions when they are already coherent.
For Terraform projects, note that the skill's reference material marks AZD Terraform support as beta, and the agent is instructed to surface that rather than migrate you to Terraform.
- Start with a review request before a change request
- Name the environment and subscription in the prompt
- Ask the agent to list the commands it intends to run
azd env listWhat people use it for
- Reviewing an azd template's azure.yaml and infra folder before the first deployment
- Setting up separate dev and production environments with azd env commands
- Troubleshooting a hook that behaves differently on Windows and POSIX shells
- Preparing a Bicep or Terraform project for validation before running a pipeline
- Checking that .gitignore excludes .azure folders and secrets before committing
Frequently asked questions
How do I install the azure developer cli agent skill?
Download the skill ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into .claude/skills/ inside a project. In the Claude apps you can upload it under Settings → Capabilities → Skills.
What do I need to use this skill?
You need the Azure Developer CLI installed to run azd commands, plus the Azure CLI and Bicep tooling or Terraform for validation. Any task that touches cloud resources also needs an Azure subscription and credentials.
Is the azure developer cli skill free?
The skill is published under the MIT licence on the github/awesome-copilot repository. This page does not list pricing for Azure itself, so check Azure's own billing for any resources a deployment creates.
Will the agent deploy to Azure without asking me?
Not by default. The skill tells the agent to confirm the target before commands that create, modify or delete resources, and to ask before running azd up, azd provision, azd deploy, azd down or azd pipeline config unless you explicitly request that action.
Does the skill work with Terraform as well as Bicep?
Yes, it covers both. Bicep is azd's default provider, and the skill's reference notes say current Microsoft documentation marks AZD Terraform support as beta.
Can I use this skill for a project that does not use Azure?
No. The guidance is specific to azd and Azure resources, so it is not suited to projects that deploy elsewhere.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits developers setting up, reviewing or troubleshooting an azd project with Bicep or Terraform, and teams checking a template before deploying it. It is a poor fit for non-Azure projects, or for anyone who wants an agent to deploy unattended, since it is built to pause for confirmation before cloud changes.
Download the skill