Azure Cloud Migrate

MicrosoftOfficialCreated by Microsoft

Skill
Workflow
Cloud and DevOps
MIT
Low risk

From the author

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.

— the description by Microsoft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Azure Cloud Migrate provides a structured, multi-phase workflow for transitioning applications from various cloud platforms to Azure. It focuses on assessing the current architecture, mapping services to Azure equivalents, and performing the necessary code and configuration conversions. The skill ensures a methodical approach by requiring an assessment report before any migration actions occur, and it provides specific guidance for common migration paths such as AWS Lambda to Azure Functions, Heroku to App Service, and Kubernetes to Container Apps.

What it does

Generates comprehensive migration assessment reports for cross-cloud workloads.
Maps source platform services, compute configurations, and dependencies to Azure equivalents.
Provides guidance for converting application code and configuration files.
Audits source code for platform-specific service discovery patterns.
Creates architecture diagrams for both current and target states.
Tracks migration progress and provides resource-level status updates.

When to use it

When planning to migrate workloads from AWS Lambda, Elastic Beanstalk, or Fargate to Azure.
When moving applications from Heroku or Google App Engine to Azure App Service.
When transitioning Kubernetes or Cloud Run deployments to Azure Container Apps.
When you need a structured assessment of migration readiness and effort.

Advantages

Ensures a consistent, step-by-step migration process.
Reduces risk by requiring a detailed assessment report before code changes.
Provides clear mapping between source platform features and Azure services.
Includes specific checks for common migration pitfalls like hardcoded service discovery.

Usage examples

“Assess my current AWS Lambda project for migration to Azure Functions.”: The agent will analyze the Lambda project, map the services to Azure Functions, and generate a migration assessment report in the output directory.
“Migrate my Heroku application to Azure App Service.”: The agent will perform an assessment, guide the conversion of configuration files, and assist in setting up the application for Azure App Service.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/azure-cloud-migrate/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip azure-cloud-migrate.zip -d .agents/skills

Documentation by Microsoft

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_bestpractices and mcp_azure_mcp_documentation MCP 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_documentation and mcp_azure_mcp_get_azure_bestpractices 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 | 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.

Files

ATTRIBUTION.mdAdded by AutoGineer989 B
LICENSELicence file added by AutoGineer1.1 KiB
SKILL.md4.3 KiB
references/services/app-service/app-engine-to-app-service.md7.1 KiB
references/services/app-service/assessment.md5.2 KiB
references/services/app-service/beanstalk-to-app-service.md6.4 KiB
references/services/app-service/code-migration.md5.0 KiB
references/services/app-service/global-rules.md2.8 KiB
references/services/app-service/heroku-to-app-service.md7.5 KiB
references/services/container-apps/assessment-guide.md7.0 KiB
references/services/container-apps/cloudrun-assessment-guide.md2.5 KiB
references/services/container-apps/cloudrun-deployment-guide.md7.9 KiB
references/services/container-apps/cloudrun-to-container-apps.md2.2 KiB
references/services/container-apps/deployment-guide.md9.6 KiB
references/services/container-apps/fargate-assessment-guide.md2.4 KiB
references/services/container-apps/fargate-deployment-guide.md10.1 KiB
references/services/container-apps/fargate-to-container-apps.md4.0 KiB
references/services/container-apps/k8s-to-container-apps.md4.9 KiB
references/services/container-apps/spring-apps-to-aca.md3.8 KiB
references/services/container-apps/spring-assessment-guide.md5.2 KiB
references/services/container-apps/spring-dependency-patterns.md1.2 KiB
references/services/container-apps/spring-deployment-guide.md15.1 KiB
references/services/functions/assessment.md6.3 KiB
references/services/functions/code-migration.md6.0 KiB
references/services/functions/global-rules.md3.3 KiB
references/services/functions/lambda-to-functions.md10.2 KiB
references/services/functions/runtimes/csharp.md5.5 KiB
references/services/functions/runtimes/java.md6.4 KiB
references/services/functions/runtimes/javascript.md8.5 KiB
references/services/functions/runtimes/powershell.md5.0 KiB
references/services/functions/runtimes/python.md6.4 KiB
references/services/functions/runtimes/typescript.md3.5 KiB
references/workflow-details.md2.3 KiB

references/services/app-service/app-engine-to-app-service.md

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: python314`	Runtime stack: Python 3.14	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.14'
      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 closest mapping from Datastore. Use Cosmos DB for MongoDB API if the app already uses MongoDB-compatible patterns.

Cloud Tasks → Service Bus / Durable Functions

Cloud Tasks Feature	Azure Equivalent
HTTP target tasks	Service Bus + Azure Functions
App Engine target tasks	Service Bus + WebJobs
Task scheduling (delayed)	Service Bus scheduled messages
Task retry / dead-letter	Service Bus retry + dead-letter queue
Rate limiting	Service Bus message throttling
Task orchestration	Durable Functions (fan-out/fan-in)

Traffic Splitting → Deployment Slots

App Engine Feature	Azure Equivalent
Version traffic splitting (%)	Slot traffic routing (%)
Canary deployment	Slot with low traffic %
A/B testing	Slot traffic routing
Version rollback	Slot swap (revert)
Gradual rollout	Increase slot traffic % incrementally
Warmup requests	Slot warm-up (pre-swap)

// Configure traffic routing: 90% production, 10% staging
resource siteConfig 'Microsoft.Web/sites/config@2023-12-01' = {
  name: 'web'
  properties: {
    experiments: {
      rampUpRules: [{
        actionHostName: '${webApp.name}-staging.azurewebsites.net'
        reroutePercentage: 10
        name: 'staging'
      }]
    }
  }
}

Memcache → Azure Cache for Redis

Memcache Feature	Azure Cache for Redis
`memcache.get()` / `set()`	`redis.get()` / `redis.set()`
Shared memcache	Azure Cache for Redis (Basic)
Dedicated memcache	Azure Cache for Redis (Standard/Premium)
Session store	Redis session store
Cache expiry	Redis TTL

Environment Variables Migration

Source	Target	Notes
`app.yaml` env_variables	App Settings	Non-sensitive config
Secret Manager refs	Key Vault references	`@Microsoft.KeyVault(SecretUri=...)`
Runtime env (auto-injected)	App Settings	Map GAE-specific vars
`GAE_APPLICATION`	`WEBSITE_SITE_NAME`	Auto-injected by App Service
`PORT`	`PORT`	Auto-injected by App Service
`GOOGLE_CLOUD_PROJECT`	(no equivalent)	GCP project IDs identify a runtime environment; Azure subscription IDs are a tooling/billing context, not a runtime equivalent. Use App Service `WEBSITE_RESOURCE_GROUP` or rely on `DefaultAzureCredential` to discover the subscription at runtime if needed.

CI/CD Migration

Cloud Build / gcloud	Azure Equivalent
`gcloud app deploy`	`az webapp deploy` or `azd deploy`
`cloudbuild.yaml`	`.github/workflows/deploy.yml`
Cloud Build triggers	GitHub Actions triggers
Artifact Registry	Azure Container Registry
`gcloud app versions`	Deployment slots

Reference Links

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Low risk

Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by

Microsoft

Publisher

Microsoft (Official)

Source

microsoft/skills · .github/plugins/azure-skills/skills/azure-cloud-migrate · commit 0696600

Licence

MIT License (redistribution allowed)

LICENSE (added by AutoGineer from .github/plugins/azure-skills/LICENSE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-08

Also distributed in

microsoft/azure-skills

AutoGineer is not affiliated with or endorsed by Microsoft.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download azure-cloud-migrate.zip

From the author

AutoGineer summary

What it does

When to use it

Advantages

Usage examples

Install

Documentation by Microsoft

Azure Cloud Migrate

Rules

Migration Scenarios

Output Directory

Steps

Files

references/services/app-service/app-engine-to-app-service.md

Google App Engine to Azure App Service Migration

Service Mapping

Standard vs Flex → App Service Plan Mapping

app.yaml → azure.yaml + Bicep

App Engine Configuration Mapping

Example: app.yaml → Bicep

Datastore / Firestore → Cosmos DB

Cloud Tasks → Service Bus / Durable Functions

Traffic Splitting → Deployment Slots

Memcache → Azure Cache for Redis

Environment Variables Migration

CI/CD Migration

Reference Links

Requirements and compatibility

Security

Attribution and licence

Related skills

Modal

Cloud Infrastructure Network Engineer

Deployment Validation Cloud Architect

Airflow Dag Patterns

Cost Optimization

Hybrid Cloud Networking

Download ZIP

`app.yaml` → `azure.yaml` + Bicep

Example: `app.yaml` → Bicep