Skills

Chapter 10 of 37

Azure Cloud Migrate

Assess and migrate cross-cloud workloads to Azure with reports and code conversion.

1 minute · 272 words · 4 sections

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 (opens in a new tab) | app-service global-rules (opens in a new tab)
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 (opens in a new tab)
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 (opens in a new tab) (assessment (opens in a new tab), code-migration (opens in a new tab))
AWS Elastic Beanstalk	Azure App Service	beanstalk-to-app-service.md (opens in a new tab)
Heroku	Azure App Service	heroku-to-app-service.md (opens in a new tab)
Google App Engine	Azure App Service	app-engine-to-app-service.md (opens in a new tab)
AWS Fargate (ECS)	Azure Container Apps	fargate-to-container-apps.md (opens in a new tab) (assessment (opens in a new tab), deployment (opens in a new tab))
Kubernetes (GKE/EKS/Self-hosted)	Azure Container Apps	k8s-to-container-apps.md (opens in a new tab)
GCP Cloud Run	Azure Container Apps	cloudrun-to-container-apps.md (opens in a new tab)
Spring Boot (Azure Spring Apps/VMs)	Azure Container Apps	spring-apps-to-aca.md (opens in a new tab)

No matching scenario? Use mcp_azure_mcp_documentation and mcp_azure_mcp_get_azure_bestpractices tools.

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 (opens in a new tab) | app-service assessment (opens in a new tab)
Migrate — Convert code/config using the scenario-specific migration guide → functions code-migration (opens in a new tab) | app-service code-migration (opens in a new tab)
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 (opens in a new tab).

Install this repository

$ npx skills add microsoft/azure-skills

» /plugin marketplace add microsoft/azure-skills

Skills install per repository, not per chapter — the CLI has no documented per-skill form, so we do not print one.

About this skill

Trigger

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 verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Licence: MIT
Also published for: GitHub — collapsed into this chapter because the copies are the same skill.
Source: skills/azure-cloud-migrate/SKILL.md

Colophon for this issue

Colophon

How this issue was made

Source

github.com/microsoft/azure-skills, branch main, last pushed 10 August 2026.

Licence

MIT — the text of every chapter is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

37 chapters found by walking the repository tree for SKILL.md, not by matching a directory convention. 6 distinct layouts observed: skills/*/SKILL.md, skills/azure-app-onboard/*/SKILL.md, skills/azure-kubernetes/*/SKILL.md, skills/microsoft-foundry/*/SKILL.md, skills/microsoft-foundry/models/deploy-model/*/SKILL.md, skills/microsoft-foundry/models/*/SKILL.md.

Duplicates collapsed

37 mirror copies folded into their canonical chapter — republished for GitHub. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.

Issue colours

Resolved from a curated brand profile — hue 251°, chroma 0.167. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this chapter so the document has one h1 and no skipped levels:

Removed “Azure Cloud Migrate”, a leading h1 that duplicated the chapter title.

Spec compliance

6 editorial notes across 3 of 37 chapters. They are printed in the margin of each chapter rather than as errors here.

Deploy — 2 notes
Prepare — 2 notes
Scaffold — 2 notes

Images

Images inside a chapter come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Microsoft, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /microsoft/azure-skills.md, and each chapter at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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 (opens in a new tab) | app-service global-rules (opens in a new tab)
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 (opens in a new tab)
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 (opens in a new tab) (assessment (opens in a new tab), code-migration (opens in a new tab))
AWS Elastic Beanstalk	Azure App Service	beanstalk-to-app-service.md (opens in a new tab)
Heroku	Azure App Service	heroku-to-app-service.md (opens in a new tab)
Google App Engine	Azure App Service	app-engine-to-app-service.md (opens in a new tab)
AWS Fargate (ECS)	Azure Container Apps	fargate-to-container-apps.md (opens in a new tab) (assessment (opens in a new tab), deployment (opens in a new tab))
Kubernetes (GKE/EKS/Self-hosted)	Azure Container Apps	k8s-to-container-apps.md (opens in a new tab)
GCP Cloud Run	Azure Container Apps	cloudrun-to-container-apps.md (opens in a new tab)
Spring Boot (Azure Spring Apps/VMs)	Azure Container Apps	spring-apps-to-aca.md (opens in a new tab)

No matching scenario? Use mcp_azure_mcp_documentation and mcp_azure_mcp_get_azure_bestpractices tools.

Output 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 (opens in a new tab) | app-service assessment (opens in a new tab)
Migrate — Convert code/config using the scenario-specific migration guide → functions code-migration (opens in a new tab) | app-service code-migration (opens in a new tab)
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 (opens in a new tab).

Azure Cloud Migrate

Rules

Migration Scenarios

Output Directory

Steps

About this skill

Trigger

Colophon

Azure Cloud Migrate

Rules

Migration Scenarios

Output Directory

Steps

Appendix 10.1–10.30

ReferencesMarkdown · 30 files

About this skill

Trigger

Colophon

Appendix 10.1–10.30

ReferencesMarkdown · 30 files