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