Windows Autopilot
Device enrollmentOverview
In brief
The documentation now states that device preparation supports GCCH and DoD environments, but device association isn't available in sovereign clouds. It also explains TPM-backed association, policy precedence, corporate ownership, naming, and OOBE customization.
What Intune admins need to know
Administrators in sovereign clouds should not plan to use device association. Others can better understand its enrollment behavior and available customizations.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
For more information, see [Windows Autopilot device preparation reporting and monitoring](reporting-monitoring).
Support for Government CommunityCloud
High (GCCH) and Department of Defense (DoD)environments.Windows Autopilot device preparation supports Government Community Cloud High (GCCH) and Department of Defense (DoD) environments.
The device association capability isn't yet available in sovereign cloud environments.
Important
Device association
Windows AutopilotDevice association uses a device preparation supports device association, which binds's Trusted Platform Module (TPM)-backed identity to establish a physical Windows 11 device totrusted relationship with your tenant before enrollment. Associated devices are automatically markedThe association is stored in the device's Unified Extensible Firmware Interface (UEFI) firmware and verified during onboarding.
Use device association to:
- Assign a device preparation policy directly to a device, regardless of which user signs in. A device-based policy assignment takes precedence over a user-based assignment.
- Automatically mark the device as corporate-
ownedowned. - Apply a device name template during enrollment.
- Customize OOBE settings, such as language and
can receive device-targeted policy assignmentskeyboard configuration, andadditional OOBE customizations.hide selected setup pages.
Device association is optional. For more information,the full capabilities and lifecycle, see Overview of Windows Autopilot device association.
Tutorial
@@ -101,7 +101,12 @@ New features in Windows Autopilot device preparation include: - Deployment time
For more information, see [Windows Autopilot device preparation reporting and monitoring](reporting-monitoring).
-- **Support for Government Community Cloud High (GCCH) and Department of Defense (DoD) environments**. Windows Autopilot device preparation supports [GCCH and DoD](/en-us/intune/fundamentals/government-service) environments.
+
+### Cloud environments
+
+Windows Autopilot device preparation supports [Government Community Cloud High (GCCH) and Department of Defense (DoD)](/en-us/intune/fundamentals/government-service) environments.
+
+The device association capability isn't yet available in sovereign cloud environments.
Important
@@ -177,7 +182,16 @@ Windows Autopilot device preparation only requires corporate identifiers for Win
### Device association
-Windows Autopilot device preparation supports device association, which binds a physical Windows 11 device to your tenant before enrollment. Associated devices are automatically marked as corporate-owned and can receive device-targeted policy assignments and additional OOBE customizations. For more information, see [Overview of Windows Autopilot device association](device-association/overview).
+Device association uses a device's Trusted Platform Module (TPM)-backed identity to establish a trusted relationship with your tenant before enrollment. The association is stored in the device's Unified Extensible Firmware Interface (UEFI) firmware and verified during onboarding.
+
+Use device association to:
+
+- Assign a device preparation policy directly to a device, regardless of which user signs in. A device-based policy assignment takes precedence over a user-based assignment.
+- Automatically mark the device as corporate-owned.
+- Apply a device name template during enrollment.
+- Customize OOBE settings, such as language and keyboard configuration, and hide selected setup pages.
+
+Device association is optional. For the full capabilities and lifecycle, see [Overview of Windows Autopilot device association](device-association/overview).
## Tutorial