What you'll build
- A Windows 11 VM that boots to your company's branded sign-in page instead of standard Windows setup.
- The user signs in once; the device joins Entra ID and enrols in Intune by itself, then shows the Enrollment Status Page.
- A Hyper-V checkpoint lets you replay the whole zero-touch demo in minutes, perfect for training.
| Item | What you need | Cost |
|---|---|---|
| Intune + Entra ID P1 | Microsoft 365 E3, E5 or Business Premium (a trial works for a short lab) | 0 extra |
| Hyper-V | Built into Windows 10/11 Pro, Enterprise or Education | 0 |
| Windows 11 media | Windows 11 Enterprise evaluation ISO or Pro ISO | 0 |
The lab uses user-driven mode with Microsoft Entra join. Self-deploying mode doesn't work on virtual machines, including Hyper-V virtual TPMs (Microsoft Learn).
How it works
You do the top row once, as the admin. The bottom row happens by itself the first time the device boots: the user only picks a region and signs in.
Prerequisites and licences
| Requirement | Why | How to check |
|---|---|---|
| Microsoft 365 E3/E5/Business Premium, or Entra ID P1 + Intune (licensing) | Automatic MDM enrolment and company branding | Admin center > Billing > Licenses |
| Licence assigned to the test user | Users need a licence to enrol devices | Admin center > Users > Active users |
| Automatic enrolment: MDM user scope = All (or a group) | The device enrols in Intune when it joins Entra | Intune > Devices > Enrollment > Windows > Automatic Enrollment |
| Users may join devices to Microsoft Entra | The first user who signs in joins the device | Entra > Devices > Device settings |
| Intune Administrator role for you | To register devices and create profiles | Entra > Roles and administrators |
| Hyper-V host: Windows 10/11 Pro or Enterprise, 8 GB+ RAM, virtualisation on | Runs the lab VM | Turn Windows features on or off > Hyper-V |
| Windows 11 ISO | Installs the VM up to the first setup screen | Microsoft Evaluation Center or Visual Studio downloads |
Company branding is optional but recommended: the square logo, sign-in page text and tenant name are what users see during Autopilot (Microsoft Learn).
Phase 1 · 15 min
Tenant preparation
- Automatic enrolment. Intune admin center > Devices > Enrollment > Windows > Automatic Enrollment: MDM user scope = All > Save.
- Device join. Entra admin center > Devices > Device settings: Users may join devices to Microsoft Entra = All; keep the device limit at 20 or more for a lab.
- Company branding. Entra admin center > User experiences > Company branding > Default sign-in > Edit: add a square logo, sign-in page text (for example Welcome to Contoso. Sign in with your work account.) and a username hint
[email protected]. - Enrollment restrictions. Intune > Devices > Enrollment > Device platform restrictions > Windows: confirm MDM = Allow and no minimum/maximum OS version that blocks Windows 11.
- Test user. Create
[email protected]and assign a Microsoft 365 E3 (or Business Premium) licence.
Phase 2 · 20 min
Group, deployment profile and Enrollment Status Page
Dynamic device group. Entra admin center > Groups > New group: Security, name Autopilot-Lab-Devices, membership Dynamic Device, rule:
(device.devicePhysicalIds -any (_ -eq "[OrderID]:Training"))
The rule matches only devices registered with the group tag Training, so the lab never touches production devices. To catch every Autopilot device instead:
(device.devicePhysicalIDs -any (_ -startsWith "[ZTDid]"))
Deployment profile. Intune > Devices > Enrollment > Windows > Windows Autopilot > Deployment profiles > Create > Windows PC:
| Setting | Lab value |
|---|---|
| Name | Autopilot User Driven Entra Join |
| Convert all targeted devices to Autopilot | No |
| Deployment mode | User-Driven |
| Join to Microsoft Entra ID as | Microsoft Entra joined |
| License terms / Privacy settings / Change account options | Hide / Hide / Hide |
| User account type | Standard |
| Allow pre-provisioned deployment | No |
| Apply device name template | Yes: LAB-%RAND:5% (15 characters maximum) |
| Assignments | Autopilot-Lab-Devices |
Enrollment Status Page. Intune > Devices > Enrollment > Windows > Enrollment Status Page > Create: show app and profile progress = Yes, timeout 60 minutes, allow reset on error = Yes, allow use if error = Yes, block device use until required apps install = Selected (none for a first demo). Assign to Autopilot-Lab-Devices.
Phase 3 · 20 min
Build the Hyper-V VM
Windows 11 needs a Generation 2 VM with Secure Boot and a virtual TPM. Run this in an elevated PowerShell on the Hyper-V host (change the ISO path first):
$vm = "AP-LAB-01" $iso = "C:\ISO\Win11.iso" New-VM -Name $vm -Generation 2 -MemoryStartupBytes 4GB -NewVHDPath "C:\Hyper-V\$vm.vhdx" -NewVHDSizeBytes 80GB -SwitchName "Default Switch" Set-VMProcessor -VMName $vm -Count 2 Set-VMMemory -VMName $vm -DynamicMemoryEnabled $false Set-VMKeyProtector -VMName $vm -NewLocalKeyProtector Enable-VMTPM -VMName $vm Add-VMDvdDrive -VMName $vm -Path $iso Set-VMFirmware -VMName $vm -FirstBootDevice (Get-VMDvdDrive -VMName $vm) Set-VM -Name $vm -AutomaticCheckpointsEnabled $false Start-VM -Name $vm
- Connect to the VM and press a key to boot from the ISO.
- Install Windows 11 (Pro or Enterprise). Choose I don't have a product key if asked.
- Stop at the first setup screen (region selection). Don't click through it: this is where Autopilot takes over.
Phase 4 · 15 min
Register the hardware hash
Option A: upload straight from the VM (recommended). At the region screen press Shift + F10, type powershell, then run Microsoft's documented commands (Microsoft Learn):
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned Install-Script -Name Get-WindowsAutopilotInfo -Force Get-WindowsAutopilotInfo -Online -GroupTag "Training"
Agree to install NuGet if prompted, then sign in with an Intune Administrator account. The first run asks you to approve the script's Microsoft Graph permissions.
Option B: save a CSV and import it. Replace the last line with the command below, copy the file off the VM, then Intune > Devices > Enrollment > Windows > Windows Autopilot > Devices > Import.
Get-WindowsAutopilotInfo -OutputFile C:\HWID\AutopilotHWID.csv
- Intune > Windows Autopilot > Devices > Sync: the VM's serial number appears with group tag
Training. - Wait until Profile status = Assigned (usually 5–15 minutes while the dynamic group updates).
- In Hyper-V Manager, take a checkpoint named OOBE - Autopilot ready, so you can re-run the demo in seconds.
Phase 5 · 15 min
Run the zero-touch demo and verify
- In the VM's PowerShell window, restart:
shutdown /r /t 0. - Choose region and keyboard. After the network check, the branded sign-in page appears with your logo and Welcome to Contoso text.
- Sign in as
[email protected]and complete MFA if asked. - The Enrollment Status Page runs: Device preparation, Device setup, Account setup.
- The desktop appears: the device is joined and managed.
On Windows 11, press Ctrl + Shift + D during setup to open the Autopilot diagnostics page if anything stalls. Your ticks are saved in this browser only.
Re-running the lab and troubleshooting
Run the demo again: delete the device from Intune > Devices > All devices (keep the Autopilot registration), then apply the checkpoint OOBE - Autopilot ready and restart the VM. Don't delete the Entra device object that Autopilot created at registration; Autopilot needs it to identify the device (Microsoft Learn).
| Symptom | Likely cause | Fix |
|---|---|---|
| Standard Windows setup, no branded sign-in | Profile not assigned before setup started | Check Profile status = Assigned, then apply the checkpoint (or reset the VM) and restart |
| Profile status stays Not assigned | Device not in the dynamic group | Check the group tag is exactly Training and the rule text; wait 15 minutes; Sync |
| Error 0x80180014 at sign-in | Enrolment blocked, often by a platform restriction or an old device record | Allow Windows MDM in enrolment restrictions; delete the old Intune device record |
| This PC can't run Windows 11 | VM is Generation 1, or TPM / Secure Boot off | Rebuild as Generation 2 with Enable-VMTPM |
| CSV import fails | File edited in Excel, extra columns or quotes | Re-export with the script; edit only in Notepad |
| Enrollment Status Page times out | Too many blocking apps for a slow VM | Block on Selected apps only, or raise the timeout |
| Self-deploying mode fails with 0x800705B4 | Not supported on VMs, including Hyper-V virtual TPM | Use user-driven mode for VM labs |
Adapting this lab to your tenant
| Example in this guide | Replace with |
|---|---|
contoso.com, [email protected] | Your domain and a licensed test user |
Group tag Training | Any tag you like; keep the group rule in sync |
Autopilot-Lab-Devices, profile and ESP names | Your naming convention |
Device name template LAB-%RAND:5% | Your prefix (15 characters maximum) |
AP-LAB-01, C:\ISO\Win11.iso, C:\Hyper-V | Your VM name and paths |
Registering devices yourself with a hardware hash is meant for testing and small numbers; in production, the manufacturer or reseller registers devices for you (Microsoft Learn). Sources checked 11 Nov 2026.
Want to build this live, with help?
This lab is part of my hands-on Intune and Windows Autopilot training. Small batches, live online, real tenant.