azure-developer-cli

Design, review, and troubleshoot Azure Developer CLI projects using azure.yaml, Bicep, and Terraform.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill azure-developer-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-developer-cli
Source: https://github.com/github/awesome-copilot/tree/main/skills/azure-developer-cli
Command: npx skills add https://github.com/github/awesome-copilot --skill azure-developer-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Building and maintaining Azure Developer CLI (azd) projects involves many moving parts—azure.yaml manifests, Bicep or Terraform infrastructure, environments, secrets, hooks, and CI/CD pipelines—where small misconfigurations cause failed deployments or leaked secrets. This Skill guides the creation, review, migration, and troubleshooting of azd projects against current Microsoft guidance.

Core Features & Use Cases

  • Project Modeling: Define services, infrastructure entry points, and environment strategies in azure.yaml following recommended repository layouts.
  • Safety Guardrails: Prevent committing secrets, .azure state, or Terraform state, and enforce confirmation before resource-changing commands like azd up or azd down.
  • Validation & CI/CD: Run Bicep builds, Terraform validation, hook tests, and design pipelines with workload identity federation and protected environments.
  • Use Case: When migrating an existing app to azd, the Skill inspects azure.yaml, aligns the Bicep modules and parameters, configures remote state, and sets up a GitHub Actions pipeline with OIDC authentication.

Quick Start

Ask the agent to review your azure.yaml and infra folder and create a deployable azd project structure for your application.

Frequently Asked Questions about azure-developer-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure an Azure Developer CLI project?

Place azure.yaml at the repository root, keep application code under src/<service-name>, and put infrastructure in an infra folder with a thin main.bicep or main.tf entry point plus reusable modules. Define one services entry per independently deployable component.

Should I use Bicep or Terraform with azd?

Bicep is azd's default provider and suits Azure-only projects wanting a stateless model. Choose Terraform when the repository already uses it or cross-provider infrastructure is required, noting that azd Terraform support is currently marked beta.

How do I manage secrets in azd environments?

Prefer managed identities with RBAC first, then use azd env set-secret to store Key Vault references. Never commit .azure folders, .env files, or put literal secrets in azure.yaml, IaC parameters, or outputs.

Does azd pipeline config support OIDC authentication?

For GitHub Actions, azd pipeline config sets up OIDC federated credentials by default in supported scenarios. However, current documentation states the Terraform pipeline flow does not support OIDC, so evaluate that authentication tradeoff explicitly.

Why does my azd deployment fail after infrastructure changed externally?

Deployment outputs cached in the AZD environment may be stale. Run azd env refresh to synchronize outputs, then verify the selected environment, subscription, and that azure.yaml service settings match the actual source projects.