30-SECOND BRIEF
What it does—and when it fits
Azure Cloud Migrate assesses and converts supported workloads from AWS, Google Cloud, Heroku, Kubernetes, or Spring environments to Azure Functions, App Service, or Container Apps. It must generate a scenario-specific assessment before code conversion, writes every result into a separate sibling Azure directory without modifying the source, and hands the migrated project to Azure Prepare.
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-cloud-migrate/~/.claude/skills/azure-cloud-migrate/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-cloud-migrate --agent claude-codeClaude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Assess a supported migration
Map source services, runtimes, configuration, dependencies, and service discovery to the target Azure platform.
Convert code and configuration
Follow the scenario guide for Lambda, App Service, Container Apps, or other supported target conversion.
Prepare the migrated project
Keep the source untouched, track migration status, then hand the new directory to Azure Prepare for testing and 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
- Only documented source-to-target scenarios have prescribed conversion workflows; unmatched migrations need fresh research.
- Automated conversion cannot guarantee behavioral parity, performance, data migration, or production readiness.
BEST FIT
Who it is for
Teams moving supported workloads from other clouds to Azure
Engineers needing assessment-first code conversion
BEFORE YOU USE IT
Risks to review before use
Behavior, data, and service-discovery regressions
Cloud services differ in identity, networking, events, storage, scaling, and runtime semantics. Preserve the source, review the assessment, test the separate output thoroughly, and migrate production data only through an approved plan.
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.