Back to catalog / Integrations
Cross-cloud migration to Azure: assess before scenario-specific conversion
Select a Lambda, Fargate/Kubernetes, Cloud Run, or App Service migration scenario.
Skills
Confirm source technology, target service, and whether assessment only is requested. Follow the matching scenario reference in phases: inventory dependencies/config and service-discovery URLs, then write an assessment. Put all output in a new `<workspace>-azure/` directory at workspace root and never modify the source tree. Flag hard-coded service hosts/ports for env-based URLs. After approval, convert code/config and update migration status; hand infrastructure and validation to azure-prepare. Destructive actions need user approval; do not deploy unless requested.
Permissions
Prerequisites
- Assess and migrate workloads from Lambda, ECS/Kubernetes, Cloud Run, Heroku, or Spring to Azure.
Permissions
- Reads source and writes assessment/conversion files to a new directory; infrastructure may follow.
Limitations
Assessment precedes migration; never change source dir; destructive work needs user approval.
Pinned upstream source
- Repository
- microsoft/skills
- File path
- .github/plugins/azure-skills/skills/azure-cloud-migrate/SKILL.md
- Pinned commit
fc164ba1d7a0c10377dbcc1c9ac07253b9329fdb- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Azure MCP documentation/best-practices · source scenario references · Azure codebase analysis
Main topic
Turn ecommerce campaign materials into a reviewable weekly brief