1.2.1. Check-In, Assignment, and Conflict
💡 First Principle: A policy reaches a device only when three things line up — the device is in a targeted group, it isn't excluded or filtered out, and it checks in. When two policies try to set the same thing differently, Intune doesn't silently pick a winner for configuration settings; it reports a conflict, because guessing wrong on a security setting is worse than not applying it.
Check-in timing. A newly enrolled Windows device checks in frequently at first — every 3 minutes for 15 minutes, then every 15 minutes for 2 hours — and then about every 8 hours. That front-loading is why a freshly provisioned device picks up its policies quickly while an established device can take hours. When you need a change now, the Sync remote action tells the device to check in immediately. Phase 3 covers the remote actions in full.
Targeting. Policies and apps are assigned to groups. Assign to user groups when a setting should follow the person to every device they enroll; assign to device groups when it belongs to the hardware regardless of who signs in, such as a kiosk or a shared device. You can include and exclude groups, with one firm rule: don't mix types across include and exclude. Including user groups while excluding device groups, or the reverse, isn't supported and produces unpredictable results.
Assignment filters refine an assignment without new groups. You still assign to a group (or to All users or All devices), and a filter then includes or excludes devices by properties such as operating system version, manufacturer or ownership, evaluated at check-in. Because filters don't depend on group membership being recalculated, they avoid the delay of dynamic groups, which Phase 2 and Phase 3 explore.
| Targeting tool | Best for | Watch out for |
|---|---|---|
| User group | Settings and apps that follow the person | Applies to every device that user enrolls |
| Device group | Hardware-bound settings, kiosks, shared devices | Dynamic membership takes time to evaluate |
| Assignment filter | Narrowing a broad assignment by device property | Refines an assignment; can't target on its own |
| Exclude group | Carving a pilot or exception out of a broad assignment | Must be the same type (user or device) as the include |
Conflicts. When two configuration policies set the same setting to different values, Intune shows the setting as conflict in reporting and the conflict must be resolved manually — usually by removing the setting from one policy or narrowing an assignment. App protection policies are the exception: when they conflict, the most restrictive value wins (except for numeric fields). Expect the exam to test that difference.
⚠️ Exam Trap: "Wait for the next check-in" and "sync the device" are both reasonable, but if the scenario says the change must apply immediately to a specific device, Sync is the answer. If it says policies must apply during enrollment, neither is — the answer is a targeting change such as enrollment time grouping.
Reflection Question: A firewall setting appears as "Conflict" on a group of laptops after you assign a second endpoint security policy. Why doesn't Intune simply apply the newer policy, and what are your two ways to resolve it?