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/heroku-to-app-service.md

Heroku to Azure App Service Migration

Detailed guidance for migrating Heroku applications to Azure App Service.

Service Mapping

Heroku Service	Azure Equivalent
Heroku App	Azure App Service
Dynos (Web)	App Service instances
Dynos (Worker)	WebJobs (continuous) or Azure Functions
Procfile	Startup command / Docker entrypoint
Buildpacks	Docker or App Service runtime stacks
Config Vars	App Settings / App Configuration / Key Vault
Heroku Postgres	Azure Database for PostgreSQL Flexible Server
Heroku Redis	Azure Cache for Redis
Heroku Kafka	Azure Event Hubs (Kafka-compatible)
Add-ons (general)	Azure managed services
Heroku Pipelines	GitHub Actions / Azure DevOps
Review Apps	Deployment Slots
Heroku CI	GitHub Actions
Heroku Scheduler	WebJobs (triggered) or Azure Functions Timer
Heroku ACM (SSL)	App Service Managed Certificate
Custom Domains	App Service Custom Domains
Heroku Logs / Logplex	Application Insights / Azure Monitor
Heroku Metrics	Azure Monitor Metrics
Heroku Connect	Azure Data Factory or Logic Apps
Private Spaces	App Service Environment (ASE)

Dyno → App Service Plan Mapping

Heroku Dyno Type	App Service Plan	Notes
Free / Eco	Free (F1)	Dev/test only — F1 has shared compute with quota limits (CPU minutes), not equivalent to Heroku's 60 min/day cap. See App Service Free SKU limits
Basic	Basic (B1)	No auto-scale, no slots
Standard-1X (512 MB)	Standard (S1)	Auto-scale, slots, custom domains
Standard-2X (1 GB)	Standard (S2)	More memory
Performance-M (2.5 GB)	Premium v3 (P1v3)	VNet, more instances
Performance-L (14 GB)	Premium v3 (P3v3)	High-memory workloads
Private-M / Private-L	App Service Environment (ASE)	Network-isolated

Procfile → Startup Configuration

Web Process

Procfile Entry	Azure Equivalent
`web: node server.js`	Startup command: `node server.js`
`web: gunicorn app:app`	Startup command: `gunicorn --bind=0.0.0.0 --timeout 600 app:app`
`web: java -jar target/app.jar`	Startup command: `java -jar app.jar`
`web: bundle exec puma -C config/puma.rb`	Custom container with Dockerfile

Worker Process

Heroku worker dynos have no direct App Service equivalent. Migration paths:

Heroku Worker Pattern	Azure Equivalent
`worker: node worker.js`	WebJob (continuous)
`worker: celery -A tasks worker`	Container App or AKS
`clock: node scheduler.js`	Azure Functions Timer trigger
`release: rake db:migrate`	Deployment slot swap scripts

Add-ons → Azure Managed Services

Heroku Add-on	Azure Equivalent	Migration Notes
Heroku Postgres	PostgreSQL Flexible Server	Use Azure DMS for data migration
Heroku Redis	Azure Cache for Redis	Export/import RDB or use replication
Heroku Kafka	Azure Event Hubs (Kafka API)	Compatible Kafka protocol
Papertrail	Application Insights	Structured logging migration
New Relic	Application Insights	APM feature parity
SendGrid	Azure Communication Services or SendGrid on Azure	SendGrid available via Azure Marketplace
Cloudinary	Azure Blob Storage + CDN	Media storage + delivery
Memcachier	Azure Cache for Redis	Redis supports memcache patterns
Bonsai (Elasticsearch)	Azure AI Search or Elastic on Azure	Search service migration
Heroku Scheduler	Azure Functions Timer trigger	Cron-based scheduling
Bucketeer (S3)	Azure Blob Storage	Object storage migration

Config Vars → App Configuration / Key Vault

Config Var Type	Azure Target	Implementation
`DATABASE_URL`	App Setting (managed identity)	Use Entra auth, not connection string
`REDIS_URL`	App Setting	Azure Cache connection string or managed identity
`SECRET_KEY`	Key Vault reference	`@Microsoft.KeyVault(SecretUri=...)`
`API_KEY` (third-party)	Key Vault reference	Store in Key Vault
`NODE_ENV` / `RAILS_ENV`	App Setting	Add as a regular App Setting (e.g., `NODE_ENV=production`) — controls runtime behavior. Do NOT confuse with `WEBSITES_NODE_DEFAULT_VERSION`, which controls the Node.js engine version on Windows App Service.
`PORT`	Auto-injected	App Service sets `PORT` automatically
Feature flags	App Configuration	Feature management support built-in

⚠️ Warning: Heroku's DATABASE_URL includes credentials. On Azure, use managed identity authentication instead. Never migrate connection strings with embedded passwords.

Buildpacks → Docker

For apps using standard runtimes, use App Service runtime stacks directly. For custom buildpacks, migrate to Docker:

Buildpack Scenario	Azure Approach
Official Node.js buildpack	App Service Node.js runtime stack
Official Python buildpack	App Service Python runtime stack
Official Java buildpack	App Service Java runtime stack
Multi-buildpack (e.g., Node + Python)	Custom Dockerfile
Custom buildpack (apt packages)	Custom Dockerfile
Heroku CNB (Cloud Native Buildpack)	Azure Container Apps with CNB

Heroku Pipelines → GitHub Actions

Pipeline Feature	Azure Equivalent
Pipeline stages (dev → staging → prod)	GitHub Actions environments
Auto-deploy on push	GitHub Actions `on: push` trigger
Review Apps	Deployment slots with PR-based deploy
Pipeline promotion	Slot swap (staging → production)
Heroku CI test runner	GitHub Actions test job
Release phase	Pre-swap slot scripts

Example: GitHub Actions Deployment

name: Deploy to App Service
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    permissions:
      id-token: write   # Required for azure/login@v2 OIDC token request
      contents: read    # Required to checkout the repo
    steps:
      - uses: actions/checkout@v4
      - uses: azure/login@v2
        with:
          client-id: ${{ secrets.AZURE_CLIENT_ID }}
          tenant-id: ${{ secrets.AZURE_TENANT_ID }}
          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
      - uses: azure/webapps-deploy@v3
        with:
          app-name: '<app-name>'
          slot-name: 'staging'

⚠️ Without the permissions: block, azure/login@v2's OIDC token request fails with HTTP 403.

Review Apps → Deployment Slots

Heroku Review Apps	App Service Deployment Slots
Auto-create per PR	Create via GitHub Actions per PR
Unique URL per PR	`<app>-<slot>.azurewebsites.net`
Auto-destroy on PR close	Delete slot in PR close workflow
Shared pipeline config	Slot-specific App Settings
`app.json` postdeploy scripts	Slot swap pre/post actions

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/heroku-to-app-service.md

Heroku to Azure App Service Migration

Service Mapping

Dyno → App Service Plan Mapping

Procfile → Startup Configuration

Web Process

Worker Process

Add-ons → Azure Managed Services

Config Vars → App Configuration / Key Vault

Buildpacks → Docker

Heroku Pipelines → GitHub Actions

Example: GitHub Actions Deployment

Review Apps → Deployment Slots

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