azure-cloud-migrate
npx machina-cli add skill microsoft/GitHub-Copilot-for-Azure/azure-cloud-migrate --openclawAzure 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_bestpracticesandmcp_azure_mcp_documentationMCP tools - Use the latest supported runtime for the target service
- Destructive actions require
ask_user— global-rules
Migration Scenarios
| Source | Target | Reference |
|---|---|---|
| AWS Lambda | Azure Functions | lambda-to-functions.md |
No matching scenario? Use
mcp_azure_mcp_documentationandmcp_azure_mcp_get_bestpracticestools.
Output Directory
All output goes to <source-folder>-azure/ at workspace root. Never modify the source directory.
Steps
- Create
<source-folder>-azure/at workspace root - Assess — Analyze source, map services, generate report → assessment.md
- Migrate — Convert code using target programming model → code-migration.md
- 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.
Source
git clone https://github.com/microsoft/GitHub-Copilot-for-Azure/blob/main/plugin/skills/azure-cloud-migrate/SKILL.mdView on GitHub Overview
Azure Cloud Migrate automates assessment and code conversion when moving workloads from AWS, GCP, or other clouds to Azure. It generates an assessment report and translates source code to Azure services, following a defined migration workflow.
How This Skill Works
The process runs in phases: assess the source workloads, then migrate code to the Azure target model. It loads the migration scenario reference and uses MCP tools (mcp_azure_mcp_get_bestpractices, mcp_azure_mcp_documentation) to guide the conversion, outputting results to <source-folder>-azure/ and tracking progress in migration-status.md. Destructive actions require user confirmation per global rules.
When to Use It
- migrate Lambda to Azure Functions
- migrate AWS to Azure
- Lambda migration assessment
- convert AWS serverless to Azure
- cross-cloud migration
Quick Start
- Step 1: Create <source-folder>-azure/ at workspace root
- Step 2: Run Assess to generate assessment.md and map services
- Step 3: Migrate code to Azure target model and review migration-status.md
Best Practices
- Follow the migration phases sequentially (assess, then migrate)
- Generate an assessment report before any code migration
- Load the scenario reference and follow its rules
- Use mcp_azure_mcp_get_bestpractices and mcp_azure_mcp_documentation MCP tools
- Use the latest supported runtime for the target service
Example Use Cases
- Migrate AWS Lambda-based API to Azure Functions with an upfront assessment
- Assess a GCP-based data pipeline for Azure migration and convert code
- Convert AWS serverless workloads to Azure Functions while mapping services
- Prepare an Azure migration readiness report for cross-cloud workloads
- Execute a full AWS-to-Azure cross-cloud migration with code migration