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\"…
Execute Azure deployments for prepared applications with built-in error recovery and validation.
Requires .azure/plan.md with Validated status from azure-validate and azure-prepare skills; will not proceed without both prerequisites Executes azd up , azd deploy , terraform apply , and az deployment commands with error handling and post-deployment verification Includes pre-deploy checklist, recipe-based deployment workflows, and post-deploy configuration for SQL managed identity and Entity Framework migrations Supports applications with API Management gateway infrastructure created during preparation phase
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
The 'azure-deploy' skill provides a robust framework for executing Azure deployments using official tools like the Azure Developer CLI (azd) and Terraform. It integrates security best practices such as managed identities, mandatory user confirmation for destructive actions, and the use of trusted Microsoft infrastructure for tool installation.
snykLOW
Analyzed May 4, 2026
No issues detected.
socketScore 0.9000 · 0 alerts
Analyzed May 4, 2026
license1
maintenance1
quality0.9
supply chain1
vulnerability1
0 alerts
Also in this package
Other skills from microsoft/azure-skills · top by installs.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars1.5K
LicenseMIT
Default branchmain
Open issues9
Last pushSep 10, 2026
Status
Active
Skill metadata
Parsed from SKILL.md frontmatter.
Version1.2.1
LicenseMIT
More metadata
author
Microsoft
version
1.2.1
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md6,632 B
docsSUMMARY.md864 B
History
First seen on skills.sh
SKILL.md last updated on GitHub
First recorded snapshot · 569,425 installs
SKILL.md
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
Run after azure-prepare and azure-validate
.azure/deployment-plan.md must exist with status Validated
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
#
Action
Reference
1
Check Plan — Read .azure/deployment-plan.md, verify status = Validated AND Validation Proof section is populated
Load Recipe — Based on recipe.type in .azure/deployment-plan.md
[recipes/README.md](references/recipes/README.md)
4
RBAC Health Check — For Container Apps + ACR with managed identity: run azd provision --no-prompt, then verify AcrPull role has propagated before proceeding (see checklist)
Report 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.
