Windows Autopilot
Device enrollment

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.
    | | | Supported modes | | | | Join types supported |
    • 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).
    | | What configurations can be delivered during provisioning? |
    • 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.
    | | Reporting & troubleshooting | Windows Autopilot device preparation deployment report:
    • Shows all Windows Autopilot device preparation deployments.
    • More data available.
    • Near real-time.
    | Windows Autopilot deployment report:
    • Only shows Windows Autopilot registered devices.
    • Not real-time.
    | | Supports LOB and Win32 applications in same deployment? | Yes. | No. | | Supported versions of Windows |
    • Windows 11, version 24H2 or later.
    • Windows 11, version 23H2 with KB5035942 or later.
    • Windows 11, version 22H2 with KB5035942 or later.
    | |

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.

Daily Intune.Admin.News

Get daily email updates

Get a concise summary of the latest Microsoft Intune updates delivered straight to your inbox.

Loading the secure signup form…