Windows Autopilot
Device enrollment

Requirements for Windows Autopilot device association | Microsoft Learn

In brief

The requirements page now includes a Hardware category and explicitly requires physical devices with TPM 2.0 enabled and healthy, not in Reduced Functionality Mode, and compliant with FIPS 186-3 or newer and TLS 1.3.

What Intune admins need to know

Administrators should validate device hardware and TPM compatibility before using Windows Autopilot device association.

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.

layout: Conceptual title: Requirements for Windows Autopilot device association | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/autopilot/device-preparation/device-association/requirements author: iceorbitalmadakeva ms.author: acabello ms.reviewer: madakeva ms.service: windows-client ms.subservice: autopilot ms.suite: ems feedback_system: Standard permissioned-type: public uhfHeaderId: MSDocsHeader-Windows description: Software, hardware, networking, licensing, and RBAC requirements for Windows Autopilot device association. ms.date: 2026-08-25T00:10-01T00:00:00.0000000Z ms.collection:

  • M365-modern-desktop ms.topic: article

Requirements for Windows Autopilot device association | Microsoft Learn

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

  • Software - OS requirements.
  • Hardware - Physical device and Trusted Platform Module (TPM) requirements.
  • Networking - Networking requirements.
  • Licensing - Licensing requirements.
  • RBAC - RBAC permissions required for Windows Autopilot device association.

Software

Software requirements

Important

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

Windows 11

Trusted Platform Module (TPM)

Hardware

Hardware requirements

Important

Device association requires a physical device—virtual. 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.

Trusted Platform Module (TPM)

TPM attestation is enforced during association: device association uses the TPM to attest the device's identity before enrollment.

TPM requirements:

  • Each device must have TPM 2.0, enabled and in a good state.
  • The TPM shouldn't be in Reduced Functionality Mode.
  • TPM must be FIPS 186-3 or newer compliant.
  • TPM must support TLS 1.3.

Networking

Networking requirements

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…