Curriculum Overview: Azure Migration Options

This document outlines the structured learning path for mastering Azure's migration ecosystem, focusing on Azure Migrate for workload transitions and Azure Data Box for large-scale data transfer. This curriculum is aligned with the Microsoft AZ-900 certification requirements.

Prerequisites

Before starting this module, students should possess:

Basic Cloud Literacy: Understanding of IaaS, PaaS, and SaaS models.
Azure Storage Fundamentals: Knowledge of Blobs, Files, and Disk storage types.
Networking Basics: Familiarity with IP addressing, bandwidth concepts, and on-premises vs. cloud environments.

Module Breakdown

Module ID	Topic Name	Focus Area	Difficulty
M1	Introduction to Azure Migrate	Discovering and assessing on-premises workloads	Intermediate
M2	The Migration Lifecycle	The 3-step process: Discover, Assess, Migrate	Intermediate
M3	Azure Data Box Family	Offline data transfer for massive datasets	Beginner
M4	Selecting the Right Tool	Comparison of AzCopy, Storage Explorer, and Data Box	Advanced

Learning Objectives per Module

Module 1: Azure Migrate Fundamentals

Define the purpose of an Azure Migrate Project as a metadata container.
Identify supported workloads (VMs, Databases, Web Apps, VDI).
Understand the cross-cloud capability (migrating from AWS/GCP to Azure).

Module 2: The Migration Process

Loading Diagram...

Module 3: Azure Data Box Family

Distinguish between the three physical form factors:
1. Data Box Disk: Up to 35 TB (5x SSDs).
2. Data Box: 80 TB ruggedized device.
3. Data Box Heavy: 1 PB (Petabyte) high-capacity device.
Explain the "Offline" nature of these services (shipping physical hardware).

Success Metrics

To demonstrate mastery of this curriculum, the learner must be able to:

Diagram the Migration Path: Correctly identify the order of Discovery, Assessment, and Migration.
Tool Selection: Choose the correct Data Box product based on a given data volume (e.g., selecting Data Box Heavy for a 500 TB migration).
Conceptual Differentiation: Explain why one would use Azure Migrate (for live VM replication) versus Data Box (for bulk data seeding).
Performance Calculation: Estimate transfer times for online tools (AzCopy) versus the physical turnaround time of Data Box.

Real-World Application

Scenario: The Data Center Exit

An enterprise is closing its local data center and moving 400 TB of historical archive data and 50 SQL servers to Azure.

[!IMPORTANT] For the 400 TB of archives, using a standard 100 Mbps internet connection would take months. The Real-World Solution is to use Azure Data Box Heavy to move the bulk data offline while using Azure Migrate to assess and replicate the active SQL servers.

Visual Decision Matrix

\begin{tikzpicture}[node distance=2cm, every node/.style={rectangle, draw, fill=blue!10, text width=3cm, align=center, minimum height=1cm}] \node (start) {Data Volume?}; \node (small) [below left of=start, xshift=-1cm] {< 35 TB}; \node (mid) [below of=start] {35 TB - 80 TB}; \node (large) [below right of=start, xshift=1cm] {> 80 TB};

code

\node (disk) [below of=small] {Data Box Disk};
\node (box) [below of=mid] {Data Box};
\node (heavy) [below of=large] {Data Box Heavy};

\draw [->] (start) -- (small);
\draw [->] (start) -- (mid);
\draw [->] (start) -- (large);
\draw [->] (small) -- (disk);
\draw [->] (mid) -- (box);
\draw [->] (large) -- (heavy);

\end{tikzpicture}

Comparison of Migration Tools

Feature	Azure Migrate	Data Box	AzCopy
Primary Use	Lift & Shift VMs/Apps	Moving Massive Files	Small/Medium File Transfer
Connectivity	Online (Network)	Offline (Shipping)	Online (Command Line)
Intelligence	Provides Assessments	Simple Storage Transfer	Scriptable File Copy
Complexity	High (Project based)	Medium (Logistics)	Low (Tool based)

[!TIP] Exam Tip: Remember that Azure Migrate isn't just for Hyper-V or VMware; it can also migrate physical servers and workloads from other cloud providers like AWS.

Curriculum Overview: Azure Migration Services & Data Transfer Solutions