Question
Syncfish has implemented a new version of the Intune Source Connector with improvements over the original Intune Connector. We will be engaging with our customers using the original Intune connector to help them move their CI Sync workloads to the new Intune Connector.
This article will answer questions you may have about the migration process.
Update April 2026 - All Customers should have migrated to Intune v2. This article will be archived in the near future.
Answers
What is better about the new version of the Intune Connector?
Faster
Changes to the processing mechanics used in the new Intune Connector has resulted in a more performant process. Our early adopter customers on the new Intune Connector are seeing improved processing times, particularly on larger sync jobs.
New Destination Class & New Fields for All
-
A new destination class “Handheld Computing Device” (cmdb_ci_handheld_computing) is now leveraged for the CORP Resource Android/iPhone/iPad datasets. This includes new fields and new search rules using those more mobile specific fields (ICCID/IMEI/MEID)
-
CORP Computer datasets (Apple Mac and Windows PC) also get additional fields and remain, by default, mapping to the Computer class (cmdb_ci_computer).
-
BYOD device datasets (Computers and Mobile Devices) also get additional fields and remain, by default, mapping to the Personal Computer class (cmdb_ci_pc_hardware).
-
See the table below for full details for all the new fields by dataset.
|
Dataset |
Intune (v1) |
Intune (v2) |
New functionality |
|---|---|---|---|
|
CORP Android
|
cmdb_ci_comm |
cmdb_ci_handheld_computing |
New Fields supported
3x New Search Rules
|
|
CORP Apple Mac
|
cmdb_ci_computer |
cmdb_ci_computer |
New fields supported
|
|
BYOD (All datasets) |
cmdb_ci_pc_hardware |
cmdb_ci_pc_hardware |
New fields supported
|
Is any Intune Connector functionality being deprecated?
Yes - the “Detected Apps” datasets are no longer available.
Any schedules you have setup using “Detected Apps” will need to be reconfigured/updated.
Are there any pre-requisites or additional requirements?
It is highly recommended that you have the CMDB CI Class Models plugin installed in your ServiceNow instances that are registered as Destination Connections in CI Sync.
This allows the leveraging of the Handheld Computing Device class for mobile devices and access to the mobile-specific additional fields and more accurate search rules using ICCID/IMEI/MEID descriptors.
Wait! What happens to all our Mobile Devices that are already in the “Communication Devices” table in ServiceNow?
Syncfish CI Sync supports “cross-class matching” - under the hood, for example, CI Sync knows that Mobile Devices can possibly be located in either the Communications Device or Handheld Computing tables in ServiceNow.
What this means is that during a Sync Job, if CI Sync needs to update a device that is currently located in the Communications Device table, the CI will be located, the update applied and the CI CI reclassified as a Handheld Computing Device in the same transaction.
Syncfish does recommend performing a full sync after moving to the new Intune Connector, so that all Mobile Devices currently located in the Communications Device table in ServiceNow are moved to the Handheld Computing Device table.
Will any of the CIs that our team already synced be impacted?
No CIs will be impacted for two reasons:
-
Cross-class matching is implemented (described above).
-
Additionally, when we assist your team in the Connector upgrade - we will be migrating your existing Intune connectors, so your Intune Job history remains the same. All the mappings of previous sync jobs are retained.
Great! How do we move to the new Intune Connector already?
If you are currently using the Syncfish Intune Connector v1, one of our team will be contact with you to review all of the above items and schedule a session to help you migrate your existing Intune Connections.
Related Articles
N/A
Control Information
|
Created |
|
|---|---|
|
Reviewed |
|
|
Data Classification |
PUBLIC
|