Windows Autopilot
Device enrollmentAutomatic Registration of Existing Devices | Microsoft Learn
In brief
The article’s title and description were updated, and wording was clarified around device requirements, hardware-hash requests, the Convert all targeted devices to Autopilot setting, and the Windows Autopilot for existing devices scenario.
What Intune admins need to know
Administrators get clearer guidance on automatic registration and the distinction between registering devices and converting existing hybrid Microsoft Entra devices.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Automatic registrationRegistration of existing devicesExisting Devices | Microsoft Learn
Requirements
An existing device can automatically register if it's: meets the following criteria:
RunningRuns a supported version of Windows- Enrolled in a mobile device management (MDM) service such as Intune
- A corporate device that isn't already registered with Windows Autopilot
For devices that meet these requirements, the MDM service can ask the device forrequest the hardware hash.hash from the device. After it has that,the hardware hash, it can automatically register the device with Windows Autopilot.
For more information onabout how to automatically register devices for Windows Autopilot with Microsoft Intune, see Create a Windows Autopilot deployment profile and review the description of the Convert all targeted devices to Autopilot setting. See the following example:
Note
Using the setting Convert all targeted devices to Autopilot setting in the Windows Autopilot profile doesn't automatically convert existing hybrid Microsoft Entra devicedevices in the assigned groups into a Microsoft Entra device.devices. The setting only registers the devices in the assigned groups for the Windows Autopilot service. For more information, see Create a Windows Autopilot deployment profile.
Windows Autopilot for existing devices
\ No newline at end of file
When you use the Windows Autopilot for existing devices scenario is used, devicesscenario, you don't need to be preregisteredpreregister devices with Windows Autopilot. Instead, use a configuration file (AutopilotConfigurationFile.json) containing allthat contains the Windows Autopilot profile settings is used. The devicesettings. You can then be registeredregister the device with Windows Autopilot by using the same Convert all targeted devices to Autopilot setting.
\ No newline at end of file
\ No newline at end of file
@@ -1,6 +1,6 @@ --- layout: Conceptual-title: Automatic registration of existing devices | Microsoft Learn+title: Automatic Registration of Existing Devices | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/autopilot/automatic-registration author: iceorbital ms.author: acabello@@ -13,8 +13,8 @@ feedback_product_url: https://feedbackportal.microsoft.com/feedback/forum/ef1d6d feedback_system: Standard permissioned-type: public uhfHeaderId: MSDocsHeader-Windows-description: Automatically add devices to Windows Autopilot.-ms.date: 2025-06-13T00:00:00.0000000Z+description: Automatically register existing devices with Windows Autopilot through Intune or another MDM service. Learn the requirements and how to convert targeted devices.+ms.date: 2026-10-30T00:00:00.0000000Z ms.topic: how-to ms.collection: - M365-modern-desktop@@ -37,31 +37,33 @@ item_type: Content source_path: autopilot/automatic-registration.md cmProducts: - https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/4b132a0c-342a-42eb-91ff-8159e1ed413d+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/a72e95ff-4b4f-4cc1-90c6-7dcba67ff05f spProducts: - https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/f2b71146-ce8e-46a8-9965-8aa8b3aa8235+- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/24dc3ccd-591a-4415-a1fe-8759afafcb12 platformId: 7f28d1aa-c61e-c7e2-ac73-0de1aaaa386e --- -# Automatic registration of existing devices | Microsoft Learn+# Automatic Registration of Existing Devices | Microsoft Learn ## Requirements
-An existing device can automatically register if it's:
+An existing device can automatically register if it meets the following criteria:
-- Running a [supported version](/en-us/windows/release-information/) of Windows
+- Runs a [supported version](/en-us/windows/release-information/) of Windows
- Enrolled in a mobile device management (MDM) service such as Intune
- A corporate device that isn't already registered with Windows Autopilot
-For devices that meet these requirements, the MDM service can ask the device for the hardware hash. After it has that, it can automatically register the device with Windows Autopilot.
+For devices that meet these requirements, the MDM service can request the hardware hash from the device. After it has the hardware hash, it can automatically register the device with Windows Autopilot.
-For more information on how to automatically register devices for Windows Autopilot with Microsoft Intune, see [Create a Windows Autopilot deployment profile](profiles#create-a-windows-autopilot-deployment-profile) and review the description of the **Convert all targeted devices to Autopilot** setting. See the following example:
+For more information about how to automatically register devices for Windows Autopilot with Microsoft Intune, see [Create a Windows Autopilot deployment profile](profiles#create-a-windows-autopilot-deployment-profile) and review the description of the **Convert all targeted devices to Autopilot** setting. See the following example:
Note
-Using the setting **Convert all targeted devices to Autopilot** in the Windows Autopilot profile doesn't automatically convert existing hybrid Microsoft Entra device in the assigned groups into a Microsoft Entra device. The setting only registers the devices in the assigned groups for the Windows Autopilot service. For more information, see [Create a Windows Autopilot deployment profile](profiles#create-a-windows-autopilot-deployment-profile).
+Using the **Convert all targeted devices to Autopilot** setting in the Windows Autopilot profile doesn't automatically convert existing hybrid Microsoft Entra devices in the assigned groups into Microsoft Entra devices. The setting only registers the devices in the assigned groups for the Windows Autopilot service. For more information, see [Create a Windows Autopilot deployment profile](profiles#create-a-windows-autopilot-deployment-profile).
## Windows Autopilot for existing devices
-When the [Windows Autopilot for existing devices](existing-devices) scenario is used, devices don't need to be preregistered with Windows Autopilot. Instead, a configuration file (AutopilotConfigurationFile.json) containing all the Windows Autopilot profile settings is used. The device can then be registered with Windows Autopilot using the same **Convert all targeted devices to Autopilot** setting.\ No newline at end of file+When you use the [Windows Autopilot for existing devices](existing-devices) scenario, you don't need to preregister devices with Windows Autopilot. Instead, use a configuration file (AutopilotConfigurationFile.json) that contains the Windows Autopilot profile settings. You can then register the device with Windows Autopilot by using the **Convert all targeted devices to Autopilot** setting.\ No newline at end of file