Microsoft 365 Contacts rule command
This membership rule command updates Microsoft 365 Dynamiс Group membership with the Microsoft 365 contacts that meet certain query criteria.
Membership Rule Command Settings
| Setting name | Description |
|---|---|
| Query criteria | Query criteria are sent to the target platform with other query parameters to reduce the number of returned objects and may improve query performance. |
| Post-query filter |
To hide unwanted data based on criteria, not supported by the target system in the query criteria, set the filtering conditions here. Example: filter by the found object Distinguished Name. TIP: For optimal performance, use the Query criteria above to filter objects whenever possible. |
| Contact sync status | Specify the contact sync status. |
| Job title | Specify contact attributes. |
| Department | |
| Company Name | |
| More Parameters | |
| Initialization Script |
Usually, rules use query criteria to limit the query search scope. It improves the performance of the executed rule. Due to PowerShell limitations, it is not possible to use calculated expressions in query criteria. That is the point where the initialization script can help. You can initialize a global variable in this setting and then use it in query criteria. IMPORTANT:
To use a variable, declared in the initialization script, in
the query scope, it must be global: |
| MS Graph query condition (OData) |
By default, Query criteria are used. But when the MS Graph query condition is specified, it overrides the Query criteria setting. See this article for examples: How to use Query Builder dialog for Query Criteria and Filter rule settings. |
| MaxResults | The maximum number of contacts returned from Microsoft 365. The default value is taken from the Maximum returned results setting on HOME > CONFIGURATION >Microsoft 365 extension settings. |
Related Articles
- Creating Dynamic Groups
- Membership Rule Commands for Active Directory and Microsoft 365 Dynamic Groups
Change History
| Version | Notes |
|---|---|
| 10.3.0 | The command has been introduced in the product. |
Comments
0 comments
Please sign in to leave a comment.