Service graph connector for Microsoft Intune pulling computer data

AnubhootiJ
Tera Contributor

12 hours ago

Hi ,

 I have two question regarding Microsoft Intune integration with ServiceNow 

 

1)As we are pulling computer data from Microsoft Intune used data source type of data stream, in Script parser step, i used parsing and doing mapping in import set table, but i want data should be pulled directly into the import set table(in short no manual mapping should be there), Is there any way to do that??

Attaching some screenshot below:

AnubhootiJ_0-1775808662714.pngAnubhootiJ_1-1775808698937.png

 


2) We are looking for the model_number, but we are not getting that from Intune, how to get it, it should be treated as unique and we have to map it into the CMDB tables.

Please suggest the answers!!


0 Helpfuls
  • 82 Views
1 REPLY 1

Naveen20
ServiceNow Employee

4 hours ago

 

The Script Parser step exists precisely because Data Streams require you to explicitly map fields to your import set table. There's no way to bypass this entirely, but you have two cleaner approaches:

  • Use a Standard REST Integration (Import Set Auto-Map): Instead of a Data Stream, create a Scheduled Import with a REST data source pointing to the Microsoft Graph API (/deviceManagement/managedDevices). When you configure the data source and run a "test load," ServiceNow can auto-create columns on the import set table matching the JSON response fields. Then your Transform Map handles the mapping to CMDB — no Script Parser needed.

  • Use IntegrationHub ETL: If you want to stay within Workflow Studio, the ETL step (available with IntegrationHub Professional+) lets you define source-to-target field mappings visually and loads directly into an import set table without writing a Script Parser. It essentially replaces the Splitter + Script Parser combination.

In short — the Data Stream + Script Parser pattern inherently requires that manual mapping. To avoid it, switch to a Scheduled Import with REST data source or ETL step.

2) Getting model_number from Intune

The Microsoft Graph API for managed devices (/deviceManagement/managedDevices) returns a model field but not a separate model_number. Here's how to handle it:

  • The model field from Intune (e.g., "Surface Pro 9", "HP EliteBook 840 G9") is typically what you'd map to the CMDB model_id field via a Transform Map lookup on cmdb_model.
  • If you need a distinct "model number" (like a manufacturer part number), Intune doesn't natively provide it. You'd need to either:
    • Enrich from another source — pull hardware details from the Windows Autopilot API (/deviceManagement/windowsAutopilotDeviceIdentities) which includes systemFamily and model, or use SCCM/MECM for richer hardware inventory.
    • Use serialNumber as the unique identifier instead — Intune reliably returns serialNumber, which is the standard CI reconciliation key in CMDB (used by IRE identification rules on cmdb_ci_computer).

For CMDB uniqueness, the recommended approach is to use serialNumber (plus manufacturer if needed) as your identification rule rather than relying on model number.

0 Helpfuls