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://mp-staging.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/spring-assessment-guide.md

Pre-Migration Assessment for Spring Boot to Azure Container Apps

Local State Assessment

IssueImpactSolution
Singleton patternsMultiple instances may run during updatesRefactor to stateless design
In-memory sessionsLost during restarts/scalingMigrate to Azure Cache for Redis
Local cachingNot shared across replicasUse Azure Cache for Redis with Spring Data Redis
File-based stateLost on restartMigrate to Azure Cosmos DB, Azure SQL, or Azure Storage

State Migration Options:

  • Azure Cache for Redis: Session data, distributed caching

  • Azure Cosmos DB: NoSQL data, document storage

  • Azure SQL/MySQL/PostgreSQL: Relational data

  • Azure Storage Blobs: Unstructured data, serialized objects

File System Usage

PatternContainer Apps Solution
Temporary filesEphemeral storage (automatic, deleted on restart)
Shared persistent dataAzure Files storage mounts
Static content servingAzure Blob Storage + Azure CDN
User uploadsAzure Blob Storage with Azure Function triggers

Platform Compatibility

Supported Java Versions

  • For Spring Boot 2.x source apps: Java 8 or 11 supported for assessment

  • For Spring Boot 3.x target apps: Java 17 or 21 required (verify with java -version)

Spring Boot Version Requirements

  • Recommended target: Spring Boot 3.x (requires Java 17+)

  • Supported source: Spring Boot 2.x on Java 8/11 → plan upgrade to Java 17+ and follow Spring Boot 3.0 Migration Guide

Spring Cloud Compatibility

External Resources Inventory

Inventory all external dependencies. See spring-dependency-patterns.md for configuration examples (databases, message brokers, caches).

Identity Providers
ProviderConfiguration
OAuth2Spring Security reference docs
Auth0Auth0 Spring Security documentation
PingFederateSpring Security SAML 2.0/OIDC docs, PingIdentity docs
Microsoft Entra IDUpdate redirect URIs to new Container Apps FQDN

Scheduled Jobs Assessment

Job TypeContainer Apps Solution
Unix cron jobsAzure Container Apps Jobs (ephemeral)
Spring Batch tasksAzure Container Apps Jobs
Quartz schedulerLong-running app (handle scale-out race conditions)
Scheduled @Scheduled methodsLong-running app (handle multiple instances)

Configuration & Secrets

Port Configuration

  • Default: 8080

  • Change via server.port or SERVER_PORT environment variable

  • Configure in Container Apps ingress settings

Secrets Checklist

  1. Inventory all secrets in application.properties/application.yml

  2. Document database passwords, API keys, connection strings

  3. Plan migration to Azure Key Vault

  4. Update app to use Key Vault references or environment variables

Certificates

  • Run keytool -list -v -keystore <path> to document SSL certificates

  • Plan migration to Azure Key Vault or Container Apps managed certificates

Deployment Architecture

Document current state:

  • Number of instances

  • CPU per instance (vCPU)

  • RAM per instance (GiB)

  • Regional distribution

  • Uptime requirements/SLA

Container Apps Limits:

  • Max 4 vCPU per container

  • Max 8 GiB RAM per container

  • Max 300 replicas per revision

Assessment Checklist

  • [ ] Identified all local state and planned migration to external storage

  • [ ] Reviewed file system usage and selected storage solution

  • [ ] Verified Java version compatibility (17+ for Spring Boot 3.x target; 8/11 for source assessment only)

  • [ ] Confirmed Spring Boot 3.x or planned upgrade

  • [ ] Inventoried databases (MySQL, PostgreSQL, MongoDB, Cosmos DB)

  • [ ] Inventoried message brokers (ActiveMQ, IBM MQ, Azure Service Bus)

  • [ ] Inventoried external caches (Redis)

  • [ ] Documented identity providers (OAuth2, SAML, Entra ID)

  • [ ] Identified scheduled jobs and selected execution model

  • [ ] Listed all configuration secrets for Key Vault migration

  • [ ] Documented SSL certificates

  • [ ] Recorded current deployment architecture (instances, CPU, RAM)

  • [ ] Reviewed logging configuration (console vs. file)

  • [ ] Identified APM tools (Application Insights, custom agents)

Complexity Guidelines

Low Complexity:

  • Stateless Spring Boot app with external database

  • No scheduled jobs or simple @Scheduled tasks

  • Standard Java version (11, 17, 21)

  • OAuth2/SAML authentication

Medium Complexity:

  • In-memory session state requiring Redis migration

  • File system writes requiring Azure Files or Blob Storage

  • Spring Boot 2.x requiring upgrade to 3.x

  • Message broker integration (ActiveMQ, Service Bus)

  • Scheduled jobs requiring Jobs configuration

High Complexity:

  • Multiple stateful components (local cache, sessions, file storage)

  • Custom JVM agents or APM integrations

  • Java 8 requiring upgrade to 11+

  • Complex scheduled jobs with coordination requirements

  • Multi-region deployment with traffic distribution

  • Custom identity provider federation

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.

Download ZIP

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