OpenSkillIndex← back to search
claude-code

Skills azure-cloud-migrate

Assess and migrate cross-cloud workloads to Azure with migration reports and code conversion. Supports AWS Lambda→Functions and GCP Cloud Run→Container Apps. WHEN: migrate Lambda to Azure Functions, migrate AWS to Azure, Lambda migration assessment, convert serverless to Azure, migration readiness report, migrate from AWS, migrate from GCP, Cloud Run to Container Apps, Cloud Run migration assessment.

install
source · Clone the upstream repo
git clone https://github.com/microsoft/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/microsoft/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.github/plugins/azure-skills/skills/azure-cloud-migrate" ~/.claude/skills/microsoft-skills-azure-cloud-migrate && rm -rf "$T"
manifest: .github/plugins/azure-skills/skills/azure-cloud-migrate/SKILL.md
source content

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_azure_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

Migration Scenarios

SourceTargetReference
AWS LambdaAzure Functionslambda-to-functions.md (assessment, code-migration)
GCP Cloud RunAzure Container Appscloudrun-to-container-apps.md

No matching scenario? Use 

mcp_azure_mcp_documentation
and 
mcp_azure_mcp_get_azure_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 using scenario-specific assessment guide
  3. Migrate — Convert code/config using scenario-specific migration guide
  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.