Microsoft's official skill for executing Azure deployments of already-prepared apps: it checks for a validated deployment plan, runs azd up, azd deploy, terraform apply or az deployment with error recovery, then verifies endpoints and RBAC roles.
Azure Prepare Skill
Microsoft's official skill for preparing apps for Azure with the Azure Developer CLI: writes a deployment plan first, then generates azure.yaml, Bicep or Terraform infrastructure and Dockerfiles before handing off to validation.
Install
Other ways to install
About
- Writes .azure/deployment-plan.md before any code and waits for user approval
- Generates azure.yaml, Bicep or Terraform under ./infra/ and per-component Dockerfiles
- Routes Python App Service, AWS/GCP migration and AI gateway requests to specialised skills
- Covers Azure Functions hosting plans, API Management and durable workflow recipes
- Entra-only authentication for SQL Server; never deletes the user's project directories
- Hands off to azure-validate, then azure-deploy, instead of deploying itself
Azure Prepare is the first step of the deployment workflow in Microsoft's microsoft/azure-skills repository, ahead of azure-validate and azure-deploy. It is for projects that will ship with the Azure Developer CLI (azd) or that already contain an azure.yaml, and it deliberately stops short of deploying: its job is to produce the plan, the infrastructure code and the configuration.
Its defining rule is plan first. Before generating anything the agent must write a .azure/deployment-plan.md skeleton in the workspace root, fill it in while it analyses the workspace (new, modify or modernize), gathers requirements, scans the codebase, picks a recipe (azd by default, or Azure CLI, Bicep or Terraform) and maps components to Azure services, then present it and wait for approval. A step-zero routing table sends Python-on-App-Service requests, AWS or GCP migrations and AI gateway work to dedicated skills, and keeps Azure Functions, API Management and durable workflow requests in this one with specific references.
After approval it researches each service, confirms the subscription and region, generates ./infra/, azure.yaml and per-component Dockerfiles, applies security hardening, verifies the app works, sets the plan status to Ready for Validation and invokes azure-validate. Hard rules include never deleting the user's project directories, asking before destructive actions, and never generating SQL Server admin logins in Bicep (Entra-only authentication instead). Requires an Azure subscription and azd or the Azure CLI. MIT licensed.
SKILL.md
The instructions your agent loads, as published by Microsoft.
Related Skills
See all Azure Prepare alternativesMicrosoft's official skill for building, deploying, evaluating, fine-tuning and operating agents and models on Microsoft Foundry with azd and the Foundry MCP tools, from project setup and RBAC to quota, tracing and CI/CD.
Microsoft's official skill for troubleshooting Azure production issues: App Service, Container Apps, Functions, AKS, VMs and messaging, using AppLens, Azure Monitor, resource health and KQL.
Skill: Azure Kubernetes Service (AKS)
by Microsoft
Microsoft's official AKS planning skill: separates the Day-0 decisions you cannot undo (networking, API server) from the Day-1 features you can switch on later.