GitHub Copilot ChatGPT Claude Codex CLI Cursor opencode Skill Text

azure-cloud-migrate

Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, mig

Ciza · 0 points · 25 views 0 listing impressions 0 install-command copies
Download microsoft-skills-.github_plugins_azure-skills_skills_azure-cloud-migrate-b35d2c6.zip · 68 KB

Install

skills CLI npx skills add https://github.com/microsoft/skills/tree/main/.github/plugins/azure-skills/skills/azure-cloud-migrate
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install microsoft-skills@llmmart
Git git clone https://github.com/microsoft/skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole microsoft/skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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 — functions global-rules | app-service global-rules
  7. 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
  8. 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

Source Target Reference
AWS Lambda Azure Functions lambda-to-functions.md (assessment, code-migration)
AWS Elastic Beanstalk Azure App Service beanstalk-to-app-service.md
Heroku Azure App Service heroku-to-app-service.md
Google App Engine Azure App Service app-engine-to-app-service.md
AWS Fargate (ECS) Azure Container Apps fargate-to-container-apps.md (assessment, deployment)
Kubernetes (GKE/EKS/Self-hosted) Azure Container Apps k8s-to-container-apps.md
GCP Cloud Run Azure Container Apps cloudrun-to-container-apps.md
Spring Boot (Azure Spring Apps/VMs) Azure Container Apps spring-apps-to-aca.md

No matching scenario? Use mcp_azure_mcp_documentation and mcp_azure_mcp_get_azure_bestpractices tools.

Output Directory

All output goes to <workspace-root-basename>-azure/ at workspace root, where <workspace-root-basename> is the name of the top-level workspace directory itself (NOT a subdirectory within it). Never modify the source directory.

Steps

  1. Create <workspace-root-basename>-azure/ at workspace root
  2. Assess — Analyze source, map services, generate report using the scenario-specific assessment guide → functions assessment | app-service assessment
  3. Migrate — Convert code/config using the scenario-specific migration guide → functions code-migration | app-service code-migration
  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.

Files (skills)
  • references
    • services
      • app-service
        • app-engine-to-app-service.md 7.1 KB
          Loading…
        • assessment.md 5.2 KB
          Loading…
        • beanstalk-to-app-service.md 6.4 KB
          Loading…
        • code-migration.md 5.2 KB
          Loading…
        • global-rules.md 2.8 KB
          Loading…
        • heroku-to-app-service.md 7.5 KB
          Loading…
      • container-apps
        • assessment-guide.md 7 KB
          Loading…
        • cloudrun-assessment-guide.md 2.5 KB
          Loading…
        • cloudrun-deployment-guide.md 7.9 KB
          Loading…
        • cloudrun-to-container-apps.md 2.2 KB
          Loading…
        • deployment-guide.md 9.6 KB
          Loading…
        • fargate-assessment-guide.md 2.4 KB
          Loading…
        • fargate-deployment-guide.md 10.1 KB
          Loading…
        • fargate-to-container-apps.md 4 KB
          Loading…
        • k8s-to-container-apps.md 4.9 KB
          Loading…
        • spring-apps-to-aca.md 3.8 KB
          Loading…
        • spring-assessment-guide.md 5.2 KB
          Loading…
        • spring-dependency-patterns.md 1.2 KB
          Loading…
        • spring-deployment-guide.md 15.1 KB
          Loading…
      • functions
        • runtimes
          • csharp.md 5.5 KB
            Loading…
          • java.md 6.4 KB
            Loading…
          • javascript.md 8.5 KB
            Loading…
          • powershell.md 5 KB
            Loading…
          • python.md 6.4 KB
            Loading…
          • typescript.md 3.5 KB
            Loading…
        • assessment.md 6.3 KB
          Loading…
        • code-migration.md 6 KB
          Loading…
        • global-rules.md 3.3 KB
          Loading…
        • lambda-to-functions.md 10.2 KB
          Loading…
    • workflow-details.md 2.3 KB
      Loading…
  • SKILL.md 4.3 KB
    ---
    name: azure-cloud-migrate
    description: "Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration."
    license: MIT
    metadata:
      author: Microsoft
      version: "1.3.3"
    ---
    
    # 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` — [functions global-rules](references/services/functions/global-rules.md) | [app-service global-rules](references/services/app-service/global-rules.md)
    7. **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](references/workflow-details.md)
    8. **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
    
    | Source | Target | Reference |
    |--------|--------|-----------|
    | AWS Lambda | Azure Functions | [lambda-to-functions.md](references/services/functions/lambda-to-functions.md) ([assessment](references/services/functions/assessment.md), [code-migration](references/services/functions/code-migration.md)) |
    | AWS Elastic Beanstalk | Azure App Service | [beanstalk-to-app-service.md](references/services/app-service/beanstalk-to-app-service.md) |
    | Heroku | Azure App Service | [heroku-to-app-service.md](references/services/app-service/heroku-to-app-service.md) |
    | Google App Engine | Azure App Service | [app-engine-to-app-service.md](references/services/app-service/app-engine-to-app-service.md) |
    | AWS Fargate (ECS) | Azure Container Apps | [fargate-to-container-apps.md](references/services/container-apps/fargate-to-container-apps.md) ([assessment](references/services/container-apps/fargate-assessment-guide.md), [deployment](references/services/container-apps/fargate-deployment-guide.md)) |
    | Kubernetes (GKE/EKS/Self-hosted) | Azure Container Apps | [k8s-to-container-apps.md](references/services/container-apps/k8s-to-container-apps.md) |
    | GCP Cloud Run | Azure Container Apps | [cloudrun-to-container-apps.md](references/services/container-apps/cloudrun-to-container-apps.md) |
    | Spring Boot (Azure Spring Apps/VMs) | Azure Container Apps | [spring-apps-to-aca.md](references/services/container-apps/spring-apps-to-aca.md) |
    
    > No matching scenario? Use `mcp_azure_mcp_documentation` and `mcp_azure_mcp_get_azure_bestpractices` tools.
    
    ## Output Directory
    
    All output goes to `<workspace-root-basename>-azure/` at workspace root, where `<workspace-root-basename>` is the name of the top-level workspace directory itself (NOT a subdirectory within it). Never modify the source directory.
    
    ## Steps
    
    1. **Create** `<workspace-root-basename>-azure/` at workspace root
    2. **Assess** — Analyze source, map services, generate report using the scenario-specific assessment guide → [functions assessment](references/services/functions/assessment.md) | [app-service assessment](references/services/app-service/assessment.md)
    3. **Migrate** — Convert code/config using the scenario-specific migration guide → [functions code-migration](references/services/functions/code-migration.md) | [app-service code-migration](references/services/app-service/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).
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.