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/downloadUnzip 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_bestpracticesandmcp_azure_mcp_documentationMCP toolsUse the latest supported runtime for the target service
Destructive actions require
ask_user— functions global-rules | app-service global-rulesReport 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_documentationandmcp_azure_mcp_get_azure_bestpracticestools.
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 rootAssess — 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/functions/runtimes/javascript.md
JavaScript (Node.js) — Azure Functions v4 Triggers & Bindings
Model: JavaScript v4 programming model. NO
function.jsonfiles. Import:const { app, input, output } = require('@azure/functions');
Lambda Migration Rules
Shared rules (bindings over SDKs, latest runtime, identity-first auth) → global-rules.md
JS-specific:
Use
extraInputs/extraOutputswith binding path expressions (e.g.,{queueTrigger}) for dynamic blob I/OAccess metadata via
context.triggerMetadatapackage.json:"@azure/functions": "^4.0.0"
Correct Migration Pattern
const { app, input, output } = require('@azure/functions');
// Use bindings for blob I/O instead of BlobServiceClient SDK
const blobInput = input.storageBlob({
path: 'source-container/{queueTrigger}',
connection: 'AzureWebJobsStorage'
});
const blobOutput = output.storageBlob({
path: 'destination-container/{queueTrigger}',
connection: 'AzureWebJobsStorage'
});
app.storageQueue('processImage', {
queueName: 'image-processing',
connection: 'AzureWebJobsStorage',
extraInputs: [blobInput],
extraOutputs: [blobOutput],
handler: async (queueItem, context) => {
const sourceBlob = context.extraInputs.get(blobInput);
context.log(`Processing blob: ${queueItem}`);
// Process the blob...
context.extraOutputs.set(blobOutput, processedBuffer);
}
});❌ Do NOT use legacy v1-v3
module.exports— always useapp.*()registration.
HTTP Trigger
app.http('httpFunction', {
methods: ['GET', 'POST'],
authLevel: 'anonymous',
handler: async (request, context) => {
const name = request.query.get('name') || (await request.text());
return { body: `Hello, ${name}!` };
}
});Blob Storage
// Trigger (use EventGrid source for reliability)
app.storageBlob('blobTrigger', {
path: 'samples-workitems/{name}',
connection: 'AzureWebJobsStorage',
source: 'EventGrid',
handler: async (blob, context) => {
context.log(`Blob: ${context.triggerMetadata.name}, Size: ${blob.length}`);
}
});
// Input binding
const blobInput = input.storageBlob({
path: 'samples-workitems/{queueTrigger}',
connection: 'AzureWebJobsStorage'
});
// Output binding
const blobOutput = output.storageBlob({
path: 'samples-output/{name}-out',
connection: 'AzureWebJobsStorage'
});⚠️ Flex Consumption + EventGrid Source Requirements: When using
source: 'EventGrid'on a Flex Consumption plan, three infrastructure requirements MUST be met or the trigger will silently fail:
Always-ready instances: Configure
alwaysReady: [{ name: 'blob', instanceCount: 1 }]in Bicep. Without this, the trigger group never starts and the Event Grid webhook endpoint is never registered.Queue endpoint: Set
AzureWebJobsStorage__queueServiceUriin app settings. The blob extension uses queues internally for poison-message tracking with EventGrid source, even though you're not using a queue trigger.Event Grid subscription via Bicep/ARM: Do NOT create event subscriptions via CLI — webhook validation times out on Flex Consumption. Deploy as a Bicep resource using
listKeys()to obtain theblobs_extensionsystem key.See lambda-to-functions.md for full Bicep patterns.
Using Azure AI Services with UAMI
When calling Azure AI services (Computer Vision, etc.) from a function, use DefaultAzureCredential with explicit UAMI client ID:
const { DefaultAzureCredential } = require('@azure/identity');
const createClient = require('@azure-rest/ai-vision-image-analysis').default;
const credential = new DefaultAzureCredential({
managedIdentityClientId: process.env.AZURE_CLIENT_ID // Required for UAMI
});
const client = createClient(process.env.COMPUTER_VISION_ENDPOINT, credential);
const result = await client.path('/imageanalysis:analyze').post({
body: { url: blobUrl },
queryParameters: { features: ['People'] } // Use 'People' for face detection
});Note:
@azure-rest/ai-vision-image-analysisis still in beta. Pin explicitly:"1.0.0-beta.3"— the^1.0.0semver range does NOT resolve.
Queue Storage
// Trigger
app.storageQueue('queueTrigger', {
queueName: 'myqueue-items',
connection: 'AzureWebJobsStorage',
handler: async (queueItem, context) => {
context.log('Queue item:', queueItem);
}
});
// Output
const queueOutput = output.storageQueue({
queueName: 'outqueue',
connection: 'AzureWebJobsStorage'
});Timer
app.timer('timerFunction', {
schedule: '0 */5 * * * *', // Every 5 minutes (NCRONTAB)
handler: async (myTimer, context) => {
context.log('Timer fired at:', myTimer.scheduleStatus.last);
}
});Event Grid
// Trigger
app.eventGrid('eventGridTrigger', {
handler: async (event, context) => {
context.log('Event:', event.subject, event.eventType);
}
});
// Output
const eventGridOutput = output.eventGrid({
topicEndpointUri: 'MyEventGridTopicUriSetting',
topicKeySetting: 'MyEventGridTopicKeySetting'
});Cosmos DB
// Trigger (Change Feed)
app.cosmosDB('cosmosDBTrigger', {
connectionStringSetting: 'CosmosDBConnection',
databaseName: 'mydb',
containerName: 'mycontainer',
createLeaseContainerIfNotExists: true,
handler: async (documents, context) => {
documents.forEach(doc => context.log('Changed doc:', doc.id));
}
});
// Input
const cosmosInput = input.cosmosDB({
connectionStringSetting: 'CosmosDBConnection',
databaseName: 'mydb',
containerName: 'mycontainer',
id: '{id}',
partitionKey: '{partitionKey}'
});
// Output
const cosmosOutput = output.cosmosDB({
connectionStringSetting: 'CosmosDBConnection',
databaseName: 'mydb',
containerName: 'mycontainer'
});Service Bus
// Queue Trigger
app.serviceBusQueue('sbQueueTrigger', {
queueName: 'myqueue',
connection: 'ServiceBusConnection',
handler: async (message, context) => {
context.log('Message:', message);
}
});
// Topic Trigger
app.serviceBusTopic('sbTopicTrigger', {
topicName: 'mytopic',
subscriptionName: 'mysubscription',
connection: 'ServiceBusConnection',
handler: async (message, context) => {
context.log('Topic message:', message);
}
});
// Output
const sbOutput = output.serviceBusQueue({
queueName: 'outqueue',
connection: 'ServiceBusConnection'
});Event Hubs
// Trigger
app.eventHub('eventHubTrigger', {
eventHubName: 'myeventhub',
connection: 'EventHubConnection',
cardinality: 'many',
handler: async (events, context) => {
events.forEach(event => context.log('Event:', event));
}
});
// Output
const ehOutput = output.eventHub({
eventHubName: 'outeventhub',
connection: 'EventHubConnection'
});Table Storage
// Input
const tableInput = input.table({
tableName: 'mytable',
partitionKey: '{partitionKey}',
rowKey: '{rowKey}',
connection: 'AzureWebJobsStorage'
});
// Output
const tableOutput = output.table({
tableName: 'mytable',
connection: 'AzureWebJobsStorage'
});SQL
// Trigger
app.generic('sqlTrigger', {
trigger: { type: 'sqlTrigger', tableName: 'dbo.MyTable', connectionStringSetting: 'SqlConnection' },
handler: async (changes, context) => {
changes.forEach(change => context.log('Change:', change));
}
});
// Input
const sqlInput = input.sql({
commandText: 'SELECT * FROM dbo.MyTable WHERE Id = @Id',
commandType: 'Text',
parameters: '@Id={id}',
connectionStringSetting: 'SqlConnection'
});
// Output
const sqlOutput = output.sql({
commandText: 'dbo.MyTable',
connectionStringSetting: 'SqlConnection'
});SignalR
// Output
const signalROutput = output.generic({
type: 'signalR',
hubName: 'myhub',
connectionStringSetting: 'AzureSignalRConnectionString'
});SendGrid
const sendGridOutput = output.generic({
type: 'sendGrid',
apiKey: 'SendGridApiKey',
from: '[email protected]',
to: '{email}'
});Using Bindings with Functions
// Combine trigger with input/output bindings
app.http('processItem', {
methods: ['POST'],
extraInputs: [cosmosInput],
extraOutputs: [queueOutput],
handler: async (request, context) => {
const doc = context.extraInputs.get(cosmosInput);
context.extraOutputs.set(queueOutput, JSON.stringify(doc));
return { body: 'Processed' };
}
});Full reference: Azure Functions JavaScript developer guide
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
- 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