BYOD Handling 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: or 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 2 - Mapping of InTune Corporate and BYOD Asset Types to ServiceNow CMDB CI Classes

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.

CleanShot 2025-10-08 at 16.10.47@2x-20251008-061116.png

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

Split Private (BYOD) and Corporate owned devices

Slider

When enabled, this setting causes the following:

Firstly, CI Sync shows Corporate and BYOD devices separately in Step 2 (Selections) when creating a synchronization job (see the screen shot below for the UI behaviour).

CleanShot 2025-10-08 at 16.15.29@2x-20251008-061545.png

Next, CI Sync maps Private owned (BYOD) devices to the cmdb_ci_pc_hardware table in ServiceNow.


When disabled (i.e. don’t split BYOD and Corporate devices), the setting causes the following:

Firstly, CI Sync combines Corporate and BYOD devices in Step 2 (Selections) when creating a synchronization job (see the screen shot below for the UI behaviour).

CleanShot 2025-10-08 at 16.20.23@2x-20251008-062037.png

Next, CI Sync maps Private owned (BYOD) devices to cmdb_ci_computer (for Apple Macs and Windows PCs) or to cmdb_ci_handheld_computing for (for Androids, iPhones and iPads).


Important

If data has been synchronized with the “Split Private (BYOD) and Corporate owned devices” enabled and the setting is subsequently disabled, existing records in cmdb_ci_pc_hardware will need to be deleted from ServiceNow before re-synchronizing.

  1. After modify 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.