You are here:
Considerations for Mapping Intune Fields to CMDB
Review these considerations before you map Intune device attributes to CMDB fields. Learn which mappings you can't change, how certain values are formatted, and how to capture more Intune data. These considerations help you avoid data issues and get accurate device data on the first scan.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with Agentforce IT Service that have Discovery enabled. |
When you create a Microsoft Intune discovery target, the Field Mapping page shows how Intune attributes map to CMDB fields. The page shows separate mappings for computers, mobile devices, and installed software. CMDB provides a set of default mappings that are ready to use. Extend the mappings only when you want to capture more Intune data.
Fixed Mappings
Certain field mappings are used for identification and reconciliation. You can't edit these mappings on the Field Mapping page:
| Field | Reason |
|---|---|
| Asset Name | Identifies the device record. |
| Serial Number | Identifies computers. |
| IMEI Number | Identifies mobile devices. |
| Last Discovered On | Records when Intune last synced the device. |
| Manufacturer | Part of the standard device identity. |
| Model | Part of the standard device identity. |
The Used By (User) field is also a fixed mapping. The field maps to the Intune primary user email address column. During discovery, the email address resolves to the matching Salesforce user record automatically.
How CMDB Formats Intune Data
CMDB automatically formats some values during discovery. You don't need to configure these mappings or adjust the values:
| Field | Intune Data | CMDB Storage |
|---|---|---|
| Storage (Total Storage, Free Storage) | Megabytes (MB) | Gigabytes (GB). CMDB divides the value by 1,024. For example,
512000 MB becomes 500.0 GB. |
| MAC Address | AABBCCDDEEFF with no separators |
AA:BB:CC:DD:EE:FF with colons. CMDB adds the colons. |
| OS Major and Minor Version | Full version string, such as 10.0.19045 |
The extracted part. Major is 10. Minor is
0. |
When you extend the mappings, follow these points to avoid empty or incorrect values:
- Map date fields only to Intune date columns. Values in other formats are ignored, and the field stays empty.
- Map a picklist field only to an Intune column that returns matching values. Any incoming value is stored, even when it isn't a defined picklist value.
- Text values longer than 255 characters are truncated.
Extend the Mappings
Some Intune attributes aren't mapped by default. For example, Compliance State and Entra extension attributes such as EID have no default mapping. To capture an unmapped attribute, create a custom field on the CI type, and then map the Intune attribute to that field on the Field Mapping page. You can map any attribute that Intune returns to a custom field.
