This setting defines the search query scope. To improve query performance, limit the scope to a specific OU.

IMPORTANT: To test the rule configuration, limit the rule scope to an OU that contains test accounts or objects and use the Preview feature.

Query criteria are sent with the query and may improve query performance.

TIP: For additional information on the criteria builder, see the How to use Query Builder dialog for Query Criteria and Filter rule settings.

Specify user sync status.

• Synced only - AD users who also have MS 365 accounts.

• Show all - both AD only users and users who also have MS 365 accounts.

Specify the number of days for the last Active Directory logon. You can also set Any or Never logged on.

Specify the number of days since a user's last successful logon of any type (Interactive or Non-Interactive) in the Microsoft 365 environment.

Use '0' and remove the lastSuccessfulSignInDays, lastSuccessfulSignInDateTime attributes from the Other Query Settings>Properties to display and System properties settings below to disable this check.

Days filter uses the last successful sign in days.

NOTE: Using this parameter requires an Azure AD Premium P1/P2 license in the tenant.

Set a minimum number of days past since a user accesses Microsoft 365 services.

This queries the dates of the Microsoft activities report and takes the most recent service activity date across all services.

Specify the number of days for the minimum account age.

Each object property defined in this setting matches the column that will be displayed in the Web Portal for this web query.

To display additional columns, add the required properties to the Properties to display list.

To add extension attribute 1 that is synchronized from AD, you need to use a value like:

"OnPremisesExtensionAttributes/extensionAttribute1~Extension Attribute 1"

Set the filtering conditions to hide unwanted data based on criteria not supported in the Query criteria setting.

Example: filter by the found object Distinguished Name.

TIP: For optimal performance, use the Query criteria setting above to filter objects whenever possible.