
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.
$ npx -y skills add microsoft/azure-skills --skill azure-cloud-migrate --agent claude-codeInstalls into .claude/skills of the current project.
This skill handles assessment and code migration of existing cloud workloads to Azure.
mcp_azure_mcp_get_azure_bestpractices and mcp_azure_mcp_documentation MCP toolsask_user — functions global-rules | app-service global-ruleshttp://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 injectionSponsors