Why Azure Migrate?
Most enterprises have a mix of on-premises workloads, legacy apps, and databases that need to move to Azure. Migration must be planned carefully to minimize downtime, avoid surprises in cost/performance, and ensure compliance.
Azure Migrate is Microsoft’s central hub for discovering, assessing, and migrating workloads into Azure.
Azure Migrate Framework
The framework is structured into three key stages:
-
Discovery
-
Inventory all workloads (servers, VMs, databases, apps).
-
Collect metadata (CPU, memory, disk usage, network dependencies).
-
Tools: Azure Migrate: Discovery & Assessment appliance.
-
Outcome: Clear view of what exists and how it’s connected.
-
-
Assessment
-
Analyze workload readiness for Azure.
-
Identify migration blockers (unsupported OS, legacy features).
-
Estimate Azure sizing and costs.
-
Classify by strategy (Rehost, Refactor, Rearchitect, Rebuild).
-
Outcome: Roadmap for each workload.
-
-
Migration
-
Execute workload moves to Azure.
-
Methods:
-
Server Migration → replicate VMs to Azure.
-
Database Migration → Azure DMS for SQL/Oracle/MySQL/PostgreSQL.
-
Web App Migration Assistant → move IIS/.NET apps to App Service.
-
-
Outcome: Workloads run in Azure, validated with testing.
-
Integration with Other Tools
-
Azure Site Recovery (ASR): for lift-and-shift VMs with minimal downtime.
-
Database Migration Service (DMS): for SQL, Oracle, open-source DBs.
-
Storage Migration Service (SMS): migrate file servers to Azure Files.
-
App Service Migration Assistant: for web apps.
Example Enterprise Scenario
A global manufacturer needs to migrate:
-
200 on-prem Windows/Linux VMs.
-
Legacy SQL databases.
-
File shares used by branch offices.
Correct design:
-
Use Azure Migrate appliance to discover workloads.
-
Run assessments for VM sizing and costs.
-
Use ASR for VM migration with near-zero downtime.
-
Use Azure DMS for database migration.
-
Use Storage Migration Service for file servers.
Confusion Buster
-
Azure Migrate vs ASR
-
Migrate = full migration framework (discovery, assessment, execution).
-
ASR = tool for VM replication/failover, used within migration execution.
-
-
Assessment vs Migration
-
Assessment = plan, cost, readiness.
-
Migration = actual execution.
-
-
Rehost vs Refactor
-
Rehost = lift-and-shift, minimal changes.
-
Refactor = minor changes to use PaaS/container options.
-
Exam Tips
-
“Which tool provides discovery & assessment of on-prem workloads?” → Azure Migrate.
-
“Which service migrates SQL Server databases to Azure?” → Azure DMS.
-
“Which migration strategy is lift-and-shift?” → Rehost.
-
“Which tool is best for moving file servers to Azure Files?” → Storage Migration Service.
What to Expect in the Exam
-
Direct Q: “Which Azure service is the central hub for migration planning?” → Azure Migrate.
-
Scenario Q: “Company wants to discover all workloads and dependencies before migration.” → Azure Migrate Discovery.
-
Scenario Q: “Which service replicates VMs to Azure with minimal downtime?” → ASR.
-
Trick Q: “Database Migration Service can discover VM dependencies.” → False (only Azure Migrate does).