Rule description
This rule queries the specified CSV file containing a list of Microsoft 365 contacts and modifies their properties according to the values in the file.
When to use this rule
Use this rule when you need to perform bulk Microsoft 365 contacts update from HR/ERP/SIS system into Microsoft Office 365.
This rule requires a source text file in the comma-separated variable format (CSV). You can use the template CSV file 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 Create Office 365 Contacts - Template CSV file
-
Click Open
The Query source text file requires the following CSV (comma-separated value) format:
Email,FirstName,LastName
joe@domain.com,Joe,Smith
kelly@domain.com,Kelly,Jones
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 |
Defines the column in the Data Source that will be used to determine if the Microsoft 365 contact already exists. This value is compared to the Contact Anchor Attribute. |
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 |
This setting specifies the columns that will be displayed during Preview and in the output file. |
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. |
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 |
---|---|
Account | |
Email address
|
Specify a column with a contact email address or skip this setting. |
First Name (FirstName) |
If the Data Source contains a field named FirstName, do nothing. Otherwise, use the Selector button to choose a field from the Data Source. Also, you can skip this setting. |
Last Name (LastName) |
If the Data Source contains a field named LastName, do nothing. Otherwise, use the Selector button to choose a field from the Data Source. |
Display Name
|
Specify the DislpayName format or skip this setting. |
Initials |
Specify a column with contact initials or skip this setting. |
Name |
The internal name of a contact must be unique. The name is not shown in the Microsoft 365 UI. Select one of the following options:
|
Name conflict resolution |
This option determines how the system should react when the name of a contact being created already exists:
|
Alias |
The following values are possible:
Note: The default Microsoft behavior is to use the name with spaces and other unsupported symbols removed.
|
Hide from GAL |
Specify if the created contact should be hidden from GAL or skip this setting. |
Mail tip |
Specify a column with a contact mail tip or skip this setting. |
Organization |
|
Company Job Title (Title) Department
|
Specify a static text value or use the Selector button to choose a field from the Data Source or skip these settings. |
Manager |
Specify contact manager. Use any supported contact/user value for the manager (email, username, ID, etc.) or skip these setting. |
Contact Info |
|
Country Office Phone (telephoneNumber) Mobile Phone (mobile) Street Address City State Postal Code Fax Web site |
Specify a static text value or use the Selector button to choose a column from the Data Source or skip these settings. |
Custom Attributes |
|
Custom attribute1 - Custom Attribute 15 |
If you use Exchange Online custom attributes to store additional information for contact accounts, you could select these attributes and map them to Custom Attributes or skip these settings. To set labels or default values for these attributes, please use Attribute Policies.
Note: Only Exchange Online attributes can be assigned to custom attributes.
|
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 |
---|---|
10.3.0 | The rule has been introduced in the product. |
Comments
0 comments
Please sign in to leave a comment.