$ loading_
Assess and migrate cross-cloud workloads to Azure with reports and code conversion.
This appears to be a prompt-oriented skill for Azure migration workflow orchestration, with no declared secrets, remote endpoints, or direct execution privileges of its own. Overall risk is low, but practical safety still depends on the Azure MCP tools it invokes and the boundaries of the runtime environment.
The material explicitly states that no keys or environment variables are required, and the README does not ask for tokens, cloud credentials, or other sensitive authentication data. For this skill itself, credential exposure and abuse risk appears low.
The objective inputs state that there are no remote endpoint hosts, and the skill itself does not declare sending data to external services. While it references `mcp_azure_mcp_get_azure_bestpractices` and `mcp_azure_mcp_documentation`, the current material does not show any additional or unknown data egress.
The system marks it as `prompt-only`, indicating that this is a rule/instruction skill rather than a tool that directly spawns processes or executes commands locally. The README mentions deployment, image pushes, and code migration workflows, but it does not show that the skill itself has permission to perform those actions.
The README instructs creating `<workspace-root-basename>-azure/` at the workspace root and scanning application source code for assessment, indicating intended access to read workspace code and write migration outputs. This is a normal capability for skill/MCP scenarios, but the host should expose only the necessary project directory to avoid unintended access to broader files.
Positive signals include a GitHub-hosted open-source repository under `microsoft/GitHub-Copilot-for-Azure`, which improves auditability. However, the license is unspecified, community adoption is 0 stars, maintenance status is unknown, and the provided material is truncated, so supply-chain trust is somewhat positive but still warrants repository and update review before adoption.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "azure-cloud-migrate" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/GitHub-Copilot-for-Azure/main/plugin/skills/azure-cloud-migrate/SKILL.md 2. Save it as ~/.claude/skills/azure-cloud-migrate/SKILL.md 3. Reload skills and tell me it's ready
Assess the feasibility of migrating our existing AWS Lambda project to Azure Functions. Provide a migration report, dependency analysis, configuration differences, and code changes needed.
A migration report with risks, effort estimates, resource mapping, and code conversion recommendations.
Analyze the steps to migrate this Heroku web app to Azure App Service. Explain environment variables, build process, deployment flow, and possible compatibility issues.
A migration checklist with detailed mapping for configuration, deployment, and compatibility.
Evaluate a plan to migrate our current Kubernetes services to Azure Container Apps. List service mapping, scaling strategy, network requirements, and the recommended migration order.
An implementation-ready migration plan covering architecture mapping, operational changes, and phased rollout recommendations.
This skill handles assessment and code migration of existing cloud workloads to Azure.
mcp_azure_mcp_get_azure_bestpractices and mcp_azure_mcp_documentation MCP toolsask_user — functions global-rules | app-service global-ruleshttp://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| 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.
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.
<workspace-root-basename>-azure/ at workspace rootTrack progress in migration-status.md — see workflow-details.md.
Set up Entra ID app registration, OAuth, permissions, and MSAL integration.
Set up Azure Application Insights telemetry for web apps with best practices.
Troubleshoot Azure Event Hubs and Service Bus SDK connection and messaging issues.
Find, list, and inspect Azure resources across subscriptions and resource groups.
Deploy, evaluate, fine-tune, and optimize Microsoft Foundry agents and models.
Deploy prepared Azure apps with built-in recovery for common release errors.
Prepare Azure apps for deployment with infra, configs, and container setup.
Analyze cloud architectures and generate recommendations, diagrams, and ADRs across major clouds.
Manage Azure storage, virtual machines, and app services more efficiently.
Give AI real-time Azure infrastructure access for ops checks, policy validation, and Terraform analysis.
Assess AKS Automatic readiness and generate fixes for migration blockers.
Assess Azure security, analyze attack paths, and generate compliance audit reports.