This integration is available to customers using the device management feature. To request a trial, contact us via Ask a support representative directly in the chat.
Purpose of MDM Integration
Device ledgers (Excel, etc.) and MDM-compatible SaaS tools often manage overlapping fields. This leads to duplicate record-keeping. This feature resolves duplicate management and streamlines operations by making the device feature the master management ledger.Basic Operations in MDM Integration
Sync Overview
Sync Specifications
- Data flows from the MDM-compatible SaaS into this service (write direction).
- This service does not push data back to the MDM-compatible SaaS.
- Connecting to an MDM-compatible SaaS syncs the mergeable fields from the SaaS into this service.
- Sync occurs at three points: on initial connection, nightly (automatic), and on demand (manual).
- The
Serial Numberis the merge key. - When the serial number in the SaaS matches one in this service, a merge is performed.
- When no device matches the SaaS serial number, a new device is created. An asset number is assigned automatically — update it to your own asset number if needed*.
- When the SaaS device has no serial number, a new device is created. An asset number is assigned automatically — update it to your own asset number if needed*.
- If you add a device manually or via CSV after syncing devices with the MDM, that device will not be merged in later syncs. Add the device manually or via CSV first, then run the MDM sync to merge it.
*Synced asset numbers can only be changed manually through the UI (bulk changes via CSV are not supported).
Sync Field Descriptions
| Field on This Service | Sync Pattern | SaaS Side (MDM-Compatible) |
|---|---|---|
| The field name managed by this service | Two main sync patterns exist. (1) MDM-based · Always merged from the MDM. · Overwrites any existing value in the device field. · Manual editing of the device field is not allowed. (2) Service-based · Merge occurs only once on initial sync. · However, if a value already exists in the device field, it is not overwritten. · Manual editing of the device field is allowed. (3) MDM field · A new field created when integrating with the MDM. · The field name differs depending on the MDM. | Where the SaaS retrieves the computer information |
Sync Target Fields
Refer to the sync fields for each MDM-compatible SaaS. Jamf (Pro) Sync Target Fields Iru (Kandji) Sync Target Fields Microsoft Intune Sync Target Fields LANSCOPE Endpoint Manager Sync Target FieldsWhether Fields Update During MDM Sync (Flowchart)
