azure-cloud-migrate
🎯SkillThis skill helps you move apps from AWS, Google Cloud, Heroku, or Kubernetes to Azure. It checks your project and writes a report first, then converts the code into a separate folder.
Installation
npx skills add microsoft/azure-skills --skill azure-cloud-migrateRun it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).
Uses skills.sh · Node.js 22.20+
After installing
Ask for related work and the agent uses it on its own, or call it yourself.
/azure-cloud-migrateInstall by hand
Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.
Open the skill folder →- This project
.claude/skills/azure-cloud-migrate/ - All projects
~/.claude/skills/azure-cloud-migrate/
These paths are for Claude Code. For other tools, the command above puts it in the right place.
What this skill does
Overview
azure-cloud-migrate is a Microsoft skill that moves existing cloud apps to Azure in fixed phases. It first writes an assessment, a report on how your current services map to Azure services, and only then converts your code and settings. All output goes to a new <workspace-root-basename>-azure/ folder, so your original project stays untouched.
Key Features
- Move AWS Lambda apps to Azure Functions, and Elastic Beanstalk, Heroku, or Google App Engine apps to Azure App Service.
- Move AWS Fargate, Kubernetes, GCP Cloud Run, or Spring Boot apps to Azure Container Apps.
- Find server addresses written directly in your code that will not work in Container Apps, so you can move them into environment variables, which are settings the app reads when it starts.
- Track progress in
migration-status.md, and approve any action that deletes or overwrites things before it runs. - Choose to test locally or deploy when the code is ready, with infrastructure and deployment handed to the azure-prepare skill.
Who is this for?
It is for teams that run apps on AWS, Google Cloud, Heroku, or Kubernetes and plan to move them to Azure. It helps when you want a clear report and converted code before you change anything in the original project.
Summarized by AI from this skill's SKILL.md. Suggest a better one
SKILL.md
View on GitHub →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.
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.
More from this repository10
Helps you build, deploy, test, and manage AI agents and models on Microsoft Foundry, Microsoft's Azure service for AI. It guides the AI through each task with fixed steps.
Helps you find and fix problems in apps running on Azure, such as crashes, slow responses, or connection failures. It checks things in a set order and can work only from logs you provide.
azure-prepare gets a new or existing app ready to deploy to Azure with azd, Microsoft's command-line tool for Azure. It first writes a plan for your approval, then creates the setup files.
azure-deploy puts your app on Azure after the azure-prepare and azure-validate skills have prepared and checked it. It runs the deployment, recovers from errors, and gives you the live web addresses.
azure-validate checks your Azure app before you deploy it, so you can catch setup and permission problems early. It runs after azure-prepare and before azure-deploy.
azure-resource-lookup finds and lists your Azure resources, such as web apps, virtual machines, and storage accounts, across your subscriptions. It only reads data and never changes anything.
azure-resource-visualizer draws a diagram of an Azure resource group that shows how each resource connects to the others. It saves the diagram and notes in a markdown file.
Lets Claude search and summarize large amounts of logs and app data stored in Azure Data Explorer. You ask what you want to know, and it writes and runs the queries for you.
Helps you send all requests to your AI models and tools through Azure API Management, so you can control cost, block harmful content and limit traffic. It includes Azure command-line steps for setup and testing.
Helps you find and fix errors in apps that send and receive messages through Azure Event Hubs or Service Bus. It checks service health and Microsoft docs to suggest a fix.