CASE STUDY 002 · ENDPOINT MANAGEMENT
Windows Autopilot & Intune enrollment
In progressA physical Windows 11 Autopilot lab investigating Microsoft Entra join, user sign-in and Intune management.
This case is a curated public summary; private source records are not directly accessible to visitors.
Case study
Evidence snapshot
Summarized observations from the documented lab. No private logs or tenant identifiers are included.
| Check | Recorded result | Evidence status |
|---|---|---|
| Microsoft Entra join | AzureAdJoined = YES; DomainJoined = NO | User-observed |
| User sign-in / PRT | AzureAdPrt = YES | User-observed |
| Intune MDM enrollment | Device visible; Managed by = Microsoft Intune | User-observed |
| ESP completion | Outcome not established | Unverified |
| Configuration and compliance | Effective policy results still pending | Unverified |
READ-ONLY COMMAND USED IN LAB
dsregcmd /statusApproach and tools
Inspected Autopilot profile targeting, enrollment restrictions and ESP settings. Completed user-driven Windows setup, signed in with the selected lab account and verified local device trust and MDM indicators.
Evidence and validation
On 3 November 2026, the user observed AzureAdJoined = YES, DomainJoined = NO and AzureAdPrt = YES via dsregcmd. The Windows device appeared in Intune with Managed by = Microsoft Intune. These confirm Entra join, user SSO readiness and Intune MDM visibility. ESP completion has not been established.
Result and limitations
Core Microsoft Entra join and Intune MDM enrollment confirmed by user observation. Effective compliance and configuration policy outcomes, application enforcement and actual ESP result remain to be tested.
Lessons learned
Validate the device trust state, user PRT and MDM status separately. A reachable desktop alone is insufficient; policy application requires additional per-device verification.