In this video, we walk through a full demo of Windows Autopilot Device Preparation, a modern replacement for classic Autopilot that simplifies device provisioning with a single unified policy.

What's covered:

- What Windows Autopilot Device Preparation is and how it differs from classic Autopilot
- Key improvements including enrollment time grouping, real time deployment monitoring and visible progress indicators
- Current limitations including the 10 app and 10 script cap and Entra ID join only support
- Requirements including Windows 11 24H2 or later and specific KB update for older versions
- Verifying auto enrollment and device enrollment settings before getting started
- Creating an assigned device group with Intune Provisioning Client as owner
- Creating a user group to assign the device preparation policy - Deploying applications and scripts to the device group (Microsoft 365 Apps, Company Portal)
- How corporate device identifiers work as a replacement for hardware hashes
- Retrieving manufacturer, model and serial number using PowerShell and uploading as a CSV
- Creating a device preparation policy including deployment mode, user account type, error messages and diagnostic settings
- Adding applications and scripts to the policy (up to 10 of each)
- Running a full end to end enrollment demo with real time progress visibility
- Verifying that applications and PowerShell scripts were successfully deployed after enrollment
- Reviewing deployment reports in Microsoft Intune including deployment time and status By the end of this video you will have everything you need to set up and test Windows Autopilot Device Preparation in your own environment.

In this video, I introduce Windows Autopilot and walk through the prerequisites and initial setup steps needed before deploying your first Autopilot profile in Microsoft Intune.

What's covered:

- What Windows Autopilot is and how it simplifies device provisioning - Benefits of Autopilot including reduced IT workload, faster onboarding and simplified device recovery
- Entra ID join vs Hybrid Entra ID join scenarios (this video covers Entra ID join)
- Prerequisites for Windows Autopilot: automatic enrollment, Intune license, device registration and Entra ID branding
- Verifying automatic enrollment (MDM user scope) in Microsoft Intune and Microsoft Entra
- Confirming that the user has a Microsoft 365 E3 license with Intune included
- Configuring and verifying Entra ID company branding for the Autopilot sign in experience
- How hardware hashes work and why devices need to be registered in Windows Autopilot
- How OEM vendors like Dell can upload hardware hashes on your behalf before shipping
- Using PowerShell to generate a hardware hash CSV file on a Windows device
- Checking and setting the PowerShell execution policy before running the script
- Installing and running the Get-WindowsAutopilotInfo script
- Uploading the hardware hash CSV file to Microsoft Intune
- Creating a dynamic Entra ID group for Autopilot managed devices using the zero-touch deployment ID query

In this video, I walk through creating a Windows Autopilot deployment profile and Enrollment Status Page in Microsoft Intune, completing the setup before enrolling the first device.

What's covered:

- Creating a Windows Autopilot deployment profile step by step
- Convert all targeted devices to Autopilot option explained - User driven vs self deploying deployment modes
- Hiding license terms, privacy settings and change account options for a better user experience
- Setting user account type to standard (no admin rights)
- Pre provisioning deployment (formerly White Glove) explained and when to use it
- Configuring device name templates using serial number or custom name with random digits
- Assigning the deployment profile to the dynamic Autopilot group
- Creating an Enrollment Status Page (ESP) profile
- Configuring ESP settings including installation timeout, custom error messages and service desk contact info
- Enabling log collection and diagnostics for troubleshooting during pilot deployments
- Blocking device use until all required apps and profiles are installed
- Setting blocking apps (Microsoft 365 Apps and Company Portal) that must install before user can sign in
- How the only fail collective blocking apps in technician phase option works during pre provisioning
- Summary of all prerequisites completed and confirmed before first device enrollment

In this video, I run a full end to end Windows Autopilot enrollment demo, verify that all applications and policies were successfully deployed, and walk through reporting and troubleshooting tools in Microsoft Intune.

What's covered:

- Resetting a device to out of box experience using Sysprep
- Configuring a Conditional Access policy to require MFA during Intune enrollment
- Setting sign in frequency to every time to ensure MFA triggers on every enrollment
- Walking through the full Autopilot enrollment flow from sign in to device preparation
- Company branding confirmed working on the sign in screen - MFA prompt triggered by Conditional Access during enrollment
- Device joining Entra ID and receiving all settings and applications automatically
- Verifying that blocking apps (Microsoft 365 Apps and Company Portal) were successfully installed
- Confirming the device name was applied correctly using the demo plus random digits template
- Checking device compliance status in Microsoft Intune immediately after enrollment
- Reviewing the Windows Autopilot deployment status report including deployment start time, end time and total duration
- How to identify which deployment profile and Enrollment Status Page were applied to a device
- Troubleshooting Autopilot issues using Event Viewer under Modern Deployment Diagnostic Provider
- Managing Enrollment Status Page profile priority and how to reorder profiles in Intune