Requirements for Windows Autopilot device association

The list of requirements for Windows Autopilot device association is organized into four categories:

• Software - OS requirements.
• Networking - Networking requirements.
• Licensing - Licensing requirements.
• RBAC - RBAC permissions required for Windows Autopilot device association.

Select the appropriate tab to see the relevant requirements:

Software

Software requirements

Important

Device association requires a physical device. Virtual machines aren't supported.

Windows 11

• Windows 11, version 25H2 with KB5120998 or later.
• Windows 11, version 24H2 with KB5120998 or later.

The following editions are supported:

• Windows 11 Pro.
• Windows 11 Pro Education.
• Windows 11 Pro for Workstations.
• Windows 11 Enterprise.
• Windows 11 Education.
• Windows 11 Enterprise LTSC.

Trusted Platform Module (TPM)

Device association requires a physical device—virtual machines aren't supported. Each device must have TPM 2.0, enabled and in a good state. The TPM shouldn't be in Reduced Functionality Mode. TPM attestation is enforced during association: device association uses the TPM to attest the device's identity before enrollment.

Networking

Networking requirements

Device association builds on Windows Autopilot device preparation and has the same baseline networking requirements. For the full list of endpoints and network configuration, see Windows Autopilot device preparation requirements.

In addition to the baseline requirements, allow HTTPS access over TCP port 443 to the following endpoints:

• https://ztd.dds.microsoft.com
• https://peapdamaa1.eus2.attest.azure.net
• https://peapdamaa2.wus2.attest.azure.net
• https://peapdamaa3.cus.attest.azure.net
• https://peapdamaa5.cus.attest.azure.net
• https://peapdamaa6.neu.attest.azure.net
• https://peapdamaa7.weu.attest.azure.net
• https://peapdamaa8.sasia.attest.azure.net
• https://peapdamaa9.eau.attest.azure.net
• https://peapdamaa19.wus2.attest.azure.net
• https://peapdamaa86.cin.attest.azure.net
• https://peapdamaa89.jpe.attest.azure.net
• https://peapdamaa93.weu.attest.azure.net

Licensing

Licensing requirements

Device association is part of Windows Autopilot device preparation and has the same licensing requirements. For the full list of supported subscriptions, see Windows Autopilot device preparation requirements.

RBAC

Required RBAC permissions

The following role-based access control (RBAC) permissions are required in an Intune role for Windows Autopilot device association.

Required for configuring the device preparation policy

• Device configurations
  • Read
  • Delete
  • Create
  • Update
• Enrollment programs
  • Enrollment time device membership assignment
• Managed apps
  • Read
• Mobile apps
  • Read
• Organization
  • Read

Required for managing associated devices

• Enrollment programs
  • Read device
  • Create device
  • Delete device
• Device configurations
  • Assign

To create a custom role with these permissions for use with Windows Autopilot device association:

1. Sign in to the Microsoft Intune admin center.
2. Select Tenant administration > Roles.
3. Select Create > Intune role.
4. On the Basics page, enter a name and description for the custom role, and then select Next.
5. On the Permissions page, set each of the permissions listed previously to Yes. Leave all other permissions at the default of No.
6. On the Scope tags page, select Next.
7. On the Review + create page, verify that all permissions are correct, and then select Create.

The new custom role can now be assigned to users who manage Windows Autopilot device association. For more information, see Role-based access control (RBAC) with Microsoft Intune.

Next steps

Tutorial: Set up Windows Autopilot device preparation with device association