30-SECOND BRIEF
What it does—and when it fits
Azure Deploy executes production deployment for an application that has already completed Azure Prepare and Azure Validate. It requires an existing .azure/deployment-plan.md with real validation proof, then runs the selected azd, Bicep, Terraform, or Azure deployment recipe with preflight checks, error recovery, post-deploy verification, and live RBAC confirmation.
INSTALL BY AGENT
Choose your Agent
Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.
.claude/skills/azure-deploy/~/.claude/skills/azure-deploy/Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.
npx skills add microsoft/azure-skills --skill azure-deploy --agent claude-codeClaude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Deploy a prepared application
Execute azd up, azd deploy, Terraform apply, or Azure deployment commands for approved infrastructure.
Recover from deployment errors
Follow recipe-specific recovery guidance without bypassing the validated plan.
Verify the live result
Check endpoints, post-deployment tasks, and actual role assignments before reporting success.
THE TRADEOFFS
Advantages and tradeoffs
Notable strengths
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to microsoft/azure-skills.
- Core uses, limitations, and risks are separated for pre-install review.
Limitations
- It cannot prepare a new application or generate missing infrastructure; Azure Prepare owns that work.
- It must stop when the plan or validation proof is absent, stale, or not marked Validated by Azure Validate.
BEST FIT
Who it is for
Azure teams shipping already-prepared workloads
Operators needing guarded deployment execution
BEFORE YOU USE IT
Risks to review before use
Production and infrastructure changes
Deployment commands can create cost, change access, replace resources, or interrupt service. Verify the approved plan, subscription, environment, validation evidence, and destructive steps before execution.
Upstream instruction drift
Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.
SECURITY
What the permission profile means
- Declared access remains governed by the current upstream SKILL.md and runtime requests.
- Treat repository files, web content, and tool output as untrusted input.
- SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.
Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.
INSIDE THE PACKAGE
Indexed files
TAGS
Manually expanded from the current upstream SKILL.md and linked source at microsoft/azure-skills, checked 2026-08-20. This is an original summary, not an execution result or security certification.