AutoGineer
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
Download ZIP

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/container-apps/fargate-to-container-apps.md

AWS Fargate to Azure Container Apps Migration

Guidance for migrating AWS Fargate (ECS) containerized workloads to Azure Container Apps.

Overview

AWS ServiceAzure EquivalentNotes
ECS FargateAzure Container AppsServerless container platform
ECRAzure Container RegistryPrivate container registry
Application Load BalancerContainer Apps IngressBuilt-in HTTPS
AWS Secrets ManagerAzure Key VaultManaged identity integration
CloudWatch LogsAzure Monitor/Log AnalyticsRequires Log Analytics workspace on environment
CloudWatch MetricsAzure Monitor MetricsAvailable without Log Analytics workspace
IAM Roles (tasks)Managed IdentityMicrosoft Entra ID integration
VPCVirtual NetworkVNet integration
Security GroupsNSG + Container Apps rulesNetwork security
Auto ScalingContainer Apps scaling rulesHTTP, CPU, memory, custom
Parameter StoreApp Configuration or Key VaultConfiguration management

Critical Differences

FeatureAWS FargateContainer AppsImpact
Max vCPU16 vCPU4 vCPU (Consumption Plan)Split CPU-intensive tasks
Max Memory120 GiB8 GiB (Consumption Plan)Redesign memory-heavy workloads
GPUAvailable (ECS)Supported (preview)Validate GPU SKU availability
Sidecar ContainersSupported (ECS)Supported (init + sidecar)Compatible pattern
Task PlacementPlacement strategies/constraintsNo node-level controlRemove placement logic
Persistent StorageEFS mountsAzure Files onlyMigrate to Azure Files or Blob
Max ReplicasService-dependent300 per revisionValidate scale requirements
NetworkingVPC + Security GroupsVNet + NSGSubnet-level isolation
Startup TimeoutNo platform limit240s defaultOptimize startup time

Migration Workflow

  1. Assess — Analyze ECS task definitions, IAM roles, VPC config → fargate-assessment-guide.md

  2. Migrate Images — Pull from ECR, push to ACR

  3. Map Services — Convert AWS dependencies to Azure equivalents

  4. Convert Config — Transform task definitions to Container Apps CLI flags

  5. Deploy — Create Container Apps environment and deploy → fargate-deployment-guide.md

  6. Validate — Health checks, scaling, monitoring

Service Dependency Mappings

AWS ServiceAzure EquivalentNotes
S3Azure Blob StorageSDK change (boto3 → azure-storage-blob)
DynamoDBAzure Cosmos DBAPI compatibility or code changes
SQSAzure Service Bus / Queue StorageSDK change
SNSAzure Event Grid / Service Bus TopicsSDK change
RDSAzure Database for PostgreSQL/MySQL/SQLConnection string + managed identity
ElastiCache (Redis)Azure Cache for RedisConnection string update
Parameter StoreAzure App Configuration / Key VaultSDK change
EventBridgeAzure Event GridSDK change required
Step FunctionsAzure Logic Apps / Durable FunctionsWorkflow redesign
KinesisAzure Event HubsSDK change required
X-RayApplication InsightsRequires SDK + connection string setup
CloudWatch LogsAzure Monitor LogsRequires Log Analytics workspace on environment

Resource Mapping

See Resource Mapping in the assessment guide for the canonical ECS-to-Container-Apps resource mapping table.

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