Update March 25, 2024: The Windows Autopilot functionality mentioned below vary depending on the manufacturer. Please reach out to your respective OEM to confirm whether this functionality is enabled for your device.
They’re back! We’re excited to announce that some key Windows Autopilot functionality has been securely returned. Last year, we made some changes to the Autopilot sign-in experience that impacted how you deployed Autopilot devices. Thanks to your patience and feedback, we were able to securely bring those features back. Starting with Intune’s July (2207) service release, admins will be able to:
- Pre-populate the Azure Active Directory (Azure AD) User Principal Name (UPN) under the pre-provisioning landing page and Azure AD sign in page.
Note: This is limited based on the manufacturer. Please contact your OEM to confirm if this functionality is enabled. - Automatically re-enroll a device through Autopilot for instances where the profile is set to self-deployment or pre-provisioning modes (public preview) without deleting the device record.
Note: This is limited based on the manufacturer. Please contact your OEM to confirm if this functionality is enabled. Automatically re-enroll devices where hardware components may have been replaced with Autopilot auto-remediation if the OS has not been reset.
This restored functionality includes updates to both the Intune July (2207) service release and certain Windows builds. To leverage the updated Windows Autopilot sign-in and deployment experience, the following versions are supported:
|
Windows Build |
Version |
|
10.0.19042.1860 |
20H2 |
|
10.0.19042.2075 |
20H2 |
|
10.0.19043.1860 |
21H1 |
|
10.0.19043.2075 |
21H1 |
|
10.0.19044.1860 |
21H2 |
|
10.0.19044.2075 |
21H2 |
|
10.0.20348.828 |
21H1 (Windows Holographic) |
|
10.0.22000.828 |
21H1 (Windows Holographic) |
For more information about Windows OS builds, see our Windows Insider Blog Releasing Windows 11 Build 22000.829.
(Updated) What changes with motherboard replacements?
When a device checks into Intune after a motherboard replacement, the hardware hash will be checked. The device will now have a new hardware hash and the original device record in Intune will no longer be trusted by Autopilot. When a change in the components is detected, Intune will display a profile status under Autopilot devices as “Fix pending” or “Attention required.” You’ll be able to click these statuses to see a description of the issue to help remediate. Admins will need to remove the original device record and reregister before the device can be reset.
What happens to returned devices?
Any device permanently leaving your organization should be deregistered by an admin, see Deregister from Intune for guidance.
In an upcoming release, we’ll make deregistering an Autopilot device easier by adding an option to deregister in the device Wipe actions.
If you have any questions, feel free to respond to this post or reach out on Twitter @IntuneSuppTeam.
Post updates:
08/08/22: More information on supported Windows builds for this restored functionality.
10/13/22: More information on supported Windows builds for this restored functionality.
04/26/23: Updated list of OEM manufacturers that support this functionality.
06/01/23: Updated list of OEM manufacturers that supports this functionality.
03/05/24: The guidance for motherboard replacements has been updated.
03/25/24: Updated blog note.