jonathan-vella 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_bestpracticesandmcp_azure-mcp_documentationMCP tools - Use the latest supported runtime for the target service
- Destructive actions require
ask_user— global-rules
Migration Scenarios
The scenarios documented today are listed below. For other source platforms
(GCP, on-premises, etc.), call mcp_azure-mcp_documentation with
command: "microsoft_docs_search" to research the target Azure service and
adapt the AWS-Lambda assessment workflow as a template.
| 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.
Reference Index
Load these on demand — do NOT read all at once:
| Reference | When to Load |
|---|---|
references/workflow-details.md |
Workflow Details |