azure-cloud-migrate

Name: azure-cloud-migrate
Author: microsoft

Official

github.com/microsoftCloud & DevOps1.6k517.7k installsUpdated today

Repository

About azure-cloud-migrate

Azure Cloud Migrate is a skill for assessing and migrating existing cloud workloads to Azure. It runs phases in sequence and writes all output to a separate directory, leaving the source directory unmodified.

Key features

01Analyzes source code and maps services in phases
02Generates a migration assessment report
03Converts code and configuration for Azure targets
04Tracks migration progress in migration-status.md

Use cases

01Migrating AWS Lambda functions to Azure Functions
02Moving Heroku apps to Azure App Service
03Moving Kubernetes workloads to Azure Container Apps

MCP support

The skill directs use of Azure MCP tools such as mcp_azure_mcp_get_azure_bestpractices and mcp_azure_mcp_documentation for best practices and documentation.

Install

Copy the command and run it in a terminal.

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

After installing, type/azure-cloud-migratein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/

workflow-details.md

references/services/app-service/

app-engine-to-app-service.md

assessment.md

beanstalk-to-app-service.md

code-migration.md

global-rules.md

heroku-to-app-service.md

references/services/container-apps/

assessment-guide.md

cloudrun-assessment-guide.md

cloudrun-deployment-guide.md

cloudrun-to-container-apps.md

deployment-guide.md

fargate-assessment-guide.md

fargate-deployment-guide.md

fargate-to-container-apps.md

k8s-to-container-apps.md

spring-apps-to-aca.md

spring-assessment-guide.md

spring-dependency-patterns.md

spring-deployment-guide.md

references/services/functions/

assessment.md

code-migration.md

global-rules.md

lambda-to-functions.md

references/services/functions/runtimes/

csharp.md

java.md

javascript.md

powershell.md

python.md

typescript.md

Details

From the project README

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.

Comments

Markdown supported

Details

Author: microsoft
Repository: microsoft/azure-skills
Category: Cloud & DevOps
Installs: 517,657
GitHub stars: 1,603
First seen: Feb 28, 2026

Report

More skills

All skills

lark-apps

open.feishu.cn

732.0k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

571.7k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

wizard

github.com/mattpocock

571.5k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-ai

github.com/microsoft

571.2k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.