Rule description
This rule queries the specified Active Directory user scope and assigns a Microsoft 365 phone number and Calling Plan to each user who has the corresponding account in Office 365.
When to use this rule
Use this rule when you need to assign a Microsoft 365 phone number and Calling Plan to Active Directory users that have the corresponding account in Office 365.
If calling plan assignment depends on phone location and emergency location or users need different Office 365 licenses to be assigned, you should use CSV-file where the columns correspond to Skype server settings. You can use the template CSV file provided with the rule, or create a file in Microsoft Excel and export 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 immediately 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. Important: To test rule configuration, limit the rule scope to an OU that contains test user accounts.
|
|
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 Query criteria above to filter objects whenever possible.
|
|
Map Settings from File |
|
|
Note: If no data source file is specified, all settings in Map Settings from File section will be ignored. In this case, the rule will define which users are in the rule scope and will try to assign them a calling plan.
|
|
|
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 the 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. |
|
Filter CSV data |
The filter can be used to filter by the values in the CSV file columns like {$_.ColumnName -eq 'value'} |
|
Users with anchor not found in the file |
You can select what users should be moved: those whose anchor 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 Skype Server extension settings.
|
|
Post filter |
In this filter, you can use both Active Directory attributes and column names from the CSV file. Column names you should type manually. |
|
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 |
|---|---|
| Telephone number | By default, will search for the next available number in Microsoft Teams by the city code from the next setting. |
| Override existing number |
If set to No, the rule will check if a user already has a number and skip a user if it has it. If set to Yes, the rule will override the existing number if a user has it. |
| Get free number from this location/City |
For Teams, specify the unassigned phone number search location by a concatenated string in the form: region-country-area-city. For example NOAM-US-NY-NY for New York City |
| Write number to AD attributes |
You can specify the Active Directory string attribute in which the number assigned to a user will also be written. |
| Emergency location search attribute | Select the attribute to use for searching for Emergency locations. Emergency locations are required for all US-based accounts. |
| Emergency location search value |
Select the attribute used to search for Emergency Addresses and locations. The location attribute is the most granular and is called "Place" in the Teams UI. Multiple locations/places can exist on a single address. E.g. use 'New York' if City is selected as the search attribute. |
| Location selection criteria | If the search attribute above is set to 'Location', returning the default location is not possible, and 'First found' will be used. |
| Use only validated locations | Locations added through the Teams admin UI are always validated. |
| Phone System license | A Phone System is required for all EV users. |
| Calling plan license | A Calling Plan is required. |
| Other licenses |
You can specify the ID of additional licenses that also should be assigned. If Separator used in file set to comma then licenses IDs must be separated by semi-colon and vice versa. |
| Verify license prerequisites | A user must be licensed for Skype for Business Online and Teams to assign a Phone System and Calling Plan addon. Setting to 'No' will attempt to assign the licenses in this section without verifying these prerequisites. |
| License delay (seconds) | Allow time for the license assignment to be complete. |
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 |
|---|---|
| 8.0.0 | Override existing number and Write number to AD attributes settings are added. |
| 7.4.0 | Use previous provision rule results instead of AD query results setting is added. |
| 7.3.0 | The rule is introduced in the product. |
Comments
0 comments
Please sign in to leave a comment.