IMEI support per MDM

The unified DeviceModel exposes two IMEI fields:

How these fields are populated depends on the underlying MDM provider. Not all integrations support IMEI, and dual-SIM handling varies.

Summary

Integration	IMEI Supported	Source Field(s)	Max IMEIs	Dual-SIM
Jamf	Yes (mobile only)	`network.imei`, `serviceSubscriptions[*].imei`	Unbounded	Via subscriptions
Kandji	Yes	`cellular.subscriptions[*].imei`	Unbounded	Via subscriptions
Hexnode	Yes	`device.imei_1`, `device.imei_2`	2	Yes (`imei_1`/`imei_2`)
Microsoft Intune	Yes	`imei`	1	No
Google Devices	No	—	0	N/A

Supports IMEI: Yes — mobile devices only. Computers always return null / [].

Unified field	Source	Details
`imei`	`network.imei`	Falls back to `serviceSubscriptions[0].imei` if `network.imei` is absent
`imeis`	`network.imei` + `serviceSubscriptions[*].imei`	Merged and deduplicated

Dual-SIM: Supported via multiple service subscriptions.

Supports IMEI: Yes

Unified field	Source
`imei`	`cellular.subscriptions[0].imei`
`imeis`	`cellular.subscriptions[*].imei`

Dual-SIM: Supported via multiple cellular subscriptions.

Supports IMEI: Yes

Unified field	Source
`imei`	`device.imei_1`
`imeis`	`device.imei_1` + `device.imei_2`

Dual-SIM: Yes — Hexnode provides explicit imei_1 and imei_2 fields, supporting up to 2 IMEIs.

Supports IMEI: Yes

Unified field	Source
`imei`	`imei` (top-level field on the device object)
`imeis`	`[imei]` (single-element array if present)

Dual-SIM: Not supported. Only one IMEI is available per device.

Supports IMEI: No

Unified field	Value
`imei`	`null` (hardcoded)
`imeis`	`[]` (hardcoded)

Google Devices does not expose IMEI data through its API.