Rule description
When to use this rule
Use this rule when you create a new linked mailbox in the federated domain and schedule to run it hourly. In this case, when this rule runs, it will check whether the user account was already created in Microsoft Office 365 and if it was, assigns the specified Office 365 license plans and options.
The licenses can be specified in this rule itself or during new user creation. You can specify the way how the Office 365 licenses and options will be assigned in New User with Linked Mailbox or New Linked Mailbox web actions in Hybrid License Options section.
Query Section
Setting name | Description |
---|---|
General Settings | |
Limit AD scope to this domain or OU |
This setting defines the search query scope. To improve query performance, limit the scope to specific OU. Important: To test rule configuration, limit the rule scope to an OU that contains test accounts or objects.
|
Query criteria Microsoft 365 query criteria |
Query criteria are sent with the query and may improve query performance. Tip: For different samples on the criteria builder, see KB20180410-1.
|
Apply to users created in last hours |
Specify an integer value that is defined the number of hours. |
Exclude MS365 disabled users |
This setting allows to exclude Microsoft 365 disabled users from the rule scope or to include them. |
Exclude AD disabled users |
This setting allows to exclude AD-disabled users from the rule scope or to include them. |
Filter Microsoft 365 filter |
To hide unwanted data based on criteria, not supported by the Active Directory and Microsoft 365 query criteria above, 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.
|
Other Query Settings |
|
Properties to display |
To display additional Microsoft 365 properties for each object found by the query, add those properties to the list. |
Sort by |
Sort result objects list. |
Maximum number of users |
The maximum number of users returned from Microsoft 365 by default is 2000. Tip: It is possible to change the default value in Microsoft Microsoft 365 extension settings.
|
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. Example: find all Microsoft 365 user accounts with displayname starting with 'Adam.' (startswith(displayName,'Adam')) |
Initialization script |
|
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: $global:<variable name>.
Example: Update AD users, created in the last ten days.
{$global:DatePeriod = (Get-Date).AddDays(-10)}
|
Action Section
Setting name | Description |
---|---|
Important: Microsoft 365 licenses that will be applied by this rule are defined during the creation of the linked mailbox by New User with Linked Mailbox or New Linked Mailbox web actions. You should not configure Microsft 365 licenses in this section.
|
|
License options |
Select which Microsoft 365 licenses and apps/services should be updated for the users. |
Change UsageLocation only if not set |
Specify whether to keep the current user's usage location or change it to a new one. |
Usage Location |
Select the usage location. |
Output Section
This section defines the output format of this rule.
To get more information about this section, please see the Output section article.
Enforce/Schedule section
This section defines the schedule for how often to run the rule.
To get more information about this section, please see the Enforce/Schedule section article.
Change History
Version | Notes |
---|---|
9.1.0 | The rule has been added to the product. |
Comments
0 comments
Please sign in to leave a comment.