2.1.3. Device Groups and Dynamic Membership Rules
💡 First Principle: A dynamic group is a saved query, not a live view. Microsoft Entra ID evaluates the rule asynchronously, after the device object and its properties exist, so membership always lags reality. Use dynamic groups when you need a reusable set of devices across services, and expect a delay; when something must apply during enrollment, you need a mechanism that doesn't wait for group evaluation.
Groups are how everything in Intune is targeted, so device groups are the plumbing behind every assignment you make. A few membership facts shape how you build them:
- Security groups can contain users or devices; Microsoft 365 groups can contain only users.
- A single dynamic rule can't mix users and devices, and a device rule can reference only device attributes — never the device owner's user attributes.
- You can't manually add or remove members of a dynamic group, and role-assignable groups can't be dynamic at all.
- Creating or editing a dynamic group requires at least the Groups Administrator role; the membership type is Dynamic User or Dynamic Device.
Licensing is a classic detail. Dynamic groups need Microsoft Entra ID P1 (or Intune for Education) for each unique user member, and the licenses must be owned in sufficient number rather than assigned. Microsoft is explicit that "no license is required for devices that are members of a dynamic membership group based on a device."
Writing device rules. The visual rule builder works only for user-based groups, so device rules are typed into the text box. The rules most worth recognizing:
device.objectId -ne null (all devices)
device.devicePhysicalIDs -any _ -startsWith "[ZTDId]" (all Autopilot devices)
device.devicePhysicalIds -any _ -eq "[OrderID]:179887111881" (one Autopilot order ID)
device.enrollmentProfileName -eq "DEP iPhones" (devices enrolled with a named profile)
device.deviceOwnership -eq "Company" (corporate-owned devices)
device.deviceOSType -startsWith "AndroidEnterprise" (Android Enterprise devices)
device.deviceTrustType -eq "AzureAD" (Entra joined devices)
| Attribute | Useful values | Why you'd use it |
|---|---|---|
devicePhysicalIds | [ZTDId], [OrderID], [PurchaseOrderId] | Group Autopilot-registered devices, all or by order |
enrollmentProfileName | The profile or policy name | Group devices by Apple ADE, Android Enterprise dedicated or Autopilot profile |
deviceOwnership | Personal, Company, Unknown | Separate corporate from personal (Intune shows Company as "Corporate") |
deviceTrustType | AzureAD, ServerAD, Workplace | Separate joined, hybrid joined and registered devices |
deviceOSType | Windows, iPhone, iPad, AndroidForWork | Group by platform |
deviceManagementAppId | Intune or Configuration Manager app ID | Separate Intune-managed from co-managed devices |
Some syntax rules catch people out. Values are compared without case sensitivity, but property names are case sensitive. Null checks use -eq null or -ne null, never -not with null. Operator precedence runs from comparison operators, then -not, -and, -or, and finally -any/-all. A rule body can be up to 3,072 characters, and a tenant can hold up to 15,000 dynamic groups. The old organizationalUnit attribute no longer adds devices, and memberOf (a rule based on membership of other groups) is still in preview.
Watching evaluation. A dynamic group's page shows its processing status — Evaluating, Processing, Update complete, Processing error, Update paused or Not started — and offers a Pause processing option. If pending updates can't be processed for more than 24 hours, an alert appears above All groups. Stale device and user objects slow processing down, which is one more reason to clean them up.
When not to use a dynamic group. Microsoft's current guidance is to prefer assignment filters for targeting Intune apps and policies, and to keep dynamic groups for needs that span other services — Conditional Access, group-based licensing and Autopilot profile assignment. Filters are evaluated at check-in, so they don't wait for group membership to be recalculated. Phase 3 covers filters in depth.
⚠️ Exam Trap: A dynamic device group does not pick up a newly enrolling device immediately, so policies and apps assigned to it can take hours to arrive. If a scenario says apps or policies must be present during enrollment, the answer is enrollment time grouping, which adds the device to a static security group as it enrolls so its assignments arrive on the first check-in. It works with Apple automated device enrollment, Windows Autopilot device preparation and Android Enterprise fully managed, corporate-owned work profile and dedicated enrollment. The static group must have the Intune Provisioning Client service principal as an owner, and it isn't supported with Android staging tokens.
Reflection Question: You build a dynamic device group with the rule device.enrollmentProfileName -eq "Warehouse Scanners" and assign the scanner app to it, yet new scanners finish setup without the app. Why does this happen, which Intune feature would make the app arrive during setup, and why does that feature need a static group rather than your dynamic one?