Build Microsoft Intune assignment filter rule syntax by picking properties and operators.
Property names, operators and value constraints follow the official reference, so invalid combinations error out immediately.
Load a common filter
“+ Add group” creates a nested set of conditions wrapped in parentheses. The top-left selector changes how each group joins its children.
Syntax
([entity].[property name] [operation] [value]) — similar in shape to Entra dynamic groups.
Properties, operators and values are case insensitive
Parentheses and nesting are supported — in Intune itself, using nesting disables the basic rule builder and leaves only the rule syntax editor. Here you can build and edit nesting with groups
Null / $Null may only be used with -eq / -ne
Up to 200 filters per tenant, 3,072 characters per filter
Operators
Operator
Meaning
Value shape
-and / -or
Combine conditions
—
-eq / -ne
Equals / not equals
string, array, Null
-gt / -lt / -ge / -le
Comparison
operatingSystemVersion only
-startsWith
Begins with
string
-contains / -notContains
Contains / does not contain
string
-in / -notIn
In array / not in array
["a","b"]
Available device properties
Deployment notes
A filter is a refinement, not a group — you layer it onto an assignment in Include / Exclude mode
Evaluation timing — at enrollment, at check-in, and whenever a policy evaluates. No group-membership processing delay like dynamic groups have
Filters vs dynamic groups — if you need cross-workload targeting (Conditional Access, licensing) or Autopilot profile assignment, use dynamic groups; use filters for Intune-specific device targeting
Managed-app filters — apply only to app protection policies and app configuration policies, not to compliance or device configuration profiles
Android device administrator (DA) is deprecated — unavailable on GMS devices; migrating to another management option is recommended