azure-cloud-migrate

Assess and migrate AWS, GCP, and Heroku workloads to Azure Functions, App Service, and Container Apps.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/merceralex397-collab/alex-stack --skill azure-cloud-migrate-merceralex397-collab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-cloud-migrate
Source: https://github.com/merceralex397-collab/alex-stack/tree/main/dev/azure-profile/azure-skills-main/azure-skills-main/.github/plugins/azure-skills/skills/azure-cloud-migrate
Command: npx skills add https://github.com/merceralex397-collab/alex-stack --skill azure-cloud-migrate-merceralex397-collab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Moving workloads from AWS, Google Cloud, or Heroku to Azure requires manual service mapping, code conversion, and configuration translation that is error-prone and time-consuming. This Skill automates the assessment and code migration phases, producing structured reports and converted code for Azure targets. ## Core Features & Use Cases - Migration Assessment: Generates a standardized assessment report with service mappings, dependency analysis, architecture diagrams, and complexity ratings before any code changes. - Code Migration: Converts source code and configuration across eight scenarios, including Lambda to Azure Functions, Beanstalk/Heroku/App Engine to App Service, and Fargate/Kubernetes/Cloud Run/Spring Boot to Container Apps. - Use Case: A team running AWS Lambda functions wants to move to Azure. The Skill inventories the functions, maps triggers and bindings to Azure equivalents, converts the code to the latest Azure Functions programming model, and hands off to azure-prepare for infrastructure and deployment. ## Quick Start Assess my AWS Lambda project in this workspace and migrate it to Azure Functions with a full assessment report.

Frequently Asked Questions about azure-cloud-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate AWS Lambda functions to Azure Functions?▼

Run the assessment phase first to inventory functions, map triggers and bindings, and generate a migration report. Then the code migration phase converts each Lambda to the latest Azure Functions programming model using bindings instead of SDKs.

How to migrate Kubernetes workloads to Azure Container Apps?▼

The Skill exports Kubernetes resources, checks compatibility against Container Apps limits, migrates images to ACR, and deploys with az containerapp commands. StatefulSets, DaemonSets, and custom CRDs are flagged as blockers requiring redesign.

What source platforms does Azure cloud migration support?▼

Supported sources are AWS Lambda, Elastic Beanstalk, Fargate (ECS), Kubernetes (GKE/EKS/self-hosted), Google App Engine, Cloud Run, Heroku, and Spring Boot. Targets are Azure Functions, App Service, and Container Apps.

What are the limitations of migrating Fargate to Container Apps?▼

Container Apps supports a maximum of 4 vCPU and 8 GiB memory per container versus Fargate's 16 vCPU and 120 GiB. Persistent storage is limited to Azure Files, and replicas cap at 300 per revision, so large workloads need redesign.

Why do Kubernetes service names fail after migrating to Container Apps?▼

Kubernetes DNS names like http://order-service:3001 do not resolve in Container Apps, which uses internal HTTPS FQDNs. The Skill audits source code for hardcoded hostnames and flags them for environment-variable-driven URL injection.