# Migrate Cloud Workloads to Azure

Cloud migrations require careful service mapping, code changes, and deployment planning. This skill guides assessment and migration work for Azure Functions, App Service, and Container Apps.

## Install

```bash
npx skillstore add microsoft/azure-cloud-migrate
```

## Metadata

- Status: approved
- Slug: microsoft-azure-cloud-migrate
- Version: 0.0.0-placeholder
- Author version: 0.0.0-placeholder
- Skillstore revision: r1
- Version status: valid
- Tree hash: fd334b4c8f2a88f6fd96bd57d60c5050e6e4b5802427229796f709bdc97fec3d
- Author: microsoft
- GitHub username: microsoft
- License: MIT
- Repository: https://github.com/microsoft/github-copilot-for-azure/tree/main/plugin/skills/azure-cloud-migrate/
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: env\_access, network, filesystem, external\_commands, scripts
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/microsoft-azure-cloud-migrate
- Manifest: https://skillstore.pages.dev/api/skills/microsoft-azure-cloud-migrate/manifest

## Capabilities

- Generates migration assessment reports before code changes.
- Maps AWS Lambda triggers to Azure Functions triggers and bindings.
- Maps Heroku, Elastic Beanstalk, and App Engine apps to Azure App Service.
- Maps Kubernetes, Fargate, Cloud Run, and Spring workloads to Azure Container Apps.
- Provides runtime-specific Azure Functions examples for JavaScript, TypeScript, Python, C\#, Java, and PowerShell.
- Prepares handoff context for Azure infrastructure, validation, and deployment steps.

## Use Cases

- Assess Lambda migration readiness: Inventory Lambda functions, triggers, dependencies, and IAM mappings before moving to Azure Functions.
- Plan web app migration: Map Heroku, Elastic Beanstalk, or App Engine applications to Azure App Service with configuration and identity guidance.
- Move container workloads: Evaluate Kubernetes, Fargate, Cloud Run, or Spring workloads for Azure Container Apps compatibility and deployment planning.

## Prompt Templates

### Assess my source workload

```
Assess this project for Azure migration. Identify the source platform, required Azure target services, blockers, and the next files you need from me.
```

### Create a migration report

```
Generate the required migration assessment report for this workload. Include service mapping, dependencies, security mapping, effort, risks, and recommended next steps.
```

### Convert service configuration

```
Convert this source platform configuration to the closest Azure target configuration. Keep the original app unchanged and write all output to the Azure migration folder.
```

### Design a phased Azure migration

```
Build a phased migration plan from assessment through deployment. Include identity, secrets, networking, observability, rollback, and validation steps for each phase.
```

## Limitations

- It provides guidance and generated migration artifacts, not guaranteed production readiness.
- It requires accurate source project files and cloud configuration from the user.
- It cannot validate cloud costs, quotas, or live permissions without environment access.
- Deployment commands can affect real cloud resources and must be reviewed before use.

## Best Practices

- Run the assessment phase and review the report before requesting code migration.
- Review every generated cloud command before execution in a live subscription or project.
- Use managed identity and Key Vault references instead of copying secrets into files or command arguments.

## Anti Patterns

- Skipping the assessment report and moving directly to deployment commands.
- Running generated migration commands against production without review and backups.
- Storing decoded secrets, connection strings, or cloud keys in the workspace.

## Security Audit

- Audited at: 2026-07-23T17:55:12.676\+00:00
- Summary: Most of the 400 presented findings are documentation false positives involving links, code fences, managed identity examples, and visible migration commands. Confirmed risks involve shared cloud keys, decoded secret transfer through CLI arguments, and local secret materialization. The 30 omitted static matches require manual review before publication. Static review was capped at 400/430 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

## Stats

- Views: 328
- Downloads: 9
- Favorites: 0
- Popularity score: 0