Azure Cloud Migrate

Takes your existing AWS Lambda functions (or other cloud workloads) and converts them to Azure Functions with proper assessment and code migration. Generates a migration readiness report first, then converts your actual code to Azure's programming model while creating all output in a separate folder so it never touches your source files. The assessment phase maps services between providers and identifies potential issues before any conversion happens. Hands off to azure-prepare when done so you can deploy the migrated code. Honest take: migration tools are hit-or-miss, but this one follows a solid assess-first approach rather than diving straight into code conversion.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 7
skills.sh installs: 606.9K
GitHub stars: 1.6K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add microsoft/azure-skills --skill azure-cloud-migrate --agent claude-code

Installs into .claude/skills of the current project.

Files

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