Breadcrumbs

Rule 9 - Synchronization of Assigned to User attribute for InTune

Rule Synopsis

These are the rule/s that control whether CI Sync synchronizes the Primary User from InTune to the Assigned_To attribute in each CI record.

This rule also controls which ServiceNow sys_user attribute is used to correlate the incoming values from the InTune Primary User attribute.

Rule Details and Default

  • By default, CI Synchronizer does not synchronize the Primary User from InTune to the Assigned_To attribute in each CI record.

Override Options

Context

Customers may consider overriding this rule so that CI Synchronizer does synchronize the Primary User from InTune to the Assigned_To attribute in each CI record.

If this rule is overridden (to cause CI Sync to synchronize the Primary User from InTune), customers can further influence the behaviour by controlling the following:

  1. Which attribute of the Primary User is read by CI Sync (e.g. the email address vs UPN associated with the Primary User).

  2. Which attribute of ServiceNow’s sys_user table (e.g. email address, User ID, user name, custom field) is used by CI Sync to correlate the incoming values from the chosen Primary User attribute (e.g. email address vs UPN).

Options

  1. This Data Sync Rule can be overridden so that CI Synchronizer does synchronize the Primary User from InTune to the Assigned_To attribute in each CI record.

  2. If this rule is overridden (to cause CI Sync to synchronize the Primary User from InTune), customers can further influence the behaviour by controlling the following which attribute is read from InTune and which attribute is used to correlate on when CI Sync sets the CI Assigned_To relationship with the sys_user table.

Overriding via Connection Settings

Customers can perform the override using a “Connection Setting” via the CI Sync User Interface (i.e. customers can perform the overrides themselves). Additional information for this is available via the following documentation:

  1. For a general overview of CI Sync Connection Settings please read Understanding the use of CI Sync Connection Settings.

  2. For the specific CI Sync Connection Setting/s related to the rule described on this page please read Assigned-To User Synchronization for InTune

For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.

Additional Information

The following diagram shows an example of the CI Sync behaviour to read one of the Primary User attributes from InTune and match to a corresponding attribute in ServiceNow’s sys_user table for the purpose of setting the cmdb_ci.assigned_to as a reference back to the sys_user table.

Example #1 - The Email Address of the Primary User from InTune is mapped to the Email Address attribute on the sys_user table in ServiceNow.

InTune Primary User and Assigned_To Overview Diagram - InTune Email to sys_user Email.svg

Example #2 - The Email Address of the Primary User from InTune is mapped to the User ID attribute on the sys_user table in ServiceNow.

InTune Primary User and Assigned_To Overview Diagram - InTune Email to sys_user user_id.svg

Example #3 - The UPN of the Primary User from InTune is mapped to a custom attribute (called u_upn) on the sys_user table in ServiceNow.

Important

Notice how BOTH a Source System (InTune) Connection Setting has been set in the CI Sync UI, AND two (2) Destination System (ServiceNow) Connection Settings have been set in the CI Sync UI.

The second ServiceNow Connection setting is specific to the use of a custom field being used to correlate to against the sys_user table in ServiceNow. The example below shows the ServiceNow Connection Setting being set to u_upn (as the example of the custom field).

InTune Primary User and Assigned_To Overview Diagram - InTune UPN to sys_user ustom Field.svg

N/A