Skip to content
Azure Deploy

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.

GitHub Docs

Install

Install with the skills CLI

One command for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf and dozens of other agents. Needs Node.js; the skill is fetched straight from microsoft/azure-skills.

$ npx skills add microsoft/azure-skills --skill azure-deploy

Run it in a terminal. The CLI finds the agents installed on your machine, asks which ones to add the skill to, and whether to install it into the folder you ran it from or for all your projects.

Other ways to install

Copy the whole skill folder — SKILL.md and any scripts or references beside it — into ~/.claude/skills/azure-deploy/, where Claude Code picks it up in every project. Only git is needed.

tmp=$(mktemp -d) && \
  git clone --depth 1 --branch main https://github.com/microsoft/azure-skills.git "$tmp" && \
  mkdir -p ~/.claude/skills && \
  cp -R "$tmp"/skills/azure-deploy ~/.claude/skills/azure-deploy

No scripts or references next to it? Saving the SKILL.md alone as ~/.claude/skills/azure-deploy/SKILL.md works too.

Using another agent? Its personal skills folder
Codex
~/.agents/skills/
Cursor
~/.cursor/skills/
GitHub Copilot
~/.copilot/skills/
Gemini CLI
~/.gemini/skills/
Windsurf
~/.codeium/windsurf/skills/
OpenCode
~/.config/opencode/skills/

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.

SKILL.md
name
azure-deploy
description
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: \"run azd up\", \"run azd deploy\", \"execute deployment\", \"push to production\", \"push to cloud\", \"go live\", \"ship it\", \"bicep deploy\", \"terraform apply\", \"publish to Azure\", \"launch on Azure\". DO NOT USE WHEN: \"create and deploy\", \"build and deploy\", \"create a new app\", \"set up infrastructure\", \"create and deploy to Azure using Terraform\" — use azure-prepare for these.
license
MIT
metadata
author: Microsoft version: "1.2.2"

Azure Deploy

AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE

PREREQUISITE: The azure-validate skill MUST be invoked and completed with status Validated BEFORE executing this skill.
⛔ STOP — PREREQUISITE CHECK REQUIRED
Before proceeding, verify BOTH prerequisites are met:

1. azure-prepare was invoked and completed → .azure/deployment-plan.md exists
2. azure-validate was invoked and passed → plan status = Validated

If EITHER is missing, STOP IMMEDIATELY:
- No plan? → Invoke azure-prepare skill first
- Status not Validated? → Invoke azure-validate skill first

⛔ DO NOT MANUALLY UPDATE THE PLAN STATUS

You are FORBIDDEN from changing the plan status to Validated yourself. Only the azure-validate skill is authorized to set this status after running actual validation checks. If you update the status without running validation, deployments will fail.

DO NOT ASSUME the app is ready. DO NOT SKIP validation to save time. Skipping steps causes deployment failures. The complete workflow ensures success:

azure-prepare → azure-validate → azure-deploy
Triggers

Activate this skill when user wants to:

  • Execute deployment of an already-prepared application (azure.yaml and infra/ exist)
  • Push updates to an existing Azure deployment
  • Run azd up, azd deploy, or az deployment on a prepared project
  • Ship already-built code to production
  • Deploy an application that already includes API Management (APIM) gateway infrastructure
Scope: This skill executes deployments. It does not create applications, generate infrastructure code, or scaffold projects. For those tasks, use azure-prepare.
APIM / AI Gateway: Use this skill to deploy applications whose APIM/AI gateway infrastructure was already created during azure-prepare. For creating or changing APIM resources, see APIM deployment guide. For AI governance policies, invoke azure-aigateway skill.
Rules
  1. Run after azure-prepare and azure-validate
  2. .azure/deployment-plan.md must exist with status Validated
  3. Pre-deploy checklist required — [Pre-Deploy Checklist](references/pre-deploy-checklist.md)
  4. ⛔ Destructive actions require `ask_user` — [global-rules](references/global-rules.md)
  5. Scope: deployment execution only — This skill owns execution of azd up, azd deploy, terraform apply, and az deployment commands. These commands are run through this skill's error recovery and verification pipeline.

---

Steps
#ActionReference
1Check Plan — Read .azure/deployment-plan.md, verify status = Validated AND Validation Proof section is populated.azure/deployment-plan.md
2Pre-Deploy Checklist — MUST complete ALL steps[Pre-Deploy Checklist](references/pre-deploy-checklist.md)
3Load Recipe — Based on recipe.type in .azure/deployment-plan.md[recipes/README.md](references/recipes/README.md)
4RBAC Health Check — For Container Apps + ACR with managed identity: run azd provision --no-prompt, then verify AcrPull role has propagated before proceeding (see checklist)[Pre-Deploy Checklist — Container Apps RBAC](references/pre-deploy-checklist.md#container-apps--acr--pre-deploy-rbac-health-check)
5Execute Deploy — Follow recipe stepsRecipe README
6Post-Deploy — Configure SQL managed identity and apply EF migrations if applicable[Post-Deployment](references/recipes/azd/post-deployment.md)
7Handle Errors — See recipe's errors.md—
8Verify Success — Confirm deployment completed and endpoints are accessible[Verification](references/recipes/azd/verify.md)
9Live Role Verification — Query Azure to confirm provisioned RBAC roles are correct and sufficient[live-role-verification.md](references/live-role-verification.md)
10Report Results — Present deployed endpoint URLs to the user as fully-qualified https:// links[Verification](references/recipes/azd/verify.md)
⛔ URL FORMAT RULE

When presenting endpoint URLs to the user, you MUST always use fully-qualified URLs with the https:// scheme (e.g. https://myapp.azurewebsites.net, not myapp.azurewebsites.net). Many Azure CLI commands return bare hostnames without a scheme — always prepend https:// before presenting them.
⛔ VALIDATION PROOF CHECK

When checking the plan, verify the Validation Proof section (Section 7) contains actual validation results with commands run and timestamps. If this section is empty, validation was bypassed — invoke azure-validate skill first.
SDK Quick References
  • Azure Developer CLI: [azd](references/sdk/azd-deployment.md)
  • Azure Identity: [Python](references/sdk/azure-identity-py.md) | [.NET](references/sdk/azure-identity-dotnet.md) | [TypeScript](references/sdk/azure-identity-ts.md) | [Java](references/sdk/azure-identity-java.md)
MCP Tools
ToolPurpose
mcp_azure_mcp_subscription_listList available subscriptions
mcp_azure_mcp_group_listList resource groups in subscription
mcp_azure_mcp_azdExecute AZD commands
azure__roleList role assignments for live RBAC verification (step 9)
References
  • [Troubleshooting](references/troubleshooting.md) - Common issues and solutions
  • [Post-Deployment Steps](references/recipes/azd/post-deployment.md) - SQL + EF Core setup
Install
New

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.

New

Microsoft'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.

New

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.

Browse all skills →