Rule description
This rule queries the specified Active Directory user scope and assigns Microsoft Teams policies to each user that satisfies query criteria in Microsoft Teams.
When to use this rule
Use this rule when you need to perform bulk Teams policy assignments to Active Directory users that have the corresponding account in Office 365.
If Teams policy configuration depends on Active Directory user attribute values, you should use a CSV file where the columns correspond to Teams policies. You can use the template CSV file provided with the rule, or create a file in Microsoft Excel and export it as CSV.
Rule Settings
Query Section
| Setting name | Description |
|---|---|
| Use previous provision rule results instead of AD query results
|
When using this rule in a runbook, set this rule to use the result set of the previous rule in that runbook. This rule is often executed after the Skype On-Premises Users | Move User to Cloud Voice rule. If you set this setting to Yes, both this rule and Skype On-Premises Users | Move User to Cloud Voice rule will have the same scope. You can use this option with the following rules:
|
|
Limit scope to this domain or OU |
This setting defines the search query scope. To improve query performance, limit the scope to specific OU. |
|
AD 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.
|
|
Filter AD query results |
To hide unwanted data based on criteria set the filtering conditions here. Tip: For optimal performance, use the Query criteria above to filter objects whenever possible.
|
|
Map Settings from File |
|
|
Note: If no data source file is set, all settings in Map Settings from File section will be ignored. In this case, the rule will assign specified Teams policies to all Active Directory users in the rule scope.
|
|
|
Data source |
Specifies the text file to be used. The […] button allows to browse for the file and the Create/Edit button allows the creation or editing of the existing file in the built-in Data Source editor. |
|
Separator used in file |
Specify separator used in the file: comma or semi-colon. |
|
Data source anchor attribute |
Defines the column in the Data Source that will be used to find existent users in Active Directory. This value is compared to the Active Directory Anchor Attribute. |
|
Active Directory anchor attribute |
Defines the attribute in the Active Directory to which the Data Source anchor attribute is to be compared. |
|
Users with anchor not found in the file |
You can select what users should be assigned Teams policies: those whose anchor is not found in the CSV file or only those whose anchor is found in the CSV file. |
|
More Options |
|
|
Returned Properties |
To display additional properties for each object found by the query, add those properties to the list. |
|
Sort by |
Sort result objects list. |
|
Exclude disabled AD users |
Specify if disabled AD user accounts should be excluded. |
|
Maximum number of users |
By default, all objects that you have provisioned in Microsoft Office 365 are returned. Tip: It is possible to change the default value in Microsoft Office 365 extension settings.
|
|
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. Example: Update AD users, created in the last ten days.
{$global:DatePeriod = (Get-Date).AddDays(-10)}
|
Action Section
| Setting name | Description |
|---|---|
|
Meeting policy Messaging policy Live events policy App permission policy App setup policy Call park policy Calling policy Caller ID policy Teams policy Upgrade (coexistence) policy Emergency calling policy Emergency call routing policy Give feedback policy IP Phone policy Cloud video interop policy External access policy Online voicemail policy |
Specify the values for the Teams policies. These policies are the same as in the Microsoft Teams admin center.
|
|
More Options |
|
|
Wait for Microsoft account creation (minutes) |
This setting is applied only when this rule is used as a post rule for New user web action. |
|
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)}
|
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.3.0 | External access policy and Online voicemail policy policies have been added. |
| 7.4.0 | Use previous provision rule results instead of AD query results setting is added. |
| 7.3.0 | The rule supports mapping between the Active Directory user account and Cloud user account by anchor attributes. |
| 7.0.0 | The rule is introduced in the product. |
Comments
0 comments
Please sign in to leave a comment.