1.3. Reflection Checkpoint
Key Takeaways
- Diagnose by layer: identity in Microsoft Entra ID, enrollment in Intune, then policy. Fix the lowest broken layer first.
- App protection policies are the one control that skips enrollment, which makes them the default for personal devices.
- Intune stores intent and devices pull it at check-in; use Sync for an immediate change and enrollment-time targeting when policies must arrive during setup.
- Don't mix user and device groups across include and exclude; use assignment filters to refine broad assignments.
- Compliance evaluates, Conditional Access enforces — and devices without a compliance policy are Compliant by default.
Connecting Forward
Phase 2 builds the bottom two layers properly: choosing a join type, grouping devices, enrolling every platform from Windows to Android, and setting up the roles, compliance policies and identity protections that everything else depends on.
Self-Check Questions
- A newly enrolled laptop got its Wi-Fi profile within minutes, but a laptop enrolled last month still hasn't received a change you made an hour ago. Explain the difference and what you would do about it.
- Why does Microsoft recommend changing Mark devices with no compliance policy assigned as to Not compliant in a tenant that uses Conditional Access?
- A requirement says "protect company data on employees' personal iPhones without managing the devices". Which layer does your answer operate on, and which layer does it skip?