Azure Cloud Migration Assistant
Assess cross-cloud workloads and convert them for Azure services.
The rules require assessment before migration, user confirmation for destructive actions and major deployment choices, isolated output, and identity-first secret handling; they also mention HTTPS, health checks, and deployment slots. Data-flow disclosure, dependency security, concrete rollback procedures, and exact permission boundaries remain incomplete, so 7 points are deducted.
Sequential phases, assessment gating, status tracking, progress updates, and abnormal workload checks are specified. However, several MCP dependencies are not verified in the supplied material, scenario references are incomplete, and key paths lack input validation, controlled failure handling, and diagnosable error feedback; 2 points are deducted within the static cap.
The skill declares clear cross-cloud triggers, source platforms, target services, and several Kubernetes/Container Apps boundaries. It does not define non-fit ranges or trigger precedence, and provides no Chinese-language or mainland-China network guidance; core MCP access may also be network-sensitive, so 6 points are deducted.
The skill includes metadata, MIT licensing, a version, phased organization, scenario tables, output conventions, examples, limitations, and handoff guidance. It lacks a clear maintainer, changelog, upgrade path, installation notes, and FAQ, and some referenced files are not present or verifiable in the supplied material; 6 points are deducted.
Service mappings, assessment templates, configuration examples, identity guidance, and handoff instructions address the core migration workflow and specify usable report/output artifacts. Still, results depend on the actual workload, external MCP tools, and later azure-prepare stages, with no verified representative output, test coverage, or cost/alternative analysis; 1 point is deducted within the static cap.
The repository context shows general CI, evaluation workflows, and tests, but not skill-specific tests or third-party execution evidence covering azure-cloud-migrate's key paths. Most claims are author-supplied mappings and examples, warranting only limited auditability; 1 point is deducted.
- This is a low-confidence static review; no migration, MCP call, code conversion, or deployment was executed.
- Before use, verify MCP availability, required source files, Azure subscription and region choices, and all generated Bicep, identity settings, runtime versions, and data-migration plans.
- The skill is broad but under-specifies non-fit cases, recovery, cost impact, and cross-border network reachability; documentation examples should not be treated as production-validated solutions.
What does this skill do, and when should you use it?
Azure Cloud Migrate assesses existing cloud workloads before converting their code and configuration for Azure. It supports AWS Lambda to Azure Functions, Beanstalk, Heroku, and App Engine to Azure App Service, plus several container and Spring Boot migrations to Azure Container Apps. The workflow is sequential and uses Azure MCP documentation and best-practice tools. It fits engineering teams planning a defined AWS, GCP, or Kubernetes migration, but it does not cover the full infrastructure deployment lifecycle.
Reads and analyzes source code and existing workload details, maps source services to Azure targets, generates scenario-specific assessment reports, and scans HTTP clients for hardcoded hostnames and ports that may break Container Apps service discovery. It then converts code and configuration according to the selected migration guide, uses Azure documentation and best-practice MCP tools, and tracks progress in migration-status.md. Outputs are written to <workspace-root-basename>-azure/ at the workspace root, while the source directory remains unchanged.
- A development team migrating an AWS Lambda application to Azure Functions.
- A platform team moving an AWS Elastic Beanstalk, Heroku, or Google App Engine application to Azure App Service.
- An engineering team migrating AWS Fargate, ECS, GKE, EKS, or self-hosted Kubernetes workloads to Azure Container Apps.
- A team moving a GCP Cloud Run or Spring Boot workload to Azure Container Apps.
What are this skill's strengths and limitations?
- Supports clearly defined migration paths for Lambda, Beanstalk, Heroku, App Engine, Fargate, Kubernetes, Cloud Run, and Spring Boot.
- Enforces assessment before migration and provides scenario-specific reference guides.
- Audits service-discovery issues in Container Apps and requires resource-level progress updates during long operations.
- Defines the output location, status tracking, and confirmation rules for destructive actions.
- Only the listed migration scenarios are explicitly covered; other scenarios depend on Azure documentation and best-practice MCP tools.
- Requires Azure MCP tools plus access to the source code and workspace filesystem.
- The supplied materials provide no skill-specific test coverage or detailed failure-recovery procedure.
- It does not itself handle the complete infrastructure preparation, testing, and deployment lifecycle.
How do you install this skill?
Install the collection with npx skills add microsoft/skills, then select the required skills in the wizard. Skills are installed in the selected agent directory, such as .github/skills/ for GitHub Copilot. The source does not document a separate installation command for this individual plugin skill.
How do you use this skill?
Use a prompt that names a supported migration scenario, such as “migrate AWS Lambda to Azure Functions” or “assess and migrate a GKE workload to Azure Container Apps.” The skill assesses first and migrates second, then asks: “Migration complete. Test locally or deploy to Azure?” Infrastructure preparation, testing, and deployment are handed off to azure-prepare.