
Azure Cloud Migrate
- 414k installs
- 1.3k repo stars
- Updated July 26, 2026
- microsoft/azure-skills
azure-cloud-migrate is a Claude skill that assesses cross-cloud workloads and migrates them to Azure services with reports and code conversion.
About
This skill assesses existing cloud workloads and migrates them to Azure, generating an assessment report before any code conversion. It supports eight source-to-target scenarios such as AWS Lambda to Azure Functions and Kubernetes/Fargate/Cloud Run to Azure Container Apps. It runs phases sequentially, flags hardcoded service-discovery hostnames, and hands off to azure-prepare for infrastructure and deployment. A developer uses it to plan and execute a cross-cloud move onto Azure.
- Assesses and migrates cross-cloud workloads to Azure with a report generated before any code migration
- Covers Lambda->Functions, Beanstalk/Heroku/App Engine->App Service, and Fargate/Kubernetes/Cloud Run/Spring Boot->Contai
- Audits app code for hardcoded service-discovery hostnames that will not resolve in Container Apps
Azure Cloud Migrate by the numbers
- 414,319 all-time installs (skills.sh)
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
azure-cloud-migrate capabilities & compatibility
MIT-licensed skill; uses Azure MCP tools and an Azure subscription for the actual migration.
- Capabilities
- cloud migration · workload assessment · code conversion · cross cloud migration
- Works with
- azure · aws · gcp · kubernetes · docker
- Use cases
- devops
- Runs
- Runs locally
- Pricing
- Free
What azure-cloud-migrate says it does
Generate assessment before any code migration
Kubernetes DNS names (e.g., `http://order-service:3001`) do not resolve in Container Apps.
This skill handles **assessment and code migration** of existing cloud workloads to Azure.
npx skills add https://github.com/microsoft/azure-skills --skill azure-cloud-migrateAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 414k |
|---|---|
| repo stars | ★ 1.3k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 26, 2026 |
| Repository | microsoft/azure-skills ↗ |
How do you migrate App Engine to Azure?
Assess and migrate an AWS/GCP/Heroku/Kubernetes workload to the matching Azure service.
Who is it for?
Assessing and migrating an AWS, GCP, Heroku or Kubernetes workload to the equivalent Azure service.
Skip if: Migrations with no matching scenario (fall back to Azure documentation/best-practices MCP tools).
When should I use this skill?
A user wants to migrate Lambda to Functions, AWS/GCP to Azure, Beanstalk/Heroku/App Engine to App Service, or ECS/Kubernetes/Cloud Run/Spring Boot to Container Apps.
What you get
azure.yaml configuration, Bicep templates, Azure service mapping plan, migrated App Service deployment
- azure.yaml
- Bicep templates
- service mapping document
By the numbers
- 8 migration scenarios in the mapping table
- 5 workflow steps (Create, Assess, Migrate, Ask User, Hand off)
Files
Google App Engine to Azure App Service Migration
Detailed guidance for migrating Google App Engine applications to Azure App Service.
Service Mapping
| GCP Service | Azure Equivalent |
|---|---|
| App Engine (Standard) | Azure App Service (Standard/Premium plan) |
| App Engine (Flex) | Azure App Service (Premium v3) or Container Apps |
| App Engine Services | App Service apps (one per service) |
app.yaml | azure.yaml + Bicep |
| Datastore / Firestore | Azure Cosmos DB |
| Cloud SQL (PostgreSQL) | Azure Database for PostgreSQL Flexible Server |
| Cloud SQL (MySQL) | Azure Database for MySQL Flexible Server |
| Cloud Storage | Azure Blob Storage |
| Cloud Tasks | Azure Service Bus / Durable Functions |
| Cloud Pub/Sub | Azure Service Bus / Event Grid |
| Memcache / Memorystore | Azure Cache for Redis |
| Cloud Scheduler | Azure Functions Timer trigger |
| Cloud CDN | Azure Front Door / Azure CDN |
| Cloud DNS | Azure DNS |
| Cloud Logging | Application Insights / Azure Monitor |
| Cloud Monitoring | Azure Monitor Metrics |
| Cloud Trace | Application Insights (distributed tracing) |
| Cloud IAM | Managed Identity + Azure RBAC |
| Cloud Build | GitHub Actions / Azure DevOps |
| Traffic Splitting | Deployment Slots (weighted routing) |
| Service Versions | Deployment Slots |
| Cloud KMS | Azure Key Vault |
| Secret Manager | Azure Key Vault |
| Cloud Endpoints | Azure API Management |
| Identity-Aware Proxy | Azure Front Door + Entra ID auth |
| VPC Connector | VNet Integration |
Standard vs Flex → App Service Plan Mapping
| App Engine Tier | App Service Equivalent | Notes |
|---|---|---|
| Standard (F1 instance) | Free (F1) | Dev/test only |
| Standard (B1/B2) | Basic (B1/B2) | Low-traffic apps |
| Standard (auto-scaling) | Standard (S1-S3) | Auto-scale, slots |
| Flex (custom runtime) | Premium v3 (P1v3-P3v3) | Custom containers |
| Flex (high-memory) | Premium v3 (P3v3) | Up to 32 GB RAM |
app.yaml → azure.yaml + Bicep
App Engine Configuration Mapping
app.yaml Field | Azure Equivalent | Implementation |
|---|---|---|
runtime: python312 | Runtime stack: Python 3.12 | Bicep siteConfig.linuxFxVersion |
instance_class: F2 | App Service Plan SKU | Bicep sku.name |
automatic_scaling | Autoscale settings | Bicep Microsoft.Insights/autoscalesettings |
env_variables | App Settings | Bicep siteConfig.appSettings |
handlers (URL routing) | App Service path mappings / Front Door | Route rules |
entrypoint | Startup command | az webapp config set --startup-file |
vpc_access_connector | VNet Integration | Bicep virtualNetworkSubnetId |
inbound_services: [warmup] | Always On | Bicep siteConfig.alwaysOn: true |
Example: app.yaml → Bicep
# app.yaml (GCP)
runtime: python312
instance_class: F2
automatic_scaling:
min_instances: 1
max_instances: 10
env_variables:
DATABASE_URL: "postgres://..."// Bicep equivalent
resource appServicePlan 'Microsoft.Web/serverfarms@2023-12-01' = {
sku: { name: 'S2', capacity: 1 }
properties: { reserved: true }
}
resource webApp 'Microsoft.Web/sites@2023-12-01' = {
properties: {
siteConfig: {
linuxFxVersion: 'PYTHON|3.12'
alwaysOn: true
appSettings: [
{ name: 'PGHOST', value: postgresServer.properties.fullyQualifiedDomainName }
]
}
}
}Datastore / Firestore → Cosmos DB
| Datastore Feature | Cosmos DB Equivalent |
|---|---|
| Entity / Document | Item |
| Kind / Collection | Container |
| Namespace | Database |
| Key / ID | Partition key + ID |
| Ancestor queries | Hierarchical partition keys |
| Eventual consistency | Session or Eventual consistency |
| Strong consistency | Strong consistency |
ndb / google.cloud.datastore | @azure/cosmos SDK |
💡 Tip: Use Cosmos DB for NoSQL API for the cl
Related skills
How it compares
Use azure-cloud-migrate for GAE-to-Azure replatforming rather than general Azure compute troubleshooting or Copilot SDK hosting skills.
FAQ
Does it migrate code before assessing?
No; a rule requires generating an assessment report before any code migration and following phases sequentially.
What service-discovery issue does it catch?
Kubernetes DNS names like http://order-service:3001 do not resolve in Container Apps, so it flags hardcoded hostnames for env-var injection.
Is Azure Cloud Migrate safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.