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.

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.

To display additional properties for each object found by the query, add those properties to the list.

Sort result object list.

Usually, rules use query criteria to limit the query search scope. It improves the performance of the executed rule.

Due to the 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: $global:<variable name>.

Example: Update AD users, created in the last ten days.

1. Add this initialization script

   Copy

   {$global:DatePeriod = (Get-Date).AddDays(-10)}

2. Use the $DatePeriod variable in the query criteria builder:

Select operation you need to perform on AD users' accounts:

1. Generate a new address. The rule will generate a new address and add it to the user as a primary or secondary address, depending on the Set generated address as the primary setting value.

2. Add prefix to all addresses. The rule will read the current addresses of the specified type on a user and add a text prefix, specified in the Address Prefix setting, to each address, and then replace addresses with new values.

3. Remove prefix from all addresses. The rule will read the current addresses of the specified type on a user, remove the text prefix, specified in the Address Prefix setting, from each address, and then replace addresses with new values.

Specify address prefix. Example: All user accounts have SMTP address like address@mydomain.com. If you select to add the prefix MyPrefix_ to all SMTP addresses, the new SMTP addresses will be MyPrefix_address@mydomain.com". If you select to remove the prefix MyPrefix_ from all SMTP addresses, SMTP addresses will be reverted back to "address@mydomain.com".

If SMTP addresses don't contain the specified prefix, they won't change.

TIP: To extract address prefix from the mail attribute use this script: { $FoundObject.mail.Split('@')[0] } If the user email address is user.name@domain.com, the address prefix will be user.name.

Specify address suffix.

NOTE: This setting is only used when the Operation is set to Generate a new address.

Select whether to set the generated address as primary or not.

NOTE: This setting is only used when the Operation is set to Generate a new address.

Select whether to remove other email addresses or not.

NOTE: This setting is only used when the Operation is set to Generate a new address.

1. Initialization Script section is added.

   1. The following settings are renamed:

   2. Generate new SMTP address -> Generate new address

   3. Add prefix to all primary and secondary SMTP addresses -> Add prefix to all addresses

   4. Remove prefix to all primary and secondary SMTP addresses -> Remove prefix from all addresses

   5. Update email attribute -> Update 'mail' attribute

   6. Add integer counter if email already exists -> Add integer counter if address already exists

2. Address type setting is added.

3. SMTP Address Additional Options section is added.