Azure Cloud Migrate
Handles the full assessment and code conversion workflow when you're moving workloads from AWS, GCP, or Heroku into Azure. You point it at Lambda functions, Beanstalk apps, or Kubernetes manifests, and it generates a migration report, rewrites your code for Functions or Container Apps, and outputs everything to a separate directory without touching your source. The scenario matrix is comprehensive (Lambda to Functions, Fargate to Container Apps, even Spring Boot migrations), and it enforces a phase-locked workflow so you can't skip the assessment step. One thing to like is the explicit rule about scanning for hardcoded service URLs in Kubernetes apps, since those DNS names won't resolve in Azure. Hands off to azure-prepare when it's time to deploy.
- GitHub stars
- 217
- last updated
- Jun 11, 2026
Install
$ npx -y skills add microsoft/github-copilot-for-azure --skill azure-cloud-migrate --agent claude-codeInstalls into .claude/skills of the current project.
Files
Azure Cloud Migrate
This skill handles assessment and code migration of existing cloud workloads to Azure.
Rules
- Follow phases sequentially — do not skip
- Generate assessment before any code migration
- Load the scenario reference and follow its rules
- Use
mcp_azure_mcp_get_azure_bestpracticesandmcp_azure_mcp_documentationMCP tools - Use the latest supported runtime for the target service
- Destructive actions require
ask_user— functions global-rules | app-service global-rules - 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
- 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_documentationandmcp_azure_mcp_get_azure_bestpracticestools.
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 | app-service assessment
- Migrate — Convert code/config using the scenario-specific migration guide → functions code-migration | app-service code-migration
- 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.
Sponsors
Details
- Repository
- github.com/microsoft/github-copilot-for-azure
- Categories
- Backend & APIs, DevOps & CI/CD, Git & Pull Requests, AI & Agent Building, Marketing & SEO, Cloud & Infrastructure, Java & JVM, Game Development
- First seen
- Jun 11, 2026
