30-SECOND BRIEF
What it does—and when it fits
Azure Prepare plans and generates azd-based Azure deployment assets, including azure.yaml, Bicep or Terraform infrastructure, and Dockerfiles. Its first required artifact is .azure/deployment-plan.md; it researches the application, routes specialized technologies, records decisions progressively, and obtains approval before generating infrastructure for later validation and deployment.
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-prepare/~/.claude/skills/azure-prepare/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-prepare --agent claude-codeClaude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Create the deployment plan
Analyze the application, Azure context, dependencies, services, and recipe in a persistent source-of-truth plan.
Generate azd infrastructure
Prepare azure.yaml plus selected Bicep or Terraform and container assets after approval.
Hand off safely
Route specialized work first, then pass the approved assets to Azure Validate before any deployment.
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 is specifically for azd workflows or projects that already contain azure.yaml, not every Azure deployment method.
- Preparation stops before deployment execution; Azure Validate and Azure Deploy remain separate mandatory stages.
BEST FIT
Who it is for
Developers preparing applications for Azure with azd
Teams standardizing infrastructure-as-code plans
BEFORE YOU USE IT
Risks to review before use
Incorrect generated infrastructure
A wrong service, region, identity, networking choice, or template conversion can create security and cost consequences later. Review and approve the persistent plan and generated diff before validation.
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.