azure-cloud-migrate

Assess and migrate cloud workloads from AWS, GCP, and other providers to Azure services.

- Supports Lambda-to-Azure Functions migration with dedicated scenario reference and best practices

- Generates assessment reports mapping source services to Azure equivalents before any code conversion

- Converts source code to target Azure runtime models, with output isolated in a separate <source-folder>-azure/ directory

- Requires sequential phase execution: assessment first, then migration, with user confirmation before destructive actions

- Hands off to azure-prepare skill for infrastructure provisioning, local testing, and deployment workflows

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