azureblog.co.uk
← MD-102 study plan
MD-102 · Manage and maintain devices

Deploy and upgrade Windows with cloud tools

Autopilot profiles versus device preparation, deployment modes, device naming, the Enrollment Status Page, Windows 11 upgrades, Windows 365 Cloud PCs and Windows Backup.

  • 24 min
  • 8 concepts
  • Try it yourself
  • 5-question check

Learn

Windows Autopilot turns a new device out of the box into a ready-to-use business device without imaging. Windows 365 does the same for a Cloud PC. Both are configured in Intune.

  1. 1

    Choose between Windows Autopilot deployment profiles and device preparation policies

    Autopilot deployment profiles (the original) need devices registered with hardware hashes first, and support user-driven, pre-provisioning, self-deploying and hybrid join. Autopilot device preparation (newer) needs no hardware hash registration: it's assigned to a user group, installs selected apps and scripts during OOBE, and gives better reporting. It supports user-driven Entra join and automatic mode for Windows 365.

    Remember: No hash registration and better reporting: device preparation.

  2. 2

    Choose between Windows Autopilot deployment modes, including user-driven, pre-provisioning, and self-deploying

    User-driven: the user signs in and setup completes. Pre-provisioning (white glove): IT or a partner does the device phase in advance (press Windows key five times), so users only do the user phase. Self-deploying: no user at all, for kiosks and shared devices; needs TPM 2.0 attestation and Entra join.

    Remember: Kiosk with no user: self-deploying.

  3. 3

    Apply a device name template by using Windows Autopilot

    In an Entra join deployment profile, set a name template up to 15 characters using %SERIAL% or %RAND:x%, for example CTS-%SERIAL%. Hybrid joined names come from the domain join profile prefix instead.

    Remember: 15 characters max, %SERIAL% or %RAND:x%.

  4. 4

    Implement Windows client deployment by using Windows Autopilot

    Steps: register devices (OEM, reseller, or upload hardware hashes), create a device group (often by group tag), create and assign the deployment profile, configure the ESP, and assign apps and policies. Autopilot can also reset devices remotely (Autopilot Reset) to a business-ready state.

    Remember: Register → group → profile → ESP → apps.

  5. 5

    Create an Enrollment Status Page (ESP)

    The ESP shows progress during setup and can block device use until required apps and policies install. Choose which apps block, set a timeout, allow users to reset or continue on error, and show error messages. Assign it to device or user groups.

    Remember: Block use until the security apps are on.

  6. 6

    Plan and implement device upgrades for Windows 11 by using Intune

    Check readiness with the Windows 11 readiness report (Endpoint analytics / Work from anywhere) for hardware such as TPM 2.0 and supported CPUs. Upgrade with a feature update policy targeting a Windows 11 version, or an upgrade edition policy for edition changes. Windows 10 reached end of support on 14 October 2025.

    Remember: Readiness report first, then a feature update policy.

  7. 7

    Provision and configure Windows 365 Cloud PCs by using Intune, including provisioning policies, network connections, and image management

    A provisioning policy sets the join type (Entra join or hybrid join), network (Microsoft hosted network or an Azure network connection to your VNet), image (gallery or custom managed image), region and language. Assign licences and the policy to users. Custom images are uploaded from Azure; gallery images include Microsoft 365 Apps.

    Remember: No VNet needed with Microsoft hosted network.

  8. 8

    Implement Windows Backup by using Intune

    Windows Backup for Organizations backs up users' Windows settings and Microsoft Store apps to the cloud so a new or reset device can be restored during setup. Turn it on with a settings catalog policy for backup and the tenant-wide restore setting in Intune, for Entra joined devices.

    Remember: Back up settings, restore them during OOBE on the new device.

Autopilot deployment modes

User-driven
  • User signs in at OOBE
  • Most common
  • Entra join or hybrid join
Pre-provisioning
  • IT does device phase first
  • Faster for users
  • Needs TPM 2.0
Self-deploying
  • No user interaction
  • Kiosks and shared devices
  • Entra join only, TPM 2.0

Try it

Pick the Autopilot approach.

This interactive part needs JavaScript.

In the portal

  • Autopilot devicesIntune admin center: Devices > Enrollment > Windows > Devices
  • Deployment profilesIntune admin center: Devices > Enrollment > Windows > Deployment profiles
  • Enrollment Status PageIntune admin center: Devices > Enrollment > Windows > Enrollment Status Page
  • Windows 365Intune admin center: Devices > Device onboarding > Windows 365

Key terms

Click a card to see the definition.

Check your understanding

5 questions. Score 80% or more and these skills are marked as confident in your MD-102 study plan.

  1. Which Autopilot mode needs no user interaction?

  2. Which approach doesn't need hardware hash registration?

  3. What stops users using a device until required apps are installed?

  4. Which is a valid name template?

  5. Cloud PCs must reach on-premises servers through your VNet. What do you set?

Sources

Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.