azure-cloud-migrate
Assess and migrate cloud workloads from AWS, GCP, and other providers to Azure services.
Works with
What it does
Supports Lambda-to-Azure Functions migration with dedicated scenario reference and best practices
Generates assessment reports mapping source services to Azure equivalents before any code conversion
Converts source code to target Azure runtime models, with output isolated in a separate <source-folder>-azure/ directory
Requires sequential phase execution: assessment first, then migration,
Installation Guide
How to use azure-cloud-migrate on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
azure-cloud-migrate
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches azure-cloud-migrate from microsoft/azure-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate azure-cloud-migrate. Access via /azure-cloud-migrate in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
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_bestpracticesandmcp_azure_mcp_documentationMCP tools - Use the latest supported runtime for the target service
- Destructive actions require
ask_user— global-rules
Migration Scenarios
| Source | Target | Reference |
|---|---|---|
| AWS Lambda | Azure Functions | lambda-to-functions.md |
No matching scenario? Use
mcp_azure_mcp_documentationandmcp_azure_mcp_get_bestpracticestools.
Output Directory
All output goes to <source-folder>-azure/ at workspace root. Never modify the source directory.
Steps
- Create
<source-folder>-azure/at workspace root - Assess — Analyze source, map services, generate report → assessment.md
- Migrate — Convert code using target programming model → code-migration.md
- 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.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort