azure-cloud-migrate

Assess and migrate AWS Lambda workloads to Azure Functions with structured reports.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/stephschofield/beth --skill azure-cloud-migrate-stephschofield
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-cloud-migrate
Source: https://github.com/stephschofield/beth/tree/main/.github/skills/azure-cloud-migrate
Command: npx skills add https://github.com/stephschofield/beth --skill azure-cloud-migrate-stephschofield

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Moving serverless workloads from AWS, GCP, or other cloud providers to Azure requires manual service mapping, runtime conversion, and risk assessment. This Skill automates the assessment and code migration phases so teams can move Lambda functions to Azure Functions without reverse-engineering every trigger, binding, and dependency by hand. ## Core Features & Use Cases - Migration Assessment Reports: Generates a standardized 13-section assessment report covering function inventory, service mapping, dependencies, IAM, monitoring, and CI/CD equivalents. - Guided Code Migration: Converts Lambda handlers to the Azure Functions v4 (JavaScript/TypeScript) or v2 (Python) programming model using bindings instead of SDKs, with per-runtime reference guides for C#, Java, and PowerShell. - Infrastructure Pitfall Coverage: Documents critical Flex Consumption requirements such as always-ready instances, Event Grid Bicep deployment, and UAMI credential patterns. - Use Case: A team with a SAM-based AWS Lambda image-processing pipeline uses this Skill to produce a migration readiness report, then converts each function to Azure Functions with blob triggers, managed identity auth, and Computer Vision replacing Rekognition. ## Quick Start Ask the agent to assess the AWS Lambda project in this workspace and migrate it to Azure Functions using the azure-cloud-migrate skill.

Frequently Asked Questions about azure-cloud-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate AWS Lambda functions to Azure Functions?▼

Run the assessment phase first to map functions, triggers, and dependencies, then the code migration phase converts handlers to the Azure Functions v4 (Node.js) or v2 (Python) programming model. Output goes to a new <source-folder>-azure directory without modifying the original code.

What AWS services map to Azure equivalents during migration?▼

Lambda maps to Azure Functions, S3 to Blob Storage, SQS to Service Bus or Storage Queues, SNS and EventBridge to Event Grid, DynamoDB to Cosmos DB, CloudWatch to Application Insights, and IAM roles to Managed Identity with RBAC.

Does the migration support languages other than JavaScript and Python?▼

Yes. Runtime reference guides cover JavaScript v4, TypeScript v4, Python v2, C# isolated worker, Java, and PowerShell. JavaScript and Python use inline bindings, while C# and Java generate binding metadata from attributes or annotations at build time.

Why does my Azure blob trigger with EventGrid source fail silently on Flex Consumption?▼

Three infrastructure requirements are commonly missed: always-ready instances for the blob trigger group, the AzureWebJobsStorage__queueServiceUri app setting for poison-message tracking, and creating the Event Grid subscription via Bicep rather than CLI, whose webhook validation times out.

Can I use connection strings or API keys for Azure services after migration?▼

The skill enforces identity-first authentication: storage uses managed identity with service URIs, Cognitive Services sets disableLocalAuth with UAMI and RBAC, and DefaultAzureCredential must receive the UAMI client ID explicitly via AZURE_CLIENT_ID.