PluginBench
Skill
Official
Pass
Audit score 90

azure-cloud-migrate

microsoft/azure-skills

Assess and migrate cross-cloud workloads to Azure with automated code conversion and reports.

SourceView on skills.sh

What is azure-cloud-migrate?

This skill analyzes existing cloud workloads from AWS, Google Cloud, Heroku, and Kubernetes environments, then converts them to equivalent Azure services. Use it when migrating Lambda functions, containerized apps, or platform-as-a-service applications to Azure.

  • Generates detailed assessment reports mapping source services to Azure equivalents
  • Converts Lambda functions to Azure Functions with runtime adaptation
  • Migrates Elastic Beanstalk, Heroku, and App Engine apps to Azure App Service
  • Transforms Fargate, Kubernetes, Cloud Run, and Spring Boot workloads to Azure Container Apps
  • Scans code for hardcoded service discovery patterns (e.g., Kubernetes DNS) and flags migration blockers
  • Tracks migration progress and outputs all artifacts to a dedicated workspace directory

How to install azure-cloud-migrate

npx skills add https://github.com/microsoft/azure-skills --skill azure-cloud-migrate
Prerequisites
  • Azure subscription and credentials configured
  • Source application code or infrastructure definitions accessible
  • Understanding of source cloud platform (AWS, GCP, Heroku, or Kubernetes)
Claude Code
Cursor
Windsurf
Cline

How to use azure-cloud-migrate

  1. 1.Run the skill and specify your source cloud platform and target Azure service
  2. 2.Review the generated assessment report identifying service mappings and migration blockers
  3. 3.Execute the code migration phase to convert application code and configurations
  4. 4.Address any flagged issues (hardcoded hostnames, runtime incompatibilities)
  5. 5.Test migrated code locally using the provided output artifacts
  6. 6.Hand off to azure-prepare skill for infrastructure provisioning and deployment

Use cases

Good for
  • Migrating AWS Lambda functions to Azure Functions with dependency conversion
  • Moving Heroku or Elastic Beanstalk applications to Azure App Service
  • Converting Kubernetes clusters (GKE/EKS) to Azure Container Apps
  • Assessing multi-cloud workloads before committing to Azure migration
  • Identifying service discovery and networking issues in containerized apps before migration
Who it's for
  • Cloud architects planning multi-cloud to Azure migrations
  • DevOps engineers managing workload transitions
  • Development teams modernizing legacy cloud applications
  • Organizations consolidating on Azure infrastructure

azure-cloud-migrate FAQ

What cloud platforms does this skill support?

AWS (Lambda, Elastic Beanstalk, Fargate, ECS), Google Cloud (App Engine, Cloud Run, GKE), Heroku, Kubernetes (self-hosted, EKS, GKE), and Spring Boot applications.

Does it modify my source code?

No. All output is written to a separate `<workspace-basename>-azure/` directory at the workspace root; your source code remains untouched.

What happens with hardcoded service URLs in Kubernetes apps?

The skill scans for hardcoded hostnames and ports (e.g., `http://order-service:3001`) during assessment and flags them for conversion to environment-variable-driven URLs, since Kubernetes DNS does not resolve in Container Apps.

Can it handle custom or unsupported migration paths?

Yes. If your scenario is not in the standard migration table, the skill uses Azure best-practices and documentation tools to generate guidance.

What's the next step after migration?

The skill hands off to the azure-prepare skill, which handles infrastructure provisioning, testing, and deployment to Azure.

Full instructions (SKILL.md)

Source of truth, from microsoft/azure-skills.


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.2"

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

SourceTargetReference
AWS LambdaAzure Functionslambda-to-functions.md (assessment, code-migration)
AWS Elastic BeanstalkAzure App Servicebeanstalk-to-app-service.md
HerokuAzure App Serviceheroku-to-app-service.md
Google App EngineAzure App Serviceapp-engine-to-app-service.md
AWS Fargate (ECS)Azure Container Appsfargate-to-container-apps.md (assessment, deployment)
Kubernetes (GKE/EKS/Self-hosted)Azure Container Appsk8s-to-container-apps.md
GCP Cloud RunAzure Container Appscloudrun-to-container-apps.md
Spring Boot (Azure Spring Apps/VMs)Azure Container Appsspring-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.