Workload Migration Tool
Azure cloud migrate

Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps.
--- name: azure-cloud-migrate description: "Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration." license: MIT metadata: author: Microsoft version: "1.3.2" --- # Azure Cloud Migrate > This skill handles **assessment and code migration** of existing cloud workloads to Azure. ## Rules 1. Follow phases sequentially — do not skip 2. Generate assessment before any code migration 3. Load the scenario reference and follow its rules
Overview
All output goes to <workspace-root-basename>-azure/ at workspace root, where <workspace-root-basename> is the name of the top-level workspace directory itself (NOT a subdirectory within it). Never modify the source directory.
Manual install (npx, ZIP)
npx skills add microsoft/azure-skills --skill azure-cloud-migrate -g -a claude-codenpx degit microsoft/azure-skills/skills/azure-cloud-migrate#main ~/.claude/skills/azure-cloud-migrateConnects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md4.3 KB
Read SKILL.md here
Show the full text53 lines
Azure Cloud Migrate
This skill handles assessment and code migration of existing cloud workloads to Azure.
Rules
- Follow phases sequentially — do not skip
- Generate assessment before any code migration
- Load the scenario reference and follow its rules
- Use
mcp_azure_mcp_get_azure_bestpracticesandmcp_azure_mcp_documentationMCP tools - Use the latest supported runtime for the target service
- Destructive actions require
ask_user— functions global-rules | app-service global-rules - Report progress to user — During long-running operations (deployments, image pushes), provide resource-level status updates so the user is never left waiting without feedback — see workflow-details.md
- Audit service discovery in app code — Kubernetes DNS names (e.g.,
http://order-service:3001) do not resolve in Container Apps. During assessment, scan source code for hardcoded hostnames/ports in HTTP clients and flag them for env-var-driven URL injection
Migration Scenarios
| Source | Target | Reference |
|---|---|---|
| AWS Lambda | Azure Functions | lambda-to-functions.md (assessment, code-migration) |
| AWS Elastic Beanstalk | Azure App Service | beanstalk-to-app-service.md |
| Heroku | Azure App Service | heroku-to-app-service.md |
| Google App Engine | Azure App Service | app-engine-to-app-service.md |
| AWS Fargate (ECS) | Azure Container Apps | fargate-to-container-apps.md (assessment, deployment) |
| Kubernetes (GKE/EKS/Self-hosted) | Azure Container Apps | k8s-to-container-apps.md |
| GCP Cloud Run | Azure Container Apps | cloudrun-to-container-apps.md |
| Spring Boot (Azure Spring Apps/VMs) | Azure Container Apps | spring-apps-to-aca.md |
No matching scenario? Use
mcp_azure_mcp_documentationandmcp_azure_mcp_get_azure_bestpracticestools.
Output Directory
All output goes to <workspace-root-basename>-azure/ at workspace root, where <workspace-root-basename> is the name of the top-level workspace directory itself (NOT a subdirectory within it). Never modify the source directory.
Steps
- Create
<workspace-root-basename>-azure/at workspace root - Assess — Analyze source, map services, generate report using the scenario-specific assessment guide → functions assessment | app-service assessment
- Migrate — Convert code/config using the scenario-specific migration guide → functions code-migration | app-service code-migration
- Ask User — "Migration complete. Test locally or deploy to Azure?"
- Hand off to azure-prepare for infrastructure, testing, and deployment
Track progress in migration-status.md — see workflow-details.md.
| 1 | |
| 2 | name azure-cloud-migrate |
| 3 | description "Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration." |
| 4 | license MIT |
| 5 | metadata |
| 6 | author Microsoft |
| 7 | version "1.3.2" |
| 8 | |
| 9 | |
| 10 | # Azure Cloud Migrate |
| 11 | |
| 12 | > This skill handles **assessment and code migration** of existing cloud workloads to Azure. |
| 13 | |
| 14 | ## Rules |
| 15 | |
| 16 | Follow phases sequentially — do not skip |
| 17 | Generate assessment before any code migration |
| 18 | Load the scenario reference and follow its rules |
| 19 | Use `mcp_azure_mcp_get_azure_bestpractices` and `mcp_azure_mcp_documentation` MCP tools |
| 20 | Use the latest supported runtime for the target service |
| 21 | Destructive actions require `ask_user` — [functions global-rules] | [app-service global-rules] |
| 22 | **Report progress to user** — During long-running operations (deployments, image pushes), provide resource-level status updates so the user is never left waiting without feedback — see [workflow-details.md] |
| 23 | **Audit service discovery in app code** — Kubernetes DNS names (e.g., `http://order-service:3001`) do not resolve in Container Apps. During assessment, scan source code for hardcoded hostnames/ports in HTTP clients and flag them for env-var-driven URL injection |
| 24 | |
| 25 | ## Migration Scenarios |
| 26 | |
| 27 | | Source | Target | Reference | |
| 28 | |--------|--------|-----------| |
| 29 | | AWS Lambda | Azure Functions | [lambda-to-functions.md] ([assessment], [code-migration]) | |
| 30 | | AWS Elastic Beanstalk | Azure App Service | [beanstalk-to-app-service.md] | |
| 31 | | Heroku | Azure App Service | [heroku-to-app-service.md] | |
| 32 | | Google App Engine | Azure App Service | [app-engine-to-app-service.md] | |
| 33 | | AWS Fargate (ECS) | Azure Container Apps | [fargate-to-container-apps.md] ([assessment], [deployment]) | |
| 34 | | Kubernetes (GKE/EKS/Self-hosted) | Azure Container Apps | [k8s-to-container-apps.md] | |
| 35 | | GCP Cloud Run | Azure Container Apps | [cloudrun-to-container-apps.md] | |
| 36 | | Spring Boot (Azure Spring Apps/VMs) | Azure Container Apps | [spring-apps-to-aca.md] | |
| 37 | |
| 38 | > No matching scenario? Use `mcp_azure_mcp_documentation` and `mcp_azure_mcp_get_azure_bestpractices` tools. |
| 39 | |
| 40 | ## Output Directory |
| 41 | |
| 42 | All output goes to `<workspace-root-basename>-azure/` at workspace root, where `<workspace-root-basename>` is the name of the top-level workspace directory itself (NOT a subdirectory within it). Never modify the source directory. |
| 43 | |
| 44 | ## Steps |
| 45 | |
| 46 | **Create** `<workspace-root-basename>-azure/` at workspace root |
| 47 | **Assess** — Analyze source, map services, generate report using the scenario-specific assessment guide → [functions assessment] | [app-service assessment] |
| 48 | **Migrate** — Convert code/config using the scenario-specific migration guide → [functions code-migration] | [app-service code-migration] |
| 49 | **Ask User** — "Migration complete. Test locally or deploy to Azure?" |
| 50 | **Hand off** to azure-prepare for infrastructure, testing, and deployment |
| 51 | |
| 52 | Track progress in `migration-status.md` — see [workflow-details.md]. |
| 53 |
Details
- License
- MIT
- Stars on the repo
- ★ 1,532
- Checked
- Source
- microsoft/azure-skills ↗
- Creator
- microsoft · 31 listings
Similar skills
See all →
SkillAzure App Deployer
SkillAzure Deployment Auditor
SkillAzure AI Gateway
SkillKusto Query Builder
AgentDocker CLI Container Gateway
AgentAgent MarketplaceMore from microsoft
AgentPlaywright Browser Automation MCP
SkillUsage-Based Agent Trainer
SkillAzure App Deployer
SkillAzure Deployment Auditor
SkillAzure Security Auditor
SkillAzure AI Gateway