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

Kubernetes to Azure Container Apps Migration

Detailed guidance for migrating containerized workloads from Kubernetes (GKE, EKS, self-hosted) to Azure Container Apps.

Overview

Kubernetes Source	Azure Equivalent
GKE / EKS / Self-hosted Kubernetes	Azure Container Apps
Docker Registry / GCR / ECR	Azure Container Registry (ACR)
ConfigMap	Container Apps Environment Variables / Secrets
Secret	Azure Key Vault + Key Vault references
Ingress	Container Apps Ingress
Service (LoadBalancer/ClusterIP)	Container Apps Ingress (external/internal)
HPA (Horizontal Pod Autoscaler)	Container Apps Scaling Rules
Namespace	Container Apps Environment
Persistent Volume	Azure Files / Blob Storage (via volume mounts)

Resource Mapping

Kubernetes Resource	Container Apps Equivalent	Notes
Deployment	Container App	One deployment → one Container App
Service (type: LoadBalancer)	Ingress (external: true)	Public endpoint
Service (type: ClusterIP)	Ingress (external: false)	Internal only
ConfigMap	`env` with plaintext values	Use Key Vault for sensitive data
Secret	`secretRef` + Key Vault	Managed identity for access
HPA	`scale` rules (http, cpu, memory, custom)	HTTP concurrency, queue depth, etc.
Ingress	Ingress configuration	Automatic HTTPS, custom domains
Liveness/Readiness Probe	Health probes	HTTP, TCP, or startup probes

Configuration Mapping

Kubernetes Manifest	Container Apps CLI/Bicep	Example
`replicas: 3`	`--min-replicas 3 --max-replicas 3`	Static scaling
`resources.requests.cpu`	`--cpu 0.5`	CPU cores (0.25-4.0)
`resources.requests.memory`	`--memory 1Gi`	Memory (0.5Gi-8Gi)
`image: gcr.io/my-registry/app:v1`	`--image myacr.azurecr.io/app:v1`	After ACR import
`env: - name: KEY, value: val`	`--env-vars KEY=val`	Environment variables
`env: - name: SECRET, valueFrom: secretKeyRef`	`--secrets SECRET=keyvaultref:...`	Key Vault reference
`ports: - containerPort: 8080`	`--target-port 8080`	Container port
`livenessProbe.httpGet.path: /health`	YAML/Bicep `probes` config	Health probes not configurable via CLI

Migration Workflow

Follow these phases sequentially:

Phase 1: Export Kubernetes Resources

Use kubectl get deployment,service,configmap,secret -o yaml to export manifests
Document current configuration (replicas, resources, env vars)
Identify external dependencies (databases, message queues, storage)

Phase 2: Assess Compatibility

Verify workloads are stateless (Container Apps doesn't support StatefulSets)
Check for unsupported features (DaemonSets, custom CRDs, Operators)
Plan Jobs/CronJobs migration to Container Apps Jobs
Identify ConfigMaps/Secrets requiring Key Vault migration
Review persistent storage needs (migrate to Azure Files/Blob)

See assessment-guide.md for detailed checklist.

Phase 3: Migrate Container Images

Create Azure Container Registry: az acr create
Import images from GCR/ECR/Docker Hub: az acr import
Or rebuild and push: docker build → docker push
Enable managed identity access: az containerapp registry set

Phase 4: Deploy to Container Apps

Create Container Apps Environment
Deploy Container Apps with converted configuration
Configure ingress, scaling rules, and health probes
Set up Key Vault references for secrets

See deployment-guide.md for step-by-step deployment.

Phase 5: Verify and Test

Test external endpoints (HTTP/HTTPS ingress)
Test internal service-to-service communication
Verify environment variables and secrets
Validate scaling behavior
Check health probes and logs

Unsupported Features

Container Apps does NOT support:

StatefulSets (use Azure Database services instead)
DaemonSets (not applicable in serverless model)
Kubernetes PV/PVC objects (use Azure Files/Blob Storage via Container Apps volume mounts instead)
Custom CNI networking
Node affinity / pod affinity

For batch and scheduled workloads, migrate Kubernetes Jobs / CronJobs to Azure Container Apps Jobs instead of long-running Container Apps.

For unsupported Kubernetes platform features, consider Azure Kubernetes Service (AKS) instead.

Best Practices

Use Managed Identity for ACR and Key Vault access (no passwords)
Store secrets in Key Vault, reference them in Container Apps
Use Container Apps Environments to group related microservices
Enable Dapr for service-to-service communication, state management, pub/sub
Configure health probes to ensure reliability
Use scaling rules based on HTTP concurrency or custom metrics
Never modify source Kubernetes cluster during migration

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

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

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

Kubernetes to Azure Container Apps Migration

Overview

Resource Mapping

Configuration Mapping

Migration Workflow

Phase 1: Export Kubernetes Resources

Phase 2: Assess Compatibility

Phase 3: Migrate Container Images

Phase 4: Deploy to Container Apps

Phase 5: Verify and Test

Unsupported Features

Best Practices

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