# Deploy Prepared Applications to Azure

Azure deployments can fail when prerequisites, identities, or environment settings are incomplete. This skill executes validated deployments with checks, recovery guidance, and verification.

## Install

```bash
npx skillstore add microsoft/azure-deploy
```

## Metadata

- Status: approved
- Slug: microsoft-azure-deploy
- Version: 0.0.0-placeholder
- Author version: 0.0.0-placeholder
- Skillstore revision: r2
- Version status: valid
- Tree hash: b70b80d44814300b9bf8f5ca762033ac622504e687ea32579e33cdcb7fe2f776
- Author: microsoft
- GitHub username: microsoft
- License: MIT
- Repository: https://github.com/microsoft/github-copilot-for-azure/tree/main/plugin/skills/azure-deploy/
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: blocked
- Manual install advisory: allowed\_with\_warning
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, env\_access, filesystem, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/microsoft-azure-deploy
- Manifest: https://skillstore.pages.dev/api/skills/microsoft-azure-deploy/manifest

## Capabilities

- Checks for a validated deployment plan before executing cloud changes.
- Runs prepared deployments through AZD, Bicep, Terraform, or Azure CLI recipes.
- Confirms Azure subscription, region, resource-group conflicts, and required environment values.
- Handles common Container Apps, registry, Terraform, Functions, and SQL deployment failures.
- Verifies resources, managed-identity roles, application health, and deployed endpoint URLs.

## Use Cases

- Release a validated application: Execute a prepared AZD deployment and report verified service endpoints.
- Operate controlled infrastructure changes: Apply a reviewed Bicep or Terraform plan after confirming subscription and region.
- Build an approved deployment pipeline: Adapt the CI/CD recipes with identity, environment, and approval controls.

## Prompt Templates

### Deploy a validated application

```
Deploy this prepared application to Azure staging. Confirm the subscription and region, complete the checklist, run the matching recipe, and report endpoint URLs.
```

### Recover a failed AZD deployment

```
Review the failed AZD deployment output. Identify the documented failure pattern, apply the safest recovery, rerun verification, and summarize every change.
```

### Run a two-phase Container Apps release

```
Deploy this validated Container Apps project in two phases. Verify AcrPull propagation before pushing the image, then confirm the active revision and endpoint.
```

### Execute a production Terraform release

```
Apply the reviewed Terraform plan to production. Confirm approvals, inspect planned changes, verify role scope, test endpoints, and produce an operational deployment summary.
```

## Limitations

- It does not create applications or generate infrastructure for unprepared projects.
- It requires authenticated Azure tooling and sufficient permissions in the selected subscription.
- It can provision billable resources and modify cloud infrastructure, database roles, and schemas.
- Some recovery and migration examples require security hardening before production use.

## Best Practices

- Run preparation and validation before this skill, then verify the recorded proof.
- Confirm the Azure subscription, region, costs, and destructive changes with the user.
- Use managed identity, narrow role scopes, reviewed plans, and production database backups.

## Anti Patterns

- Do not deploy a new or unvalidated project through this execution skill.
- Do not use plaintext registry passwords, shell eval, or unverified remote installers.
- Do not auto-approve production changes without reviewed plans and required approval gates.

## Security Audit

- Audited at: 2026-07-23T18:27:00.816\+00:00
- Summary: Most findings are false positives from Markdown formatting, relative links, project .azure paths, read-only Azure queries, and documented environment identifiers. Confirmed risks include unsafe shell evaluation, command-line registry password exposure, and a remote installer piped to Bash. Additional concerns include mutable dependencies, broad SQL schema privileges, and unvalidated health-check targets.

## Stats

- Views: 372
- Downloads: 11
- Favorites: 0
- Popularity score: 0