PaperclipOrg
Claude Agent Skill · by Microsoft

Azure Cloud Migrate

Takes your existing AWS Lambda functions (or other cloud workloads) and converts them to Azure Functions with proper assessment and code migration. Generates a

Install
Terminal · npx
$npx skills add https://github.com/microsoft/azure-skills --skill azure-cloud-migrate
Works with Paperclip

How Azure Cloud Migrate fits into a Paperclip company.

Azure Cloud Migrate drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md44 lines
Expand
---name: azure-cloud-migratedescription: "Assess and migrate cross-cloud workloads to Azure with migration reports and code conversion. Supports AWS Lambda→Functions and GCP Cloud Run→Container Apps. WHEN: migrate Lambda to Azure Functions, migrate AWS to Azure, Lambda migration assessment, convert serverless to Azure, migration readiness report, migrate from AWS, migrate from GCP, Cloud Run to Container Apps, Cloud Run migration assessment."license: MITmetadata:  author: Microsoft  version: "1.0.2"--- # Azure Cloud Migrate > This skill handles **assessment and code migration** of existing cloud workloads to Azure. ## Rules 1. Follow phases sequentially — do not skip2. Generate assessment before any code migration3. Load the scenario reference and follow its rules4. Use `mcp_azure_mcp_get_bestpractices` and `mcp_azure_mcp_documentation` MCP tools5. Use the latest supported runtime for the target service6. Destructive actions require `ask_user` — [global-rules](references/services/functions/global-rules.md) ## Migration Scenarios | Source | Target | Reference ||--------|--------|-----------|| AWS Lambda | Azure Functions | [lambda-to-functions.md](references/services/functions/lambda-to-functions.md) ([assessment](references/services/functions/assessment.md), [code-migration](references/services/functions/code-migration.md)) || GCP Cloud Run | Azure Container Apps | [cloudrun-to-container-apps.md](references/services/container-apps/cloudrun-to-container-apps.md) | > No matching scenario? Use `mcp_azure_mcp_documentation` and `mcp_azure_mcp_get_bestpractices` tools. ## Output Directory All output goes to `<source-folder>-azure/` at workspace root. Never modify the source directory. ## Steps 1. **Create** `<source-folder>-azure/` at workspace root2. **Assess** — Analyze source, map services, generate report using scenario-specific assessment guide3. **Migrate** — Convert code/config using scenario-specific migration guide4. **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](references/workflow-details.md).