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.
Azure Deploy Skill
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.
Install
Other ways to install
About
- Refuses to run without a Validated .azure/deployment-plan.md from azure-prepare and azure-validate
- Executes azd up, azd deploy, terraform apply and az deployment through recipe-specific guides
- Pre-deploy checklist including an AcrPull RBAC propagation check for Container Apps
- Post-deploy SQL managed identity setup and EF Core migrations
- Verifies endpoints and live role assignments after deployment
- Asks the user before destructive actions and reports full https:// endpoint URLs
Azure Deploy is the execution step of the deployment workflow in Microsoft's microsoft/azure-skills repository. It is deliberately narrow: it does not create applications or write infrastructure code, it ships projects that have already been prepared and validated by its sibling skills, in the fixed order azure-prepare → azure-validate → azure-deploy.
Before doing anything the agent must find .azure/deployment-plan.md with the status Validated and a populated Validation Proof section, and it is explicitly forbidden from setting that status itself. If the plan is missing or unvalidated, it stops and calls the earlier skill instead.
The run itself is a ten-step table: check the plan, complete a pre-deploy checklist, load the recipe named by recipe.type in the plan (the recipes ship under references/recipes/), run an RBAC health check for Container Apps pulling from Azure Container Registry with managed identity, execute the deployment, apply post-deploy steps such as SQL managed identity and EF Core migrations, handle errors from the recipe's own error guide, verify the endpoints, confirm the provisioned role assignments against live Azure, and report every endpoint as a full https:// URL. Destructive actions require asking the user first.
It triggers on phrases like "run azd up", "terraform apply", "push to production" or "publish to Azure", and steers "create and deploy" requests back to azure-prepare. It also deploys apps whose API Management / AI gateway infrastructure was set up during preparation. Requirements are an Azure subscription, the Azure Developer CLI or Azure CLI (or Terraform, depending on the recipe) and, optionally, the Azure MCP server, whose subscription, resource-group, azd and role tools it lists. MIT licensed.
SKILL.md
The instructions your agent loads, as published by Microsoft.
Related Skills
See all Azure Deploy 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.