PluginBench
Skill
Official
Review
Audit score 70

azure-deploy

microsoft/azure-skills

Execute Azure deployments for prepared applications with built-in error recovery and validation.

SourceView on skills.sh

What is azure-deploy?

Deploys already-prepared Azure applications using azd, Terraform, or Bicep commands. Use this after azure-prepare and azure-validate have completed. Handles deployment execution, error recovery, and post-deployment verification for Container Apps, App Service, and other Azure resources.

  • Executes azd up, azd deploy, terraform apply, and az deployment commands
  • Performs pre-deploy checklist validation and RBAC health checks
  • Loads and follows recipe-specific deployment steps based on infrastructure type
  • Handles post-deployment tasks including SQL managed identity and EF Core migrations
  • Verifies deployment success and confirms endpoint accessibility
  • Performs live RBAC role verification against Azure

How to install azure-deploy

npx skills add https://github.com/microsoft/azure-skills --skill azure-deploy
Prerequisites
  • .azure/deployment-plan.md must exist with status 'Validated' (from azure-prepare)
  • azure-validate skill must be invoked and completed successfully before running this skill
  • Azure CLI and Azure Developer CLI (azd) installed and authenticated
  • Appropriate Azure RBAC permissions for the target subscription and resource group
Claude Code
Cursor
Windsurf
Cline

How to use azure-deploy

  1. 1.Verify .azure/deployment-plan.md exists and has status 'Validated'
  2. 2.Complete the pre-deploy checklist (credentials, resource group, quotas, RBAC)
  3. 3.Run RBAC health check for Container Apps + ACR if applicable
  4. 4.Execute deployment using the appropriate recipe (azd up, terraform apply, etc.)
  5. 5.Complete post-deployment steps (SQL managed identity, EF migrations if needed)
  6. 6.Verify deployment success and endpoint accessibility
  7. 7.Perform live RBAC role verification against Azure
  8. 8.Review and confirm fully-qualified endpoint URLs

Use cases

Good for
  • Push updates to an existing Azure deployment after code changes
  • Execute production deployments of Container Apps or App Service applications
  • Deploy Terraform or Bicep infrastructure to Azure after validation
  • Ship prepared applications to Azure with automatic error recovery
  • Verify and configure RBAC roles and managed identities post-deployment
Who it's for
  • DevOps engineers executing prepared deployments
  • Developers shipping applications to Azure production
  • Teams using Azure Developer CLI (azd) workflows
  • Infrastructure teams deploying Terraform or Bicep templates

azure-deploy FAQ

When should I use azure-deploy vs azure-prepare?

Use azure-deploy only when you already have a prepared application with .azure/deployment-plan.md and azure-validate has passed. Use azure-prepare to create new applications or set up infrastructure from scratch.

What happens if azure-validate hasn't been run?

Do not proceed. You must invoke azure-validate first and confirm the plan status is 'Validated'. Skipping validation causes deployment failures.

Can I manually update the plan status to 'Validated'?

No. Only the azure-validate skill is authorized to set the status after running actual validation checks. Manually changing the status will cause deployments to fail.

What if deployment fails?

Check the recipe's errors.md file for your infrastructure type, review the error message, and follow the troubleshooting steps. Common issues include RBAC propagation delays, quota limits, or missing credentials.

How are endpoint URLs presented?

All endpoint URLs are presented as fully-qualified https:// URLs (e.g., https://myapp.azurewebsites.net), even if Azure CLI returns bare hostnames.

Full instructions (SKILL.md)

Source of truth, from microsoft/azure-skills.


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.1"

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

#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 stepsPre-Deploy Checklist
3Load Recipe — Based on recipe.type in .azure/deployment-plan.mdrecipes/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
5Execute Deploy — Follow recipe stepsRecipe README
6Post-Deploy — Configure SQL managed identity and apply EF migrations if applicablePost-Deployment
7Handle Errors — See recipe's errors.md—
8Verify Success — Confirm deployment completed and endpoints are accessibleVerification
9Live Role Verification — Query Azure to confirm provisioned RBAC roles are correct and sufficientlive-role-verification.md
10Report Results — Present deployed endpoint URLs to the user as fully-qualified https:// linksVerification

⛔ 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

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