AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-deploy

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.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-deploy at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 33

references/recipes/azd/README.md

AZD Deploy Recipe

Deploy to Azure using Azure Developer CLI (azd).

💡 Note: azd supports both Bicep and Terraform as IaC providers. The deployment workflow is identical regardless of which you use.

Prerequisites

  • azd CLI installed → Run mcp_azure_mcp_extension_cli_install with cli-type: azd if needed
  • .azure/deployment-plan.md exists with status Validated
  • azure.yaml exists and validated
  • Infrastructure files exist (Bicep: infra/main.bicep, Terraform: infra/*.tf)
  • AZD environment configured → Done in azure-validate
  • Subscription and location confirmed → See Pre-deploy Checklist

Workflow

| Step | Task | Command | |------|------|---------| | 1 | Verify environment | azd env get-values — Confirm AZURE_SUBSCRIPTION_ID and AZURE_LOCATION set | | 2 | Provision infrastructure | azd provision --no-prompt | | 3 | RBAC health check (Container Apps + ACR only) | After provisioning, verify AcrPull role has propagated before deploying — see Pre-Deploy Checklist | | 4 | Deploy application | azd deploy --no-prompt | | 5 | Post-Deploy | Post-Deployment Steps — If using SQL + managed identity | | 6 | Verify | See Verification | | 7 | Report | Present deployed endpoint URLs to the user — see Verification Step 3 |

⚠️ Important: For Container Apps that use a managed identity to pull from ACR, always run azd provision and azd deploy as separate steps (not azd up) and complete the RBAC health check between them. This ensures the managed identity AcrPull role assignment has propagated before the Container App revision attempts to pull the image.

⚠️ Important: For .NET Aspire projects or projects using azd "limited mode" (no explicit infra/ folder), verify that azd provision populated all required environment variables. If azd deploy fails with errors about missing AZURE_CONTAINER_REGISTRY_ENDPOINT, AZURE_CONTAINER_REGISTRY_MANAGED_IDENTITY_ID, or MANAGED_IDENTITY_CLIENT_ID, see Error Handling for the resolution.

Common Mistakes

| ❌ Wrong | Why It Fails | |----------|-------------| | azd up --location eastus2 | --location is not a valid flag for azd up | | azd up without azd env new | Prompts for input, fails with --no-prompt | | mkdir .azure then azd env new --no-prompt | Creates env folder structure incorrectly | | Setting AZURE_LOCATION without checking RG | "Invalid resource group location" if RG exists elsewhere | | Ignoring azd-service-name tag conflicts in same RG | "found '2' resources tagged with..." error | | language: html or language: static | Not valid - use language: js with dist: . for static sites |

Deployment Commands

⚠️ azd up takes 5-15 min. Run with output streamed visibly to the user — do NOT run silently or suppress output. The user must see provisioning progress in real time.

Full Deployment

Provisions infrastructure AND deploys application:

azd up --no-prompt

Infrastructure Only

azd provision --no-prompt

Application Only

Deploy code to existing infrastructure:

azd deploy --no-prompt

Single Service

azd deploy api --no-prompt

References