Windows Autopilot OEM Registration Process | Microsoft Learn
In brief
The article updates its title and description, replaces “OEM” with “manufacturer” throughout, and refreshes its metadata. It continues to describe manufacturer registration, device guidelines, and Microsoft Entra Global Administrator approval.
What Intune admins need to know
No administrator action is indicated; the updated wording clarifies the manufacturer’s role in registration.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
Windows Autopilot OEM registration processRegistration Process | Microsoft Learn
Device registration process
When devices are purchased from an OEM, the OEMmanufacturer can automatically register the devices with the Windows Autopilot. For the list of OEMsmanufacturers that support registration, see the Participant device manufacturers and resellers section of the Windows Autopilot page.
Note
While the hardware hashes, also known as hardware IDs, are generated as part of the OEM device manufacturing process, the hardware hashes aren't normally provided directly to customers or Cloud Solution Partners (CSPs). Instead, the OEMmanufacturer should register devices on the customer's behalf. In cases where CSPs register devices, OEMsmanufacturers might provide PKID information to those partners to support the device registration process.
OEMsManufacturers must follow device guidelines for Windows Autopilot devices.
Service data
Microsoft manages and maintains Windows Autopilot. This service provides the backend database that associates hardware hashes with customer tenants. When an OEMmanufacturer registers devices for a customer, they're writing that data to this database and not directly to the customer's tenant. No permissions to the customer's tenant are granted or required for OEMsmanufacturers to register devices on the customer's behalf.
Customer consent
Before an OEMmanufacturer can register devices for an organization, the organization's Microsoft Entra Global Administrator must approve the OEM. For more information, see OEM authorization.
Important
@@ -1,6 +1,6 @@ --- layout: Conceptual-title: Windows Autopilot OEM registration process | Microsoft Learn+title: Windows Autopilot OEM Registration Process | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/autopilot/oem-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: How OEMs add devices to Windows Autopilot.-ms.date: 2025-06-13T00:00:00.0000000Z+description: Windows Autopilot OEM registration lets manufacturers register devices on your behalf. Learn how the process works in your tenant.+ms.date: 2026-10-30T00:00:00.0000000Z ms.topic: how-to ms.collection: - M365-modern-desktop@@ -43,25 +43,25 @@ spProducts: platformId: 969968b6-9bef-5401-c980-6da760206ad0 --- -# Windows Autopilot OEM registration process | Microsoft Learn+# Windows Autopilot OEM Registration Process | Microsoft Learn ## Device registration process
-When devices are purchased from an OEM, the OEM can automatically register the devices with the Windows Autopilot. For the list of OEMs that support registration, see the **Participant device manufacturers and resellers** section of the [Windows Autopilot page](https://aka.ms/windowsautopilot).
+When devices are purchased from an OEM, the manufacturer can automatically register the devices with the Windows Autopilot. For the list of manufacturers that support registration, see the **Participant device manufacturers and resellers** section of the [Windows Autopilot page](https://aka.ms/windowsautopilot).
Note
-While the hardware hashes, also known as hardware IDs, are generated as part of the OEM device manufacturing process, the hardware hashes aren't normally provided directly to customers or Cloud Solution Partners (CSPs). Instead, the OEM should register devices on the customer's behalf. In cases where CSPs register devices, OEMs might provide PKID information to those partners to support the device registration process.
+While the hardware hashes, also known as hardware IDs, are generated as part of the device manufacturing process, the hardware hashes aren't normally provided directly to customers or Cloud Solution Partners (CSPs). Instead, the manufacturer should register devices on the customer's behalf. In cases where CSPs register devices, manufacturers might provide PKID information to those partners to support the device registration process.
-OEMs must follow [device guidelines](autopilot-device-guidelines) for Windows Autopilot devices.
+Manufacturers must follow [device guidelines](autopilot-device-guidelines) for Windows Autopilot devices.
### Service data
-Microsoft manages and maintains Windows Autopilot. This service provides the backend database that associates hardware hashes with customer tenants. When an OEM registers devices for a customer, they're writing that data to this database and not directly to the customer's tenant. No permissions to the customer's tenant are granted or required for OEMs to register devices on the customer's behalf.
+Microsoft manages and maintains Windows Autopilot. This service provides the backend database that associates hardware hashes with customer tenants. When an manufacturer registers devices for a customer, they're writing that data to this database and not directly to the customer's tenant. No permissions to the customer's tenant are granted or required for manufacturers to register devices on the customer's behalf.
### Customer consent
-Before an OEM can register devices for an organization, the organization's Microsoft Entra Global Administrator must approve the OEM. For more information, see [OEM authorization](registration-auth#oem-authorization).
+Before manufacturer can register devices for an organization, the organization's Microsoft Entra Global Administrator must approve the OEM. For more information, see [OEM authorization](registration-auth#oem-authorization).
Important