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/bicep/README.md

Bicep Deploy Recipe

Deploy to Azure using Bicep templates directly.

Prerequisites

  • az CLI installed with Bicep extension
  • .azure/deployment-plan.md exists with status Validated
  • Bicep templates exist in infra/
  • Subscription and location confirmed → See Pre-Deploy Checklist

Workflow

| Step | Task | Command | |------|------|---------| | 1 | Pre-deploy checklist | Confirm subscription/location with user | | 2 | Build (optional) | az bicep build --file main.bicep | | 3 | Deploy | az deployment sub create | | 4 | Verify | az resource list | | 5 | Report | Present deployed endpoint URLs to the user — see Verification |

Deployment Commands

Subscription-Level Deployment

az deployment sub create \
  --location eastus2 \
  --template-file ./infra/main.bicep \
  --parameters ./infra/main.parameters.json

Resource Group Deployment

az deployment group create \
  --resource-group rg-myapp-dev \
  --template-file ./infra/main.bicep \
  --parameters ./infra/main.parameters.json

With Inline Parameters

az deployment sub create \
  --location eastus2 \
  --template-file ./infra/main.bicep \
  --parameters environmentName=dev location=eastus2

What-If (Preview Changes)

az deployment sub what-if \
  --location eastus2 \
  --template-file ./infra/main.bicep \
  --parameters environmentName=dev

Get Deployment Outputs

az deployment sub show \
  --name main \
  --query properties.outputs

References

MCP Tools

| Tool | Purpose | |------|---------| | mcp_bicep_get_bicep_best_practices | Best practices | | mcp_bicep_get_az_resource_type_schema | Resource schemas | | mcp_bicep_list_avm_metadata | Azure Verified Modules |

AVM Verification Before Deploy

Before running deployment commands, verify generated templates followed AVM-first module selection:

  1. AVM Bicep Pattern Modules (prefer AVM+AZD patterns)
  2. AVM Bicep Resource Modules
  3. AVM Bicep Utility Modules

If no AVM+AZD pattern module is available, fallback must remain within AVM modules (resource -> utility).

Cleanup (DESTRUCTIVE)

az group delete --name <rg-name> --yes

⚠️ Permanently deletes ALL resources in the group.