Compare Windows Autopilot device preparation and Windows Autopilot
In brief
The comparison now documents that device preparation devices can be associated with a tenant before enrollment, while Windows Autopilot devices can be registered. It also updates the explanation of deployment selection for Autopilot-registered devices.
What Intune admins need to know
Admins can use the updated comparison to understand pre-enrollment device binding and how deployment selection is described.
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.
title: Compare Windows Autopilot device preparation and Windows Autopilot
description: Compare Windows Autopilot device preparation and Windows Autopilot features and when to use each.
ms.date: 04/02/202508/07/2026
ms.topic: overview
ms.collection:
- M365-modern-desktop
| Features |
- Support for Government Community Cloud High (GCCH) and Department of Defense (DoD) environments.
- Faster, more consistent provisioning experience.
- Near real-time monitoring and troubleshooting info.
- Support for multiple device types (HoloLens, Teams Meeting Room).
- Many customization options for the provisioning experience.
- User-driven.
- Automatic.
- Microsoft Entra join.
- Microsoft Entra join.
- Microsoft Entra hybrid join.
|Device| Device registration required? | No. | Yes. | | Is it possible to bind devices to my tenant before enrollment? | Yes, you can associate devices. | Yes, you can register devices. | | What do admins need to configure? |- Windows Autopilot device preparation policy.
- Device security group with Intune Provisioning Client as owner.
- Windows Autopilot deployment profile.
- Enrollment Status Page (ESP).
- Device-based only during the out-of-box experience (OOBE).
- Up to 25 essential applications (line-of-business (LOB), Win32, Microsoft Store, Microsoft 365).
- Up to 10 essential PowerShell scripts.
- Device-based during device ESP.
- User-based during user ESP.
- Up to 100 applications.
- Shows all Windows Autopilot device preparation deployments.
- More data available.
- Near real-time.
- Only shows Windows Autopilot registered devices.
- Not real-time.
- Windows 11, version 24H2 or later.
- Windows 11, version 23H2 with KB5035942 or later.
- Windows 11, version 22H2 with KB5035942 or later.
- All
currently supportedcurrently supported versions of Windows 11 General Availability Channel. - All
currently supportedcurrently supported versions of Windows 10 General Availability Channel.
Which Windows Autopilot solution to use
Using Windows Autopilot device preparation and Windows Autopilot concurrently
Windows Autopilot device preparation and Windows autopilotAutopilot can be used concurrently and side by side within an organization. However, any one device in an environment can only run one of the two solutions. For a device that's registered with Windows Autopilot, which deployment runs depends on the device's association state. If the device isn't associated with the tenant, the Windows Autopilot profiles takeprofile takes precedence. If the device is associated, device association takes precedence overand the Windows Autopilot device preparation policies. If a Windows Autopilot registered device needs to go through adeployment runs. To use Windows Autopilot device preparation deployment, it muston a registered device without associating it, first be removed as a Windows Autopilot device. For more information, see deregister the device.
@@ -1,7 +1,7 @@ --- title: Compare Windows Autopilot device preparation and Windows Autopilot description: Compare Windows Autopilot device preparation and Windows Autopilot features and when to use each.-ms.date: 04/02/2025+ms.date: 08/07/2026 ms.topic: overview ms.collection: - M365-modern-desktop@@ -19,12 +19,13 @@ appliesto: | Features | <ul><li>Support for Government Community Cloud High (GCCH) and Department of Defense (DoD) environments.</li><li>Faster, more consistent provisioning experience.</li><li>Near real-time monitoring and troubleshooting info.</li></ul> | <ul><li>Support for multiple device types ([HoloLens](/hololens/hololens2-autopilot), [Teams Meeting Room](/microsoftteams/rooms/autopilot-autologin)).</li><li>Many customization options for the provisioning experience.</li></ul> | | Supported modes | <ul><li>[User-driven](tutorial/user-driven/entra-join-workflow.md).</li><li>Automatic.</li></ul> | <ul><li>[User-driven](../tutorial/user-driven/azure-ad-join-workflow.md).</li><li>[Pre-provisioned](../tutorial/pre-provisioning/azure-ad-join-workflow.md).</li><li>[Self-deploying](../tutorial/self-deploying/self-deploying-workflow.md).</li><li>[Existing devices](../tutorial/existing-devices/existing-devices-workflow.md).</li></ul>| | Join types supported | <ul><li>Microsoft Entra join.</li></ul> | <ul><li>Microsoft Entra join.</li><li>Microsoft Entra hybrid join.</li></ul> |-|Device registration required? | No. | Yes. |+| Device registration required? | No. | Yes. |+| Is it possible to bind devices to my tenant before enrollment? | Yes, you can [associate devices](tutorial/user-driven/entra-join-device-association.md). | Yes, you can [register devices](../registration-overview.md). | | What do admins need to configure? | <ul><li>Windows Autopilot device preparation policy.</li><li>Device security group with **Intune Provisioning Client** as owner.</li></ul> | <ul><li>Windows Autopilot deployment profile.</li><li>Enrollment Status Page (ESP).</li></ul> | | What configurations can be delivered during provisioning? | <ul><li>Device-based only during the out-of-box experience (OOBE).</li><li>Up to 25 essential applications (line-of-business (LOB), Win32, Microsoft Store, Microsoft 365).</li><li>Up to 10 essential PowerShell scripts.</li></ul> | <ul><li>Device-based during device ESP.</li><li>User-based during user ESP.</li><li>Up to [100 applications](/intune/intune-service/enrollment/windows-enrollment-status#block-access-to-a-device-until-a-specific-application-is-installed).</li></ul> | | Reporting & troubleshooting | Windows Autopilot device preparation deployment report:<ul><li>Shows all Windows Autopilot device preparation deployments.</li><li>More data available.</li><li>Near real-time.</li></ul> | Windows Autopilot deployment report:<ul><li>Only shows Windows Autopilot registered devices.</li><li>Not real-time.</li></ul> | | Supports LOB and Win32 applications in same deployment? | Yes. | No. |-| Supported versions of Windows | <ul><li>Windows 11, version 24H2 or later.</li><li>Windows 11, version 23H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later.</li><li> Windows 11, version 22H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later.</li></ul> | <ul><li>All [currently supported](/windows/release-health/supported-versions-windows-client#windows-11-supported-versions) versions of Windows 11 General Availability Channel.</li><li>All [currently supported](/windows/release-health/supported-versions-windows-client#windows-10-supported-versions) versions of Windows 10 General Availability Channel.</li></ul> |+| Supported versions of Windows | <ul><li>Windows 11, version 24H2 or later.</li><li>Windows 11, version 23H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later.</li><li> Windows 11, version 22H2 with [KB5035942](https://support.microsoft.com/topic/march-26-2024-kb5035942-os-builds-22621-3374-and-22631-3374-preview-3ad9affc-1a91-4fcb-8f98-1fe3be91d8df) or later.</li></ul> | <ul><li>All [currently supported](/windows/release-health/supported-versions-windows-client#windows-11-supported-versions-by-servicing-option) versions of Windows 11 General Availability Channel.</li><li>All [currently supported](/windows/release-health/supported-versions-windows-client#windows-10-supported-versions-by-servicing-option) versions of Windows 10 General Availability Channel.</li></ul> | ## Which Windows Autopilot solution to use @@ -61,4 +62,4 @@ In general, the following are some of the major factors when considering between ## Using Windows Autopilot device preparation and Windows Autopilot concurrently -Windows Autopilot device preparation and Windows autopilot can be used concurrently and side by side within an organization. However, any one device in an environment can only run one of the two solutions. Windows Autopilot profiles take precedence over Windows Autopilot device preparation policies. If a Windows Autopilot registered device needs to go through a Windows Autopilot device preparation deployment, it must first be removed as a Windows Autopilot device. For more information, see [Deregister a device](../registration-overview.md#deregister-a-device).+Windows Autopilot device preparation and Windows Autopilot can be used concurrently and side by side within an organization. However, any one device in an environment can only run one of the two solutions. For a device that's registered with Windows Autopilot, which deployment runs depends on the device's association state. If the device isn't associated with the tenant, the Windows Autopilot profile takes precedence. If the device is associated, device association takes precedence and the Windows Autopilot device preparation deployment runs. To use Windows Autopilot device preparation on a registered device without associating it, first [deregister the device](../registration-overview.md#deregister-a-device).