Skip to content
alyn
Microsoft Official

Azure Cloud Migrate skill

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 App

$npx skills add microsoft/azure-skills --skill azure-cloud-migrate
View this skill on GitHubmicrosoft/azure-skills/skills/azure-cloud-migrate/SKILL.md
Pack stars
1,636
Pack installs
17M
Alyn Score
75/99
Updated
7 h ago
License
MIT
– views – installs via Alyn

Install Azure Cloud Migrate

Pick your agent. Every command is ready to paste.

$npx skills add microsoft/azure-skills --skill azure-cloud-migrate

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads azure-cloud-migrate when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the azure-cloud-migrate skill”. In Codex, type $azure-cloud-migrate.

The skill itself

SKILL.md

FolderGitHub

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
  4. Use mcp_azure_mcp_get_azure_bestpractices and mcp_azure_mcp_documentation MCP tools
  5. Use the latest supported runtime for the target service
  6. Destructive actions require ask_user — functions global-rules | app-service global-rules
  7. 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
  8. 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

  1. Create <workspace-root-basename>-azure/ at workspace root
  2. Assess — Analyze source, map services, generate report using the scenario-specific assessment guide → functions assessment | app-service assessment
  3. Migrate — Convert code/config using the scenario-specific migration guide → functions code-migration | app-service code-migration
  4. Ask User — "Migration complete. Test locally or deploy to Azure?"
  5. Hand off to azure-prepare for infrastructure, testing, and deployment

Track progress in migration-status.md — see workflow-details.md.

Tips for Azure Cloud Migrate

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • It bundles reference files. The agent reads them only when needed, so they cost no context until then.
  • • It is part of a pack with 30 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Azure Cloud Migrate

What does the Azure Cloud Migrate skill do?

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 App

How do I install Azure Cloud Migrate?

Run "npx skills add microsoft/azure-skills --skill azure-cloud-migrate" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Azure Cloud Migrate work in Cursor and Codex?

Yes. Azure Cloud Migrate uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Azure Cloud Migrate free?

Azure Cloud Migrate is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.

Who made Azure Cloud Migrate?

Azure Cloud Migrate is published by Microsoft in the microsoft/azure-skills repository, together with 29 other skills.

Similar skills. From other creators.