Agent skill · software engineering · aiskillstore
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, 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.
Why this skill is useful
Adds executable scripts for assessing and migrating cloud workloads to Azure, including specific code conversion patterns and best practices not widely known.
What it needs
Requires azure-cli installed locally. Requires azure account access. About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 mcpazuremcpgetazurebestpractices and mcpazuremcpdocumentation MCP tools 5. Use the latest supported runtime for the target service 6. Destructive actions require askuser — 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 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 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/azure-cloud-migrate