Why Workload-Specific Migration?
Not all workloads migrate the same way. VMs, databases, web apps, and storage each have different dependencies, downtime risks, and tooling. Choosing the right approach for each ensures smooth migration with minimal disruption.
1. Virtual Machines (VMs)
Migration Tools:
-
Azure Migrate: Server Migration → replicates VMware/Hyper-V VMs into Azure.
-
Azure Site Recovery (ASR) → used for lift-and-shift with minimal downtime.
Design Considerations:
-
Assess OS compatibility (Windows/Linux support).
-
Place VMs in Availability Sets/Zones post-migration for HA.
-
Use Reserved Instances for cost optimization.
Example: Rehost a payroll app running on Windows Server 2012 → Azure VM using ASR.
2. Databases
Migration Tools:
-
Azure Database Migration Service (DMS).
-
SQL Data Sync or Geo-replication for minimal downtime.
Target Options:
-
SQL on VM → IaaS (legacy, full control).
-
Azure SQL Database → PaaS.
-
Azure SQL Managed Instance → compatibility for legacy SQL features.
-
PostgreSQL/MySQL → Azure Database for PostgreSQL/MySQL.
Design Considerations:
-
Downtime tolerance → decide between offline vs online migration.
-
Compliance → may require customer-managed keys or specific regions.
Example: Refactor SQL app into Azure SQL Managed Instance with minimal code change.
3. Web Apps
Migration Tools:
-
App Service Migration Assistant → moves IIS/.NET web apps to App Service.
-
Containers → repackage apps into ACR (Azure Container Registry) + AKS.
Design Considerations:
-
SSL/TLS → integrate with Key Vault.
-
Scaling → enable autoscaling for unpredictable traffic.
-
Authentication → Entra ID (Azure AD) integration for SSO.
Example: Move customer portal from IIS on-prem → Azure App Service with Entra ID SSO.
4. Storage & File Servers
Migration Tools:
-
Azure Storage Migration Service (SMS).
-
AzCopy or Azure Data Box (for bulk transfer).
Target Options:
-
File servers → Azure Files.
-
Archive storage → Blob Cool/Archive tiers.
-
Large datasets → Azure Data Lake.
Design Considerations:
-
Map access control → integrate with Entra ID (AD DS for Azure Files).
-
Compliance → data residency and encryption (AES-256, CMK).
-
Bandwidth → large migrations may need Data Box (physical transfer).
Example: Move on-prem HR file shares → Azure Files with hybrid access via File Sync.
Example Enterprise Migration Plan
A manufacturing company requires:
-
Migrate 150 VMware VMs.
-
SQL and Oracle databases.
-
IIS-based HR portal.
-
File servers storing CAD drawings.
Correct design:
-
Use Azure Migrate + ASR for VMs.
-
Use DMS for SQL/Oracle DBs → Azure SQL MI.
-
Use App Service Migration Assistant for HR portal.
-
Use Storage Migration Service + File Sync for CAD shares.
Confusion Buster
-
Azure Migrate vs ASR
-
Azure Migrate = framework & toolset.
-
ASR = replication engine (used inside migration).
-
-
SQL DB vs SQL Managed Instance
-
DB = modern, lightweight apps.
-
MI = legacy workloads needing SQL Agent, cross-DB queries.
-
-
App Service vs AKS
-
App Service = single app migration.
-
AKS = microservices/multiple containers.
-
-
AzCopy vs Data Box
-
AzCopy = online migration for small/medium datasets.
-
Data Box = offline, petabyte-scale migration.
-
Exam Tips
-
“Which service migrates VMware VMs into Azure?” → Azure Migrate (Server Migration).
-
“Which tool moves SQL databases to Azure with minimal downtime?” → DMS.
-
“Which service assists in moving IIS apps to App Service?” → App Service Migration Assistant.
-
“Which service migrates on-prem file servers to Azure Files?” → Storage Migration Service.
-
“Which offline service transfers petabytes of data to Azure?” → Data Box.
What to Expect in the Exam
-
Direct Q: “Which tool is central for migrating SQL/Oracle DBs to Azure?” → DMS.
-
Scenario Q: “Company wants to move IIS web apps into PaaS environment.” → App Service Migration Assistant.
-
Scenario Q: “Company needs to migrate 100 TB of data but limited bandwidth.” → Azure Data Box.
-
Trick Q: “Azure SQL DB supports SQL Agent.” → False (use Managed Instance).