azure-developer-cli

Designs, reviews, and troubleshoots Azure Developer CLI projects with azure.yaml, IaC, and CI/CD guidance.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/serpro-workshop-fortaleza/sifap-modernization-paula --skill azure-developer-cli-serpro-workshop-fortaleza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-developer-cli
Source: https://github.com/serpro-workshop-fortaleza/sifap-modernization-paula/tree/main/.github/skills/azure-developer-cli
Command: npx skills add https://github.com/serpro-workshop-fortaleza/sifap-modernization-paula --skill azure-developer-cli-serpro-workshop-fortaleza

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Structuring and operating Azure Developer CLI (azd) projects correctly is error-prone: misconfigured azure.yaml manifests, leaked secrets, wrong IaC provider assumptions, and unsafe deployment commands can break environments or expose credentials. This Skill provides current Microsoft-aligned guidance for building, reviewing, migrating, and troubleshooting azd projects safely. ## Core Features & Use Cases - Project Modeling: Defines services, infrastructure entry points, and environments in azure.yaml following azd conventions, with Terraform as the default IaC provider in this kit and Bicep covered as reference. - Security Guardrails: Enforces managed identity, Key Vault references, and azd env set-secret practices while blocking cloud-mutating commands (azd up, provision, deploy, down) without explicit approval. - CI/CD and Operations: Guides pipeline design with OIDC federation, remote state configuration, hooks, validation commands, and structured troubleshooting sequences. - Use Case: A developer asks to review an azure.yaml and infra/ folder before deploying to a staging environment; the Skill checks service paths, IaC provider alignment, secret handling, and runs terraform validate before reporting findings. ## Quick Start Ask the assistant to review your azure.yaml and infra directory for azd best-practice issues before running azd provision.

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 with azure.yaml?

Place azure.yaml at the repository root, define one services entry per independently deployable component under src/<service-name>, and keep infrastructure in an infra directory with a lean main.bicep or main.tf entry point. Declare the infra provider, path, and module explicitly to match the actual repository layout.

Should I use Bicep or Terraform with the Azure Developer CLI?

Bicep is the default azd IaC provider and fits Azure-only projects wanting stateless deployment. Use Terraform when the repository already uses it or the team has established module and state practices; note Microsoft currently classifies azd Terraform support as beta.

How do I manage secrets in azd environments?

Prefer managed identity with RBAC first, then use azd env set-secret to store a Key Vault reference in the environment. Never commit .azure directories, .env files, or place secrets in azure.yaml, IaC outputs, or command-line arguments that get logged.

Why does azd provision fail in my staging environment?

First isolate whether the failure is in packaging, provisioning, deployment, hooks, or authentication, then rerun only the failing phase. Verify the selected environment, subscription, tenant, and region, and run azd env refresh if another agent changed deployment outputs.

Does azd pipeline config support Terraform with OIDC authentication?

Current Microsoft documentation states azd pipeline config is beta and that azd pipelines with Terraform do not support OIDC federation. Evaluate the authentication tradeoff explicitly and configure protected remote Terraform state before setting up the pipeline.