Azure Cloud Migrate

microsoft/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. 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.

45k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

6 d ago

last touched

this folder, not the whole repository

Install

one command, takes just this skill from the repository

npx skills add https://github.com/microsoft/skills --skill azure-cloud-migrate

What comes with it

177 518 bytes besides the instruction

references/services/app-service/app-engine-to-app-service.md

references/services/app-service/assessment.md

references/services/app-service/beanstalk-to-app-service.md

references/services/app-service/code-migration.md

references/services/app-service/global-rules.md

references/services/app-service/heroku-to-app-service.md

references/services/container-apps/assessment-guide.md

references/services/container-apps/cloudrun-assessment-guide.md

references/services/container-apps/cloudrun-deployment-guide.md

references/services/container-apps/cloudrun-to-container-apps.md

references/services/container-apps/deployment-guide.md

references/services/container-apps/fargate-assessment-guide.md

references/services/container-apps/fargate-deployment-guide.md

references/services/container-apps/fargate-to-container-apps.md

references/services/container-apps/k8s-to-container-apps.md

references/services/container-apps/spring-apps-to-aca.md

references/services/container-apps/spring-assessment-guide.md

references/services/container-apps/spring-dependency-patterns.md

references/services/container-apps/spring-deployment-guide.md

references/services/functions/assessment.md

references/services/functions/code-migration.md

references/services/functions/global-rules.md

references/services/functions/lambda-to-functions.md

references/services/functions/runtimes/csharp.md

references/services/functions/runtimes/java.md

references/services/functions/runtimes/javascript.md

references/services/functions/runtimes/powershell.md

references/services/functions/runtimes/python.md

references/services/functions/runtimes/typescript.md

references/workflow-details.md

The instruction itself

5 sections, as written by the author

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_bestpractices and mcp_azure_mcp_documentation MCP 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_documentation and mcp_azure_mcp_get_azure_bestpractices tools.

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.

Repackaged in 1 other repositories

same content, different owner

microsoft/azure-skills open on GitHub →

How to use it

Copy the folder

Take microsoft/azure-cloud-migrate from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.