Rule description
This rule takes a text file containing a list of users with the phone numbers that should be assigned to this user and assigns the corresponding number.
When to use this rule
Use this rule when you need to assign phone numbers to hybrid or cloud users from the CSV file.
You can assign the following number types:
- Microsoft Calling Plan
- Direct Routing
- Operator Connect
This rule requires a source text file in the comma-separated variable format (CSV). You can use the template CSV files provided with the rule, or create a file in Microsoft Excel and export it as CSV.
To use a template CSV file:
- In the Query section, click the [...] button next to the Select Data Source setting
-
Open Templates folder
-
Select AD Users Template CSV file
-
Click Open
The Query's source text file requires the following CSV (comma-separated value) format:
UserPrincipalName,PhoneNumber,PhoneNumberType
Joe.Smith@domain.com,+12340000,DirectRouting
Kelly.Jones@domain.com,+12340001,DirectRouting
The supported values for the PhoneNumberType column are:
- CallingPlan
- DirectRouting
- OperatorConnect
Rule Settings
Query Section
| Setting name | Description |
|---|---|
|
Select data source |
Specifies the text file to be imported. The […] button allows the user 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. |
|
Data source anchor attribute |
Select a column in the data source that contains the attribute value for identifying and mapping a user like UserPrincipalName. |
|
Account source system |
Select the source system of the accounts listed in the CSV file: Hybrid or Microsoft 365. |
|
User anchor attribute |
Automap searches for a user using the standard identity attribute DistinduishedName, UserPrincipalName, and samAccountName. Select a custom attribute if your users are identified by a different attribute. Note: Microsoft best practices assume the Active Directory and Office 365/Azure AD UPNs will match. |
|
More Options |
|
|
Filter CSV data |
This setting specifies the filter that can remove data rows from the imported text file that satisfies the specific condition. |
|
Properties to display |
To display additional properties for each object found by the query, add those properties to the list. |
|
Filter Office 365 users |
To hide unwanted data set the filtering conditions here. |
| Empty field in Data Source
|
If the record in the CSV file column is empty, you can skip updating the attribute or clear its value. |
| 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.
|
| 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 |
|---|---|
| Number to assign | Select the column that contains the phone numbers to be assigned. |
| Phone number type |
Select the number type directly if it is the same across all users or set by the value in the selected column. These phone number types are possible:
|
| Emergency location ID |
If you want to set an emergency location input the location ID into this field or select a column that contains the location IDs for each user. The location ID for a location can be found in the Teams UI. |
| 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. |
| 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. Note: Option is valid only for Hybrid Account source system type.
|
| Phone System license | A phone system is required for all enterprise voice users. Select one of the licenses listed in the field, type an SKU ID directly or select a column from the mapping file if the license assignment is mapped. |
| Other licenses |
You can specify the ID of additional licenses that also should be assigned. If Separator used in file is set to a comma then license IDs must be separated by a semi-colon. If the separator is set to semi-colon then license IDs must be separated by a comma. |
| Verify license prerequisites | A user must be licensed for Skype for Business Online and Teams to assign a Phone System and Calling Plan add-on. Setting to 'No' will attempt to assign the Phone System and other licenses in this section without verifying the prerequisites. Use 'No' if you plan to assign licenses that include all required services, such as E5 licenses. |
| 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 |
|---|---|
| 9.3.0 | The rule has been introduced in the product. |
Comments
0 comments
Please sign in to leave a comment.