Intune – Windows Autopilot Devices – Preparation and Deployment
- 1 Intune – Windows Autopilot Devices – Overview
- 2 Intune – Windows Devices – Entra and Intune Status
- 3 Intune – Windows Autopilot Devices – Export Device Hash
- 4 Intune – Windows Autopilot Devices – Import Device Hash
- 5 Intune – Windows Autopilot Devices – Get Device ID
- 6 Intune – Windows Devices – Device Group Requirements
- 7 Intune – Windows Devices – Identify Group Membership
- 8 Intune – Windows Devices – Add or Remove Device Group Membership
- 9 Windows Devices – Imaging Preparation
- 10 Windows Devices – Imaging
- 11 Windows Devices – Create Windows Installer
- 12 Intune – Windows Autopilot Devices – User Driven Deployment
- 13 Intune – Windows Autopilot Devices – Self-Deploying
- 14 Intune – Windows Autopilot Devices – Delete
Section titles indicate whether the instructions are for Intune Windows devices in general, Windows devices (sans Intune), or Windows Autopilot devices specifically.
These instructions are meant for devices being Entra joined and Intune enrolled. They apply to both user driven and self-deploying Autopilot deployments (unless stated otherwise) and must be completed before proceeding with Windows Devices – Imaging
Determine device's Entra and Intune status before proceeding
Export Device Hash from Device
Import Device Hash to Autopilot Devices
Get Device ID from Intune
Assign Device ID to Group
Prepare Device for Windows installation
Install Windows
Proceed with Autopilot Deployment (User Driven or Self-Deploying)
Devices that are not brand new must be vetted on Intune before treating as "new to Intune"
Go to Intune Admin Center > Devices > By platform > Windows > Search box > Enter device name
Gotchas:
Use the search box above the device list, not the global search in the upper left
There's no serial number property to search, even though some devices may have their serial in their name
If the device name is unknown, search by most recent user
Intune Admin Center > Users > All users > Search box (name or email) > Click username > Devices
Some users will show multiple devices; use the Activity and Name columns to help deduce
If the device is not found:
If the device is found:
Note the values in the following columns
Join type
MDM
If device shows...
Join type = Microsoft Entra Joined
MDM = Microsoft Intune
...Proceed with Intune – Windows Devices – Repurpose, Surplus, or Missing (to be created)
If device shows...
Join type = Microsoft Entra Registered
MDM = Microsoft Intune
...Proceed with Intune – Windows Autopilot Devices – Delete
If device shows...
Join type = Microsoft Entra Registered
MDM = None
...Proceed with Intune – Windows Autopilot Devices – Export Device Hash
Check if device hash was previously imported
Go to Intune Admin Center > Devices > By platform > Windows > Device onboarding > Enrollment > Windows Autopilot > Devices > Search box > Enter serial number
If device exists, proceed with Intune – Windows Autopilot Devices – Get Device ID
If s/n is not present, export the device's hardware hash
Official methods: https://learn.microsoft.com/en-us/autopilot/add-devices
Recommended method: "Directly on the device using the Access work or school pane in the Settings app."
If possible, sign-in to an existing Windows install before re-imaging, and export the hash using recommended method
Copy CSV file (device hash) to your admin device where you will import it to Autopilot Devices
Next: Intune – Windows Autopilot Devices – Import Device Hash
Import Device Hash
Go to Intune Admin Center > Devices > By platform > Windows > Device onboarding > Enrollment > Windows Autopilot > Devices
Browse to the CSV acquired during Intune – Windows Autopilot Devices – Export Device Hash
Click Import button
Wait at least 5 minutes before proceeding
These steps are for acquiring a device’s “Device ID” which is required when assigning the correct device to a group.
Go to Intune Admin Center > Devices > By platform > Windows > Device onboarding > Enrollment > Windows Autopilot > Devices
Search for device’s serial number
If the device is not found, follow steps in Intune – Windows Autopilot Devices – Import Device Hash
Click the serial number and a pane will appear to the right
Click “Associated Microsoft Entra Device” in the pane
Copy the Device ID for later use
Next: Intune – Windows Devices – Add or Remove Device Group Membership
Devices must be manually assigned to at least one security group
At the time of writing, these groups are suffixed with “.Direct” (e.g. SPO.Intune.Devices.Classroom.Public.Direct)
Group names also identify whether the device will use "User Driven" or "Self-Deploying" deployment
Names that imply Self-Deploying contain “Public” or “Shared”
Otherwise, it’s likely meant for single user deployments (ask for clarification if unsure)
A device must have one of these “.Direct” groups assigned to it for Autopilot to work
These groups are also assigned to a Deployment Profile, Enrollment Status Page, apps, and policies (these elements are outside the scope of this documentation and should only be altered by an Endpoint Administrator)
A list of group names and their purposes will be supplied outside of this documentation
These instructions are for discovering which group a device is assigned to for Autopilot deployment
Go to Intune Admin Center > Devices > By platform > Windows > [search for Device ID (see: Intune – Windows Autopilot Devices - Get Device ID)]
Under device, click “Group membership”
Note the group ending in “.Direct”
Critical: If the device is a member of multiple groups ending in “.Direct”, escalate for help
See: Intune – Windows Devices – Device Group Requirements for more on Autopilot device group membership
It is implied that all groups in question end with “.Direct” as they are “assigned membership” type device groups that Autopilot depends upon.
Assign Device to Group Using its Device ID
Follow the steps in Intune – Windows Autopilot Devices – Get Device ID if you don’t already have the Device ID
Go to Intune Admin Center > Groups > All Groups > [search for target group]
Click group name > Members > Add members > Paste Device ID into search > Check box > Click Select (bottom) to add it
Refresh group list to confirm it’s been added
Use Intune’s Refresh button, not browser refresh (multiple refreshes may be needed to see changes)
Next:
Remove Device from Group
While not often necessary, these steps apply to contexts where a device is being repurposed outside its previous use-case
Follow the steps in Intune – Windows Devices – Identify Group Membership to find current group membership
Go to Intune Admin Center > Groups > All Groups > [group in question] > Members
Select device in question > Click Remove
Refresh group list to confirm it’s been removed
Always use Intune’s Refresh button, not browser refresh (multiple refreshes may be needed to see changes)
These steps apply to Dell devices; interpret as-needed for other vendors
Prepare Device for Windows Installation
Boot device > Hit F2 for BIOS > Reset BIOS to Factory Defaults > Reboot
Boot device > Hit F2 for BIOS > Storage > Select AHCI
RAID requires drivers we don’t have on our vanilla Windows Enterprise image
If the drive controller is changed, it will prevent the existing Windows installation from booting
Revert to RAID if existing Windows installation is needed again
Save and Exit
These steps assume you are imaging a Dell device and deploying with Intune’s Autopilot
Do not proceed with imaging until all prerequisites are complete
Image the device with Windows Enterprise Edition using a USB thumb drive supplied by the Spokane campus help desk
Follow Windows Devices – Create Windows Installer if starting from scratch
Boot device > Hit F12
Choose the thumb drive from the UEFI boot list
Gotcha: There may be two entries found on the same USB drive; use the first. If that doesn't work, use the second
Windows setup begins > Choose Language > Choose Keyboard > Stop at "Select setup option"
Critical: Click “Previous Version of Setup” in the lower left corner of Windows Setup
Proceed through prompts > Click Install Now > Accept License > Choose Custom install
Delete all partitions on Drive 0 until only one “Unallocated” space remains
Critical: These instructions assume there is only one internal drive installed (drive 0); be certain that any additional internal drives are not being wiped as they may contain user data
Click Drive 0 unallocated space > New > Apply (use max storage available)
Click Next; the necessary partitions will be created automatically
Click Next; Windows installation begins
Next:
Obtain Windows ISO
Go to \\cs.spokane.wsu.edu\its\Push\Microsoft\ and browse to the latest Windows release deployed by Spokane ITS (Windows 11 25H2 at the time of writing)
Copy the Windows ISO to local storage
Download Rufus
Microsoft Store UWP App:
Official Site:
https://rufus.ie/en/ > Scroll down to Download section
Gotcha: Watch out for ads on the page with the word “Download”!
Download Rufus (Standard type) for your device’s platform (x86 or ARM)
Rufus does not require installation as it will launch from wherever the EXE is located
Create Windows Installer
Open Rufus
Insert your Windows installer USB drive
Rufus Settings
Device
Choose the Windows installer USB drive; be certain by confirming its name, letter, and capacity
Boot selection
Disk or ISO image
Browse to the Windows ISO
Image option
Standard Windows installation
Partition scheme
GPT
Target System
UEFI (non CSM)
Volume label:
e.g. Windows 11 25H2
File system
NTFS
Cluster size
4096 (Default)
Show advanced format options
Select “Quick format”
Select “Create extended label and icon files”
Click START
User-driven deployment is meant for devices with a Primary User (AKA single user)
Autopilot User Driven Deployment Prerequisites
Use Ethernet for best results, but WiFi is an option
Device ID has been assigned to a group (see: Intune – Windows Devices – Add or Remove Device Group Membership)
You’ve completed Windows Devices - Imaging
Initiating Pre-Provisioning for User Driven Deployment
You may begin when Windows is waiting at OOBE (out of box experience)
If using Ethernet:
Proceed to the Microsoft Account sign-in screen
Press Windows key 5 times
If using WiFi:
Proceed to network selection and connect to WSU Wireless
Proceed to the Microsoft Account sign-in screen
Press Windows key 5 times
Autopilot loads with 3 options; choose “Pre-Provision with Windows Autopilot”
Wait while Pre-Provisioning installs required apps and policies
Not all apps install during Pre-Provisioning, so the customer will need to wait for stragglers to finish installing
Click “Reseal” when it completes; the device will power off
Device can now be given to the customer
The customer will need to use the Company Portal app for our offering of optional apps
At the time of writing this offering is limited; more may be added if there is a need
Self-deploying is meant for shared devices (loaner, library, and classroom devices)
Autopilot Self-Deployment Pre-Requisites
Ethernet connection
Gotcha: Relying on WiFi for self-deployments will likely result in failure even after connecting to WiFi
Device ID is assigned to a group name that ends with either “Public.Direct” or “Shared.Direct” (see: Intune – Windows Devices – Add or Remove Device Group Membership)
You’ve completed Windows Devices - Imaging and any additional required steps
Initiating Self-Deployment
Self-deployment will begin without warning after Windows installation completes
It’s finished when you see the Windows sign-in screen with two sign-in options: “Other user“ and “Guest”
Customers may login with their WSU email address or use the Guest account
Remove Autopilot device registration to ensure the device cannot re-enroll via Autopilot
Go to Intune Admin Center > Devices > By platform > Windows > Device onboarding > Enrollment > Windows Autopilot > Devices > Search box > Enter serial number
Select device > Delete
To surplus (or otherwise remove) a device on Intune, proceed with Intune – Windows Devices – Wipe (to be created)
To re-deploy a device with Autopilot, proceed with Intune – Windows Autopilot Devices – Export Device Hash