azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with migration reports and code conversion guidance. Supports AWS, GCP, and other providers. WHEN: migrate Lambda to Azure Functions, migrate AWS to Azure, Lambda migration assessment, convert AWS serverless to Azure, migration readiness report, migrate from AWS, migrate from GCP, cross-cloud migration.
Source facts
- Repository
- LongLeo287/OmniClaw
- Last source activity
- April 11, 2026 at 23:12
- Detected SKILL.md language
- English
- Stars
- 7
- Forks
- 0
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
File Explorer
4 filesShowing SKILL.md
SKILL.md
Source instructions ยท Read-only preview- name
- azure_cloud_migrate
- description
- Assess and migrate cross-cloud workloads to Azure with migration reports and code conversion guidance. Supports AWS, GCP, and other providers. WHEN: migrate Lambda to Azure Functions, migrate AWS to Azure, Lambda migration assessment, convert AWS serverless to Azure, migration readiness report, migrate from AWS, migrate from GCP, cross-cloud migration.
- license
- MIT
- metadata
- {"author":"Microsoft","version":"1.0.1"}
# Azure Cloud Migrate
> This skill handles **assessment and code migration** of existing cloud workloads to Azure.
## Rules
1. Follow phases sequentially โ do not skip
2. Generate assessment before any code migration
3. Load the scenario reference and follow its rules
4. Use `mcp_azure_mcp_get_bestpractices` and `mcp_azure_mcp_documentation` MCP tools
5. Use the latest supported runtime for the target service
6. Destructive actions require `ask_user` โ [global-rules](references/services/functions/global-rules.md)
## Migration Scenarios
| Source | Target | Reference |
|--------|--------|-----------|
| AWS Lambda | Azure Functions | [lambda-to-functions.md](references/services/functions/lambda-to-functions.md) |
> No matching scenario? Use `mcp_azure_mcp_documentation` and `mcp_azure_mcp_get_bestpractices` tools.
## Output Directory
All output goes to `<source-folder>-azure/` at workspace root. Never modify the source directory.
## Steps
1. **Create** `<source-folder>-azure/` at workspace root
2. **Assess** โ Analyze source, map services, generate report โ [assessment.md](references/services/functions/assessment.md)
3. **Migrate** โ Convert code using target programming model โ [code-migration.md](references/services/functions/code-migration.md)
4. **Ask User** โ "Migration complete. Test locally or deploy to Azure?"
5. **Hand off** to azure-prepare for infrastructure, testing, and deployment
Track progress in `migration-status.md` โ see [workflow-details.md](references/workflow-details.md).
View on GitHub