3.2.4. Targeting with Assignment Filters and Enrollment Time Grouping
💡 First Principle: Group membership is calculated by Microsoft Entra ID on its own schedule, so anything that depends on a dynamic group arrives late — and for a new device, "late" means after the user has already started working. Assignment filters and enrollment time grouping both remove that wait, in different ways: a filter checks the device's own properties at check-in, and enrollment time grouping places the device into a static group at the moment it enrolls.
Assignment filters refine an assignment; they never replace one. You still assign the policy or app to a group — or to All users or All devices — and then choose a filter mode: Include filtered devices or Exclude filtered devices. Intune evaluates the filter at enrollment, at check-in and whenever policy evaluates, without any group membership processing, so targeting isn't affected by group size or by how long Entra takes to recalculate a dynamic group.
There are two filter types. Managed devices filters target enrolled devices on Android, iOS/iPadOS, macOS and Windows. Managed apps filters apply only to app protection and app configuration policies. A tenant can have up to 200 filters of up to 3,072 characters each, created at Tenant administration > Assignment filters; a filter in use can't be deleted.
The rule syntax is (device.property operator value), and properties, operators and values are case-insensitive. For example:
(device.deviceOwnership -eq "Corporate") -and (device.operatingSystemSKU -eq "Enterprise")
Useful properties include manufacturer, model, deviceOwnership, enrollmentProfileName (the Autopilot, ADE or Google enrollment profile name), operatingSystemVersion, operatingSystemSKU and, on Windows, deviceTrustType (joined, registered or hybrid joined).
Where filters don't work. Filters are supported on most Windows profiles, update rings, Remediations and most endpoint security policies. They're not supported for Windows security baselines, feature updates, PowerShell scripts, macOS shell scripts, custom compliance, policy sets or the wired network profile. For targeting outside Intune policy — Conditional Access, group-based licensing or Autopilot profile assignment — you still need dynamic groups.
Enrollment time grouping solves a different problem: getting required apps and policies onto a device during setup. Without it, devices are grouped after enrollment by inventory properties and group tags, and it can take up to 8 hours to receive everything. With it, the device joins a static Entra security group during enrollment, so whatever is assigned to that group arrives at first check-in. The group must be a static (assigned) security group owned by the Intune Provisioning Client — the same requirement as device preparation, which is built on this feature.
- Supported enrollment methods: Apple ADE (iOS/iPadOS, tvOS, visionOS), macOS ADE, Windows Autopilot device preparation and Android Enterprise (fully managed, corporate-owned work profile and dedicated — but not the staging token).
- One static group per enrollment policy, and it applies only to new enrollments.
- The group must be within the admin's role scope groups, and admins need the enrollment time device membership assignment permission for that platform.
- Failures appear in Devices > Monitor > Enrollment time grouping failures.
Include and exclude combinations. Microsoft documents which mixes work:
| Include | Exclude | Supported? |
|---|---|---|
| User groups | User groups | Yes |
| Device groups | Static device groups | Yes |
| Device groups | Dynamic device groups | Partially — membership latency can deploy unwanted policies |
| Device groups | User groups | No — devices of excluded users still get the policy |
| User groups | Device groups | No |
Microsoft's guidance for latency-sensitive or userless targeting is to assign to All devices (or to user groups) with an assignment filter rather than to a dynamic device group, and to use filters rather than dynamic device groups for exclusions.
⚠️ Exam Trap: Because filters use rule syntax that looks like dynamic group rules, it's tempting to think a filter can target devices on its own. It can't. A filter only includes or excludes devices from an assignment that already targets a group (or All users or All devices). An answer that says "create a filter and assign the policy to it" is wrong; "assign to All devices with an include filter" is right.
Reflection Question: New Android Enterprise fully managed devices must receive a Wi-Fi profile before the user finishes setup, but only devices from one manufacturer should get a second, vendor-specific profile. Which targeting tool handles each requirement, and why not use a dynamic device group for either?