Skip to content

Robertjam954/multimodal_rag_application / .claude/skills/azure-deploy

azure-deploy

Flagged

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.

FileKindSize
SKILL.mdskill md6.5 KB
references/auth-best-practices.mdmarkdown6.1 KB
references/global-rules.mdmarkdown1.2 KB
references/live-role-verification.mdmarkdown3.9 KB
references/pre-deploy-checklist.mdmarkdown18.4 KB
references/recipes/README.mdmarkdown431 B
references/recipes/azcli/README.mdmarkdown1.7 KB
references/recipes/azcli/errors.mdmarkdown492 B
references/recipes/azcli/verify.mdmarkdown2.0 KB
references/recipes/azd/README.mdmarkdown3.7 KB
references/recipes/azd/ef-migrations.mdmarkdown5.0 KB
references/recipes/azd/errors.mdmarkdown15.4 KB
references/recipes/azd/functions-deploy.mdmarkdown3.5 KB
references/recipes/azd/post-deployment.mdmarkdown4.2 KB
references/recipes/azd/scripts/apply-migrations.ps1script1.8 KB
references/recipes/azd/scripts/apply-migrations.shscript1.8 KB
references/recipes/azd/scripts/grant-and-migrate.ps1script4.2 KB
references/recipes/azd/scripts/grant-and-migrate.shscript4.3 KB
references/recipes/azd/sql-entra-auth.mdmarkdown2.5 KB
references/recipes/azd/sql-managed-identity.mdmarkdown7.4 KB
references/recipes/azd/verify.mdmarkdown4.9 KB
references/recipes/bicep/README.mdmarkdown2.4 KB
references/recipes/bicep/errors.mdmarkdown511 B
references/recipes/bicep/verify.mdmarkdown763 B
references/recipes/cicd/README.mdmarkdown1.2 KB
references/recipes/cicd/errors.mdmarkdown542 B
references/recipes/cicd/examples/azdo-azd.ymlconfig487 B
references/recipes/cicd/examples/azdo-multistage.ymlconfig831 B
references/recipes/cicd/examples/github-azd.ymlconfig782 B
references/recipes/cicd/examples/github-bicep.ymlconfig660 B
references/recipes/cicd/verify.mdmarkdown754 B
references/recipes/terraform/README.mdmarkdown3.2 KB
references/recipes/terraform/errors.mdmarkdown858 B
references/recipes/terraform/verify.mdmarkdown752 B
references/region-availability.mdmarkdown3.0 KB
references/sdk/azd-deployment.mdmarkdown792 B
references/sdk/azure-identity-dotnet.mdmarkdown941 B
references/sdk/azure-identity-java.mdmarkdown1.2 KB
references/sdk/azure-identity-py.mdmarkdown1.1 KB
references/sdk/azure-identity-ts.mdmarkdown1.1 KB
references/troubleshooting.mdmarkdown8.0 KB

references/recipes/azd/README.md

View on GitHub
# 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](../../pre-deploy-checklist.md)

## 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](../../pre-deploy-checklist.md#container-apps--acr--pre-deploy-rbac-health-check) |
| 4 | **Deploy application** | `azd deploy --no-prompt` |
| 5 | **Post-Deploy** | [Post-Deployment Steps](post-deployment.md) — If using SQL + managed identity |
| 6 | **Verify** | See [Verification](verify.md) |
| 7 | **Report** | Present deployed endpoint URLs to the user — see [Verification](verify.md) 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](errors.md#missing-container-registry-variables) 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:

```bash
azd up --no-prompt
```

### Infrastructure Only

```bash
azd provision --no-prompt
```

### Application Only

Deploy code to existing infrastructure:

```bash
azd deploy --no-prompt
```

### Single Service

```bash
azd deploy api --no-prompt
```

## References

- [Pre-deploy Checklist](../../pre-deploy-checklist.md) — **REQUIRED**
- [Post-Deployment Steps](post-deployment.md) — SQL + managed identity setup
- [Azure Functions Deployment](functions-deploy.md)
- [Verification](verify.md)
- [Error Handling](errors.md)
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall