Prevent syncing records with a null serial number for InTune

Connector Applicability

Applies to Source Connectors

InTune

Applies to Destination Connectors

All

Assumptions

These instructions assume you have already setup a source connection in CI Sync for InTune using the CI Sync instructions here: Add InTune to SaaS Agent.

Pre-Read

Syncfish recommend customers read the following documentation before changing the Connection Setting/s described below.

  1. Understanding the use of CI Sync Connection Settings

  2. Rule 13 - Syncing records with a null serial number for InTune

Locating and Amending the Connection Setting in the CI Sync UI

  1. Navigate to the Settings page

  2. Under the Source Connections heading (list), locate your InTune connection.

  3. Click the Update link on the right hand side of the InTune connection.

  4. Scroll down and locate the Section Heading and view the Individual Settings.

Intune insert suppression 2.jpg

The screen shot is provided only as sample to assist when reading this page. The state of your own CI Sync UI will depend on whether you are starting from the CI Sync default position or if you have already amended one/more of the settings.

  1. Tick the Override default box/boxes and then use the sliders related to the individual settings. The following table elaborates any further information about these particular settings.

Setting

Type

Additional Notes

Suppress Insert of Records with Null Serial Numbers

Slider

This setting is off by default. Records with Null (or empty string) Serial Number will be inserted into ServiceNow.

If enabled, CI sync will prevent records in Intune with Null (or empty string) Serial Number values from being inserted into ServiceNow.

  1. After modifying the settings, scroll to the bottom of the page, tick the “I consent…” checkbox and finally click the Save connection button.

  2. You can now run a sync job and the amended settings will be applied causing the CI Sync Data Sync rules to be modified accordingly.

Importantly

Make sure you consciously override the setting against either your TEST or PROD environment (i.e. your TEST vs PROD sync jobs).

For more information on how to use TEST vs PROD Connection Settings please read Understanding the use of CI Sync Connection Settings.

Syncfish strongly recommend making changes for TEST environment/sync jobs first. Only modify PROD related settings after thoroughly validating the intended results in TEST.