Migrating to Azure
Microsoft Azure is one of Cloudville's biggest districts, and Microsoft gives you a full map and a full toolbox for moving in. In this lesson we'll follow the Cloud Adoption Framework (the map) and the Azure Migrate toolchain (the movers) from first plan to running workloads. Everything here is provider-neutral thinking made concrete with Azure's own names.
Imagine the Rusty family is moving into the Azure neighborhood of Cloudville. Microsoft hands them a printed guidebook that says which day to do what (that's the Framework), plus a truck, a box-counter, and a labeler with "Azure" stamped on the side (those are the tools). Same moving day you already know — just with Azure-branded gear.
The map: the Cloud Adoption Framework
☺ Like you're 10: Before anyone lifts a box, Microsoft's guidebook tells you the order of the day so you don't put the couch in before the walls are painted.
The Cloud Adoption Framework (CAF) is Microsoft's free step-by-step guidance for moving to and running in Azure. It's organized into methodologies — think of them as chapters of the guidebook. Some run in order at the start; others run continuously forever after.
The first four (Strategy → Plan → Ready → Adopt) are mostly sequential — you do them roughly in order. Govern, Secure, and Manage are operational — they start early and never stop. This mirrors the vendor-neutral migration journey you already learned: assess, plan, prepare, migrate, operate. (Arriving from another cloud instead of a data center? The same chapters apply — see cloud-to-cloud migration.) Here's each chapter of the guidebook.
Strategy — write down why you're moving
☺ Like you're 10: First figure out why you're moving before you pack a single box.
Strategy is where you write down why you're moving (save money? close a data center? move faster?). This is your business case — the reason everything else exists. Skip it and you'll spend money moving things you should have retired.
Plan — inventory and build the roadmap
☺ Like you're 10: Count everything you own and write down the moving schedule.
Plan is where you inventory what you have and build a migration plan and timeline. The output is a roadmap: what moves, in what order, by when. This is also where a large estate gets broken into waves so you never move everything in one risky night.
Ready — prepare the Azure environment
☺ Like you're 10: Build and furnish the new house before anyone shows up with boxes.
Ready is where you prepare the Azure environment itself: the Azure landing zone. It's the difference between unpacking into a finished home and dumping boxes on a bare concrete slab. We build this out in full in the next section.
Adopt — Migrate and Modernize
☺ Like you're 10: This is the actual carrying-boxes-and-arranging-furniture part.
Adopt is the doing part, split into Migrate (move what exists) and Modernize (improve it). The "Migrate & Modernize" guidance inside Adopt is where CAF connects to the 7 R's: a simple rehost ("lift and shift") is a Migrate move, while turning an app into containers or serverless is a Modernize move.
Govern, Secure, and Manage — the chapters that never end
☺ Like you're 10: The chores that never stop — keeping the new place tidy, locked, and running.
Govern, Secure, and Manage are the ongoing chapters that run in parallel, forever, keeping the neighborhood compliant, protected, and healthy. Unlike the first four, they don't have a finish line — they start early and keep going long after the last box is unpacked.
Ready in depth: the Azure landing zone
☺ Like you're 10: Before the truck arrives, someone builds the house — walls, locks, address, and rules on the fridge — so the family has a safe, organized place to unpack into.
An Azure landing zone is a pre-built, well-organized Azure environment ready to receive your workloads. It's the output of the Ready methodology. Instead of dumping servers into a messy account, you set up structure first. The key building blocks each get their own piece of the house.
Management groups
☺ Like you're 10: Folders for your accounts, so one rule can cover many at once.
Management groups are folders that hold your Azure subscriptions, so you can apply the same rules to many subscriptions at once. Set a rule on the folder and every subscription inside inherits it — no copy-pasting the same policy a hundred times.
Azure Policy
☺ Like you're 10: Rules taped to the fridge that enforce themselves.
Azure Policy provides automatic guardrails ("all storage must be encrypted", "no resources outside Europe"). Policy-driven governance means the rules enforce themselves — a resource that breaks a rule is flagged or blocked without anyone having to notice.
Platform vs. application landing zones
☺ Like you're 10: One part of the house holds the shared plumbing; the others hold each family's stuff.
A platform landing zone holds shared services (identity, networking, monitoring); application landing zones are where individual apps live. Splitting them means the shared foundations are built and secured once, and each app lands in its own tidy space on top.
The Azure landing zone accelerator
☺ Like you're 10: A kit that builds the whole house for you in one go.
Microsoft ships a reference implementation often called the Azure landing zone accelerator (historically "enterprise-scale") that deploys this whole structure for you. It's the concrete version of the vendor-neutral idea covered in provisions and landing zones.
The tools, by phase
☺ Like you're 10: Every job on moving day has its own gadget — one counts boxes, one drives the truck, one carefully carries the fish tank. Here's which Azure gadget does which job.
Benny's Azure toolbox lines up neatly with the CAF phases. The central hub is Azure Migrate — a single place in the Azure portal that runs discovery, assessment, and much of the migration. You deploy a lightweight Azure Migrate appliance in your data center; it quietly collects configuration and performance data about your servers and sends it up to Azure.
Discover & assess
☺ Like you're 10: The gadgets that walk around, count every box, and note how heavy each one is.
This is where every Azure migration starts — you can't move what you haven't counted or sized. Three tools do the counting:
- Azure Migrate: Discovery and assessment — the hub. What it does: inventories servers, VMs, and apps and recommends Azure target sizes and cost estimates; it now also discovers and assesses SQL Server, MySQL, and PostgreSQL, recommending target sizes. When to use it: first, on every project.
- SQL Server Management Studio’s migration assessment (the successor to Data Migration Assistant, which Microsoft retired in July 2025) — What it does: checks a database for compatibility issues before you move it. When to use it: on each SQL database during Plan / Assess.
- App Service Migration Assistant — What it does: assesses .NET and PHP web apps. When to use it: when the workload is a web app headed for Azure App Service.
Move servers
☺ Like you're 10: The truck that drives whole machines to the new house.
- Azure Migrate’s Migration and modernization tool (Microsoft’s current name for what was “Server Migration”) — What it does: replicates and cuts over VMs and physical servers, in agentless mode (no software on each server) or agent-based mode. When to use it: to rehost machines during Adopt · Migrate.
Move databases
☺ Like you're 10: The careful mover for the fish tank — the data must arrive alive and complete.
- Azure Database Migration Service (DMS) — What it does: migrates databases at scale (SQL Server, MySQL, PostgreSQL) with minimal downtime. When to use it: to move the databases themselves once DMA says the compatibility is clean.
Move data — files & objects
☺ Like you're 10: For a mountain of boxes: mail them over the wire, or if it's too much, load a shipping container.
- Azure Storage Mover (a free managed service) — What it does: moves file/object data over the network. When to use it: online transfers of file shares.
- AzCopy (a command-line tool) — What it does: pushes data over the network. When to use it: scripted or ad-hoc online copies.
- Azure Data Box family — What it does: ships you a physical, encrypted appliance to fill and mail back. When to use it: offline, when the dataset is too big for the network — the answer to data gravity when the network is too slow.
| CAF phase | Job to do | Azure tool |
|---|---|---|
| Plan / Assess | Find & size servers, VMs, apps, DBs | Azure Migrate: Discovery and assessment |
| Plan / Assess | Check database compatibility | SSMS migration assessment (successor to the retired DMA) |
| Plan / Assess | Assess web apps | App Service Migration Assistant |
| Ready | Build the governed foundation | Azure landing zone · Management groups · Azure Policy |
| Adopt · Migrate | Move servers & VMs (rehost) | Azure Migrate: Server Migration |
| Adopt · Migrate | Move databases | Azure Database Migration Service (DMS) |
| Adopt · Migrate | Move files/objects online | Azure Storage Mover · AzCopy |
| Adopt · Migrate | Move huge data offline | Azure Data Box family |
| Adopt · Modernize | Containerize / re-architect | Azure Kubernetes Service · App Service · Functions |
| Govern / Secure / Manage | Keep it compliant & healthy | Azure Policy · Microsoft Defender for Cloud · Azure Monitor |
Azure Migrate is the hub: it does discovery and assessment, and it drives server migration. DMS handles databases; Storage Mover, AzCopy, and Data Box handle raw data. The Cloud Adoption Framework tells you the order to use them in. (For the vendor-neutral categories these all map to, see the tools overview.)
A short worked example
☺ Like you're 10: Let's actually move one small business into Azure, step by step, and name the gadget used at each step.
Say "Rusty Retail" runs 40 Windows VMs and one big SQL Server database on-premises and wants to close its data center. Watch how the CAF phases and the tools slot together.
Strategy & Plan
☺ Like you're 10: Decide the deadline, then let the box-counter tell you what's really there.
The goal is to exit the data center in nine months. They deploy the Azure Migrate appliance; after two weeks it reports all 40 servers, their dependencies, and a monthly Azure cost estimate. DMA flags two deprecated features in the SQL database to fix first.
Ready
☺ Like you're 10: Build Rusty Retail's new Azure house before moving anything in.
They deploy an Azure landing zone with a management group for "Corp", an Azure Policy requiring encryption, and a platform landing zone for shared networking.
Adopt · Migrate
☺ Like you're 10: Now actually drive the servers, the database, and the giant archive over.
Azure Migrate: Server Migration replicates the 40 VMs in agentless mode over several nights, then cuts them over on a weekend (in a real project you'd split 40 VMs across a few waves rather than one weekend). Azure Database Migration Service moves the SQL database with only minutes of downtime. A one-time 20 TB archive is too big for the network, so they order an Azure Data Box, fill it, and ship it back.
Manage
☺ Like you're 10: The move is done — now keep watch and switch off the old place.
With everything running, Azure Monitor and Microsoft Defender for Cloud keep watch, and the old Fort Rusty racks get switched off.
Pick any 3 rows from the toolchain table above. For each, write one sentence in your own words explaining what that tool does and which CAF phase it belongs to. Then answer: which single tool would you reach for first in any Azure migration, and why?
Foxy: Professor, there are so many Azure tools — how do I not get lost?
Professor Owl: You don't memorize tools first — you follow the Framework. Strategy, Plan, Ready, Adopt. The tools slot into the phases.
Gizmo: Boring! Just spin up VMs in a fresh subscription and dump everything in. Skip the "Ready" chapter!
Benny: No landing zone? No management groups, no Azure Policy? That's how you get 40 servers with no encryption and no rules. I'd be rebuilding it all in a month.
Timmy: Fact-check: Ready comes before Adopt for exactly that reason. Build the house, then move in the furniture.
Professor Owl: Start with Azure Migrate to discover and assess. Let the data — not Gizmo — decide what moves.
Azure product names change often. "Azure Site Recovery" once handled lift-and-shift; today Azure Migrate: Server Migration is the recommended path. Always confirm the current tool in Microsoft Learn before you build a plan — and see the tools overview for the vendor-neutral categories these map to.
1. Name the four sequential CAF methodologies in order. 2. What is an Azure landing zone, and which two of its building blocks enforce rules? 3. Which Azure tool is the central hub for discovery and assessment? 4. Your database is huge and the network is slow — online or offline transfer, and which tool?
Check your answers
- Strategy → Plan → Ready → Adopt (then Govern, Secure, and Manage run continuously).
- A pre-built, governed Azure environment ready to receive workloads; Management groups organize subscriptions and Azure Policy enforces guardrails.
- Azure Migrate — specifically its Discovery and assessment capability; it also drives server migration.
- Offline — order an Azure Data Box, fill it, and ship it back (this defeats data gravity when the network is too slow).