2.4. Reflection Checkpoint
Key Takeaways
- Choose identity by ownership first: register personal devices, Entra join organization-owned devices, and keep hybrid join only for devices that still depend on on-premises AD and can reach a domain controller.
- Expect dynamic groups to lag; when apps and policies must arrive during setup, use enrollment time grouping, and prefer assignment filters for everyday Intune targeting.
- Match the enrollment method to ownership: ADE and the Android corporate modes for company devices, account-driven user enrollment and personal work profiles for BYOD — and know the 2026 changes (modern authentication only in Setup Assistant, web-based Android BYOD enrollment).
- Keep the two device limits apart: Entra's per-user maximum (default 50) counts identities, Intune's device limit restriction (1–15) counts enrollments and skips Entra join, Autopilot and DEM.
- Build admin access from role + members + scope groups + scope tags, add Multi Admin Approval for high-impact changes, and create a custom role for LAPS rotation.
- Compliance records a verdict; Conditional Access enforces it — after you create compliance policies, exclude break-glass and sync accounts, start in Report-only, and change the no-policy default to Not compliant.
Connecting Forward
Phase 3 builds on this foundation to provision and manage devices at scale. With join types, enrollment, groups and roles in place, you can deploy Windows with Autopilot and device preparation policies, provision Windows 365 Cloud PCs, shape devices with configuration profiles and assignment filters, extend management with the Intune advanced capabilities, and act on devices with remote actions such as wipe, BitLocker key rotation and the LAPS rotation you just delegated.
Self-Check Questions
- A company's sales staff use personal iPhones for email and company-bought Windows laptops that never visit the office. For each device type, which identity type and enrollment method would you choose, and what single fact in the scenario drove each choice?
- An admin with the Policy and Profile Manager role and a "Retail" scope tag can't see a compliance policy that a colleague created, but a Global Administrator sees everything regardless of tags. Explain both behaviors using the parts of a role assignment.
- Your Conditional Access policy requires a compliant device, yet a newly enrolled laptop with no compliance policy assigned opens Outlook without trouble. Trace the chain from compliance to Conditional Access and identify the setting that let it through.