Azure deploy skill

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files.

by microsoft·MIT license·★ 3,077 Stars on the repo·GitHub ↗

Use now

Files of Azure deploy

microsoft/main1 file shown
SKILL.md
Show the full text98 lines
azure-deploy/SKILL.md98 lines · 6.5 KB

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
  4. ⛔ Destructive actions require ask_user — global-rules
  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

# Action Reference
1 Check Plan — Read .azure/deployment-plan.md, verify status = Validated AND Validation Proof section is populated .azure/deployment-plan.md
2 Pre-Deploy Checklist — MUST complete ALL steps Pre-Deploy Checklist
3 Load Recipe — Based on recipe.type in .azure/deployment-plan.md 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) Pre-Deploy Checklist — Container Apps RBAC
5 Execute Deploy — Follow recipe steps Recipe README
6 Post-Deploy — Configure SQL managed identity and apply EF migrations if applicable Post-Deployment
7 Handle Errors — See recipe's errors.md —
8 Verify Success — Confirm deployment completed and endpoints are accessible Verification
9 Live Role Verification — Query Azure to confirm provisioned RBAC roles are correct and sufficient live-role-verification.md
10 Report Results — Present deployed endpoint URLs to the user as fully-qualified https:// links Verification

⛔ 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

MCP Tools

Tool Purpose
mcp_azure_mcp_subscription_list List available subscriptions
mcp_azure_mcp_group_list List resource groups in subscription
mcp_azure_mcp_azd Execute AZD commands
azure__role List role assignments for live RBAC verification (step 9)

References

1---
2name: azure-deploy
3description: "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."
4license: MIT
5metadata:
6 author: Microsoft
7 version: "1.2.2"
8---
9 
10# Azure Deploy
11 
12> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**
13>
14> **PREREQUISITE**: The **azure-validate** skill **MUST** be invoked and completed with status `Validated` BEFORE executing this skill.
15 
16> **⛔ STOP — PREREQUISITE CHECK REQUIRED**
17> Before proceeding, verify BOTH prerequisites are met:
18>
19> 1. **azure-prepare** was invoked and completed → `.azure/deployment-plan.md` exists
20> 2. **azure-validate** was invoked and passed → plan status = `Validated`
21>
22> If EITHER is missing, **STOP IMMEDIATELY**:
23> - No plan? → Invoke **azure-prepare** skill first
24> - Status not `Validated`? → Invoke **azure-validate** skill first
25>
26> **⛔ DO NOT MANUALLY UPDATE THE PLAN STATUS**
27>
28> 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.
29>
30> **DO NOT ASSUME** the app is ready. **DO NOT SKIP** validation to save time. Skipping steps causes deployment failures. The complete workflow ensures success:
31>
32> `azure-prepare` → `azure-validate` → `azure-deploy`
33 
34## Triggers
35 
36Activate this skill when user wants to:
37- Execute deployment of an already-prepared application (azure.yaml and infra/ exist)
38- Push updates to an existing Azure deployment
39- Run `azd up`, `azd deploy`, or `az deployment` on a prepared project
40- Ship already-built code to production
41- Deploy an application that already includes API Management (APIM) gateway infrastructure
42 
43> **Scope**: This skill executes deployments. It does not create applications, generate infrastructure code, or scaffold projects. For those tasks, use **azure-prepare**.
44 
45> **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](https://learn.microsoft.com/azure/api-management/get-started-create-service-instance). For AI governance policies, invoke **azure-aigateway** skill.
46 
47## Rules
48 
491. Run after azure-prepare and azure-validate
502. `.azure/deployment-plan.md` must exist with status `Validated`
513. **Pre-deploy checklist required** — [Pre-Deploy Checklist](references/pre-deploy-checklist.md)
524. ⛔ **Destructive actions require `ask_user`** — [global-rules](references/global-rules.md)
535. **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.
54 
55---
56 
57## Steps
58 
59| # | Action | Reference |
60|---|--------|-----------|
61| 1 | **Check Plan** — Read `.azure/deployment-plan.md`, verify status = `Validated` AND **Validation Proof** section is populated | `.azure/deployment-plan.md` |
62| 2 | **Pre-Deploy Checklist** — MUST complete ALL steps | [Pre-Deploy Checklist](references/pre-deploy-checklist.md) |
63| 3 | **Load Recipe** — Based on `recipe.type` in `.azure/deployment-plan.md` | [recipes/README.md](references/recipes/README.md) |
64| 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) | [Pre-Deploy Checklist — Container Apps RBAC](references/pre-deploy-checklist.md#container-apps--acr--pre-deploy-rbac-health-check) |
65| 5 | **Execute Deploy** — Follow recipe steps | Recipe README |
66| 6 | **Post-Deploy** — Configure SQL managed identity and apply EF migrations if applicable | [Post-Deployment](references/recipes/azd/post-deployment.md) |
67| 7 | **Handle Errors** — See recipe's `errors.md` | — |
68| 8 | **Verify Success** — Confirm deployment completed and endpoints are accessible | [Verification](references/recipes/azd/verify.md) |
69| 9 | **Live Role Verification** — Query Azure to confirm provisioned RBAC roles are correct and sufficient | [live-role-verification.md](references/live-role-verification.md) |
70| 10 | **Report Results** — Present deployed endpoint URLs to the user as fully-qualified `https://` links | [Verification](references/recipes/azd/verify.md) |
71 
72> **⛔ URL FORMAT RULE**
73>
74> 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.
75 
76> **⛔ VALIDATION PROOF CHECK**
77>
78> 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.
79 
80## SDK Quick References
81 
82- **Azure Developer CLI**: [azd](references/sdk/azd-deployment.md)
83- **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)
84 
85## MCP Tools
86 
87| Tool | Purpose |
88|------|---------|
89| `mcp_azure_mcp_subscription_list` | List available subscriptions |
90| `mcp_azure_mcp_group_list` | List resource groups in subscription |
91| `mcp_azure_mcp_azd` | Execute AZD commands |
92| `azure__role` | List role assignments for live RBAC verification (step 9) |
93 
94## References
95 
96- [Troubleshooting](references/troubleshooting.md) - Common issues and solutions
97- [Post-Deployment Steps](references/recipes/azd/post-deployment.md) - SQL + EF Core setup
98 

Discussion

Alternatives

Azure app onboardEnd-to-end orchestrator: from a business idea, app idea, or existing app to running Azure deployment with cost estimates and pre-deploy approval. Analyzes your app, auto-detects the right Azure services, scaffolds infrastructure code, and deploys — tailored to your app, not a template. Handles moving existing apps to Azure without rewriting or with minimal changes. WHEN: bring your app to Azure, plan my app, cost to run, is my code ready to deploy, deploy my app to the cloud, deploy all my services, what Azure services do I need, plan my Azure deployment, deploy my new app to Azure, one-click deploy, I have an app and want it on Azure, migrate my app to Azure, help me get started, build an app, no code yet, starter project. DO NOT USE FOR: use azd for deployment(use azure-deploy), optimizing existing costs (use cost-optimization), code readiness checks only (use azure-app-onboard-prereq).Infrastructure & ops · MITAzure App Onboard Prereq — Repository EvaluationAssess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility. Answers questions about what your app needs before it can be deployed — frameworks, dependencies, and configuration. Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks. WHEN: "evaluate my repo", "is my app ready to deploy", "what does my app need to deploy", "what do I need before deploying", "does my app need", "can I ship this to Azure", "scan my repo for issues", "is this app deployable", "check if my app is ready for Azure", "do I need a Dockerfile", "what's blocking my deployment", "are there any blockers", "are my dependencies compatible", "does Azure support my framework", "what needs to change before deploying", "check my app configuration".Infrastructure & ops · MITDocker MCP gatewayDocker's own CLI plugin: run any server from the Docker MCP Catalog in its own container, behind one connection, with secrets kept out of env vars.Coding · MITAzure cloud migrateAssess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration.Infrastructure & ops · MIT