3.1. Deploy and Upgrade Windows Clients with Cloud-Based Tools
💡 First Principle: Cloud deployment replaces the imaging bench. Instead of copying a golden image onto every disk, you ship a factory-fresh device straight to the user, and on first boot Windows configures itself from the cloud: it joins Microsoft Entra ID, enrolls in Intune and pulls down its apps and policies. Every tool here answers one question: how much happens before the user sees a desktop, and who has to be there?
Why care? The method decides whether the user waits at the setup screen, whether IT touches the device at all, and whether it can be hybrid joined — and the wrong one fails outright or breaks at scale.
Think of it as furniture delivery. Classic Autopilot is a service you register with in advance: the device is on file before it ships, and a progress screen keeps the user out of the room until everything is assembled. Device preparation needs no advance registration and assembles the essentials while the user watches, with fewer delivery options. Windows 365 skips delivery altogether — the "device" is a Cloud PC in a Microsoft datacenter.
⚠️ Common Misconception: Because Microsoft presents Autopilot device preparation as the next generation of Autopilot, many people assume it's a newer version of deployment profiles with the same features. It isn't a superset: it needs no hardware hash pre-registration, but it has no Enrollment Status Page, doesn't support pre-provisioning or self-deploying mode, and can't hybrid join physical devices. Classic deployment profiles remain the right choice there, and both can run side by side in one tenant.