Windows Cloud Enrollment: Microsoft Entra Join and Intune Enrollment – Part 1

Estimated reading and study time: 50–65 minutes. Allow time to review 56 slides, inspect the evidence and absorb the concepts. This estimate excludes reproducing the procedures and waiting for installation, synchronization or policy delivery.

Part 1 of LAB-ENR-01 follows Microsoft Entra join and automatic Intune enrollment for an existing Windows endpoint. It brings together tenant prerequisites, enrollment restrictions, the resulting device identity and the organizational user’s PRT, giving readers a basis for comparing client state with cloud records.

This walkthrough focuses on identity and enrollment. Compliance and Windows Hello remain follow-up items and should not be inferred from a successful join or the presence of an Intune device record.

Related learning: Continue with Part 2: Policies, Security and Corporate Branding for policy delivery, compliance and local encryption observations. Read Autopilot requirements — conceptual guide to compare this existing-device enrollment route with provisioning through Autopilot, then see hardware hash registration and profile assignment for the separate Autopilot preparation workflow.

Official documentation: Use Microsoft’s Windows automatic MDM enrollment guidance for tenant configuration and dsregcmd reference to interpret identity and user SSO state. Consult Autopilot requirements when comparing this enrollment route with device provisioning.