Generated banner for Azure Cloud Migrate
Generated logo for Azure Cloud Migrate

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

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/microsoft/azure-cloud-migrate/download
  2. 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

  1. Follow phases sequentially — do not skip

  2. Generate assessment before any code migration

  3. Load the scenario reference and follow its rules

  4. Use mcp_azure_mcp_get_azure_bestpractices and mcp_azure_mcp_documentation MCP tools

  5. Use the latest supported runtime for the target service

  6. Destructive actions require ask_user — functions global-rules | app-service global-rules

  7. 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

  8. 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

SourceTargetReference
AWS LambdaAzure Functionslambda-to-functions.md (assessment, code-migration)
AWS Elastic BeanstalkAzure App Servicebeanstalk-to-app-service.md
HerokuAzure App Serviceheroku-to-app-service.md
Google App EngineAzure App Serviceapp-engine-to-app-service.md
AWS Fargate (ECS)Azure Container Appsfargate-to-container-apps.md (assessment, deployment)
Kubernetes (GKE/EKS/Self-hosted)Azure Container Appsk8s-to-container-apps.md
GCP Cloud RunAzure Container Appscloudrun-to-container-apps.md
Spring Boot (Azure Spring Apps/VMs)Azure Container Appsspring-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

  1. Create <workspace-root-basename>-azure/ at workspace root

  2. Assess — Analyze source, map services, generate report using the scenario-specific assessment guide → functions assessment | app-service assessment

  3. Migrate — Convert code/config using the scenario-specific migration guide → functions code-migration | app-service code-migration

  4. Ask User — "Migration complete. Test locally or deploy to Azure?"

  5. Hand off to azure-prepare for infrastructure, testing, and deployment

Track progress in migration-status.md — see workflow-details.md.

Files

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

AWS Elastic Beanstalk to Azure App Service Migration

Detailed guidance for migrating AWS Elastic Beanstalk applications to Azure App Service.

Service Mapping

AWS ServiceAzure Equivalent
Elastic BeanstalkAzure App Service
Elastic Beanstalk EnvironmentApp Service + App Service Plan
Platform PresetsRuntime Stacks
.ebextensions/Bicep + App Settings
ProcfileStartup Command
RDS (PostgreSQL)Azure Database for PostgreSQL Flexible Server
RDS (MySQL)Azure Database for MySQL Flexible Server
RDS (SQL Server)Azure SQL Database
ElastiCache (Redis)Azure Cache for Redis
ElastiCache (Memcached)Azure Cache for Redis
S3Azure Blob Storage
ALB / ELBApp Service built-in LB / Azure Front Door
Route 53Azure DNS
ACM (Certificate Manager)App Service Managed Certificate
CloudWatchApplication Insights / Azure Monitor
CloudWatch AlarmsAzure Monitor Alerts
X-RayApplication Insights (distributed tracing)
IAM RolesManaged Identity + Azure RBAC
CodePipeline / CodeBuildGitHub Actions / Azure DevOps
CloudFormationBicep / ARM Templates
Parameter StoreAzure App Configuration
Secrets ManagerAzure Key Vault
SQSAzure Service Bus / Storage Queue
SNSAzure Event Grid
Auto Scaling GroupApp Service Autoscale
VPCAzure VNet Integration
Security GroupsNSG + App Service Access Restrictions

Platform Preset → Runtime Stack Mapping

Beanstalk PlatformApp Service Runtime Stack
Node.js 22Node 22 LTS
Node.js 24Node 24 LTS
Python 3.13Python 3.13
Python 3.14Python 3.14
Java 21 (Corretto)Java 21 (Microsoft Build of OpenJDK)
Java 24 (Corretto)Java 24 (Microsoft Build of OpenJDK)
.NET 10 on Linux.NET 10
Go (Docker)Custom Container (Go)
RubyCustom Container (Ruby)
PHP 8.xPHP 8.x
DockerAzure App Service (Custom Container)

.ebextensions/ Migration

Beanstalk .ebextensions/ YAML configs map to Bicep and App Settings:

.ebextensions/ FeatureAzure EquivalentImplementation
option_settings (env vars)App SettingsBicep siteConfig.appSettings
packages (yum/apt)Startup script or DockerfileCustom container or startup command
files (config files)Deployment package or Blob StorageInclude in app deployment
commands / container_commandsStartup command or deployment scriptaz webapp config set --startup-file
Resources (CloudFormation)Bicep modulesEquivalent Azure resources
services (sysvinit)WebJobs (continuous) or Azure FunctionsBackground processing — App Service "Always On" only prevents idle unload; it is NOT a replacement for sysvinit-style background services
Example: .ebextensions/ → Bicep
# .ebextensions/environment.config (AWS)
option_settings:
  aws:elasticbeanstalk:application:environment:
    NODE_ENV: production
    DB_HOST: mydb.xxx.rds.amazonaws.com
// Bicep equivalent
resource webApp 'Microsoft.Web/sites@2023-12-01' = {
  properties: {
    siteConfig: {
      appSettings: [
        { name: 'NODE_ENV', value: 'production' }
        { name: 'PGHOST', value: postgresServer.properties.fullyQualifiedDomainName }
      ]
    }
  }
}

RDS → Azure Database Migration

RDS FeatureAzure Equivalent
Multi-AZ deploymentZone-redundant HA
Read replicasRead replicas
Automated backupsAutomated backups (up to 35 days)
Parameter groupsServer parameters
Subnet groupsVNet integration + private endpoints
IAM authenticationMicrosoft Entra authentication
RDS ProxyAzure Database for PostgreSQL Flexible Server (built-in PgBouncer)

💡 Tip: Use Azure Database Migration Service (DMS) for data migration from RDS.

Auto Scaling Migration

Beanstalk ScalingApp Service Autoscale
MinSize / MaxSizeMin/Max instance count
Trigger metric (CPU, Network)Autoscale rules (CPU, Memory, HTTP queue)
BreachDurationTime window + cool-down period
ScalingAdjustmentScale-out/in increment
Time-based scalingSchedule-based autoscale rules
resource autoscale 'Microsoft.Insights/autoscalesettings@2022-10-01' = {
  properties: {
    targetResourceUri: appServicePlan.id
    profiles: [{
      capacity: { minimum: '2', maximum: '10', default: '2' }
      rules: [{
        metricTrigger: {
          metricName: 'CpuPercentage'
          operator: 'GreaterThan'
          threshold: 70
          timeAggregation: 'Average'
          timeWindow: 'PT5M'
        }
        scaleAction: {
          direction: 'Increase'
          type: 'ChangeCount'
          value: '1'
          cooldown: 'PT5M'
        }
      }]
    }]
  }
}

ALB → App Service Load Balancing

ALB FeatureAzure Equivalent
Path-based routingApp Service path mappings or Front Door rules
Host-based routingCustom domains + Front Door
Health checksApp Service Health Check feature
SSL terminationBuilt-in TLS / Front Door
WAFAzure Front Door WAF or App Gateway WAF
Sticky sessionsARR Affinity (App Service)

For global load balancing with WAF, use Azure Front Door instead of App Service built-in LB.

Environment Variables Migration

SourceTargetNotes
option_settings (env vars)App SettingsNon-sensitive config
option_settings (secrets)Key Vault references@Microsoft.KeyVault(SecretUri=...)
Parameter Store refsApp ConfigurationShared config across environments
Secrets Manager refsKey VaultSecrets with rotation
.env fileApp Settings + Key VaultSplit by sensitivity

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
Also distributed in
microsoft/azure-skills

AutoGineer is not affiliated with or endorsed by Microsoft or Microsoft.

Download ZIP

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