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.
Assess and migrate cloud workloads from AWS, GCP, and other providers to Azure services.
Supports Lambda-to-Azure Functions migration with dedicated scenario reference and best practices Generates assessment reports mapping source services to Azure equivalents before any code conversion Converts source code to target Azure runtime models, with output isolated in a separate <source-folder>-azure/ directory Requires sequential phase execution: assessment first, then migration, with user confirmation before destructive actions Hands off to azure-prepare skill for infrastructure provisioning, local testing, and deployment workflows
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
This skill provides comprehensive guidance and automation scripts for migrating cloud workloads from AWS, GCP, and Heroku to Azure. It demonstrates a strong security posture by emphasizing managed identities, secure secret management through Azure Key Vault, and hardened deployment configurations.
snykLOW
Analyzed May 7, 2026
No issues detected.
socketScore 0.9000 · 0 alerts
Analyzed May 7, 2026
license1
maintenance1
quality0.9
supply chain1
vulnerability1
0 alerts
Also in this package
Other skills from microsoft/azure-skills · top by installs.
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)
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
No matching scenario? Use mcpazuremcpdocumentation and mcpazuremcpgetazurebestpractices 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
Create<workspace-root-basename>-azure/ at workspace root
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)
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)
Ask User — "Migration complete. Test locally or deploy to Azure?"
Hand off to azure-prepare for infrastructure, testing, and deployment
Track progress in migration-status.md — see [workflow-details.md](references/workflow-details.md).