1.2. How Intune Turns Intent into Device State
💡 First Principle: Intune stores intent; devices apply it. You declare what a group of devices should look like, and each device, on its own schedule, asks Intune what it should be doing, applies what it's given and reports back. Timing, conflicts and troubleshooting all follow from that pull-based design.
Why care? Most "it didn't work" scenarios are timing or targeting problems, not configuration mistakes. The policy was right; the device hadn't checked in, wasn't in the group yet, or got two policies that disagreed. Knowing how delivery works lets you pick "sync the device" or "use enrollment time grouping" over "recreate the policy".
Think of Intune as a delivery depot holding parcels addressed to groups. Devices are couriers who drop by on a schedule to collect whatever is addressed to them. A doorbell (a push notification) can ask a courier to come early, but nothing is delivered until the courier arrives — and when they report back, the depot learns whether the parcel was accepted.
⚠️ Common Misconception: Many people believe Intune pushes a policy the moment you save it. Devices pull policy when they check in. Intune sends a notification that prompts a check-in and the Sync action forces one, but after the first hours of enrollment a Windows device's routine check-in settles to about every eight hours, so an offline or sleeping device gets the change later.