How does it handle networking and service discovery changes?

The skill audits your application code for internal hostnames (like Kubernetes DNS) and flags them for replacement with environment-variable-driven URL injection to ensure they work in Azure Container Apps.

Can it migrate Kubernetes workloads to Azure?

Yes, it specifically handles the migration of Kubernetes configurations (from GKE, EKS, or self-hosted) into Azure Container Apps (ACA) configurations.

What source cloud providers are supported?

This skill supports migrating workloads from AWS (Lambda, ECS/Fargate, EKS) and GCP (Cloud Run, GKE) to their respective Azure equivalents.

Does this skill modify my existing project files?

No, it is designed to be non-destructive. All assessments and migrated code are placed in a new directory named after your workspace with an '-azure' suffix.

What are the primary target services on Azure?

The skill primarily targets Azure Functions for serverless workloads and Azure Container Apps (ACA) for all containerized scenarios.

Azure Cloud Migration

Name: Azure Cloud Migration
Author: microsoft

bymicrosoft

•

797

•

Infraestructura en la Nube

Automates the assessment and migration of serverless and containerized workloads from AWS and GCP to Microsoft Azure.

This skill streamlines the transition of cross-cloud workloads to Azure by providing structured assessments and automated code conversion. It specializes in migrating AWS Lambda to Azure Functions, and AWS Fargate, Kubernetes (EKS/GKE), or GCP Cloud Run to Azure Container Apps. By auditing service discovery, updating runtimes, and generating detailed readiness reports, it ensures a smooth migration path while keeping source code safe in an isolated workspace.

Características Principales

01797 GitHub stars

02Code conversion from AWS Lambda to Azure Functions with runtime updates

03Automated readiness reports for AWS and GCP workload assessments

04Safe workspace isolation that never modifies original source directories

05Service discovery auditing to identify and fix hardcoded DNS/port dependencies

06Container migration for ECS, Kubernetes, and Cloud Run to Azure Container Apps

Casos de Uso

01Moving containerized microservices from Google Cloud Run or AWS Fargate to Azure Container Apps

02Migrating AWS Lambda serverless functions to Azure Functions with full code conversion

03Generating a technical migration assessment to identify gaps before moving from Kubernetes to Azure

Características Principales

01797 GitHub stars

02Code conversion from AWS Lambda to Azure Functions with runtime updates

03Automated readiness reports for AWS and GCP workload assessments

04Safe workspace isolation that never modifies original source directories

05Service discovery auditing to identify and fix hardcoded DNS/port dependencies

06Container migration for ECS, Kubernetes, and Cloud Run to Azure Container Apps

Casos de Uso

01Moving containerized microservices from Google Cloud Run or AWS Fargate to Azure Container Apps

02Migrating AWS Lambda serverless functions to Azure Functions with full code conversion

03Generating a technical migration assessment to identify gaps before moving from Kubernetes to Azure