Insights & updates from our experts
Intune CMDB
This guide explains how to install and configure the Microsoft Intune V2 app in Xurrent to securely synchronize device data from Intune with customizable mappings and automated updates.
Microsoft Intune V2 app: installation guide
The Microsoft Intune V2 app synchronizes the devices managed in Microsoft Intune into the Xurrent CMDB as configuration items (CIs). This guide covers:
- Prerequisites in Microsoft Entra ID: the app registration and its permissions.
- Installing the app and each of its settings.
- What the integration synchronizes, and what it changes on existing CIs.
- The Execution Summary, to check each run.
Prerequisites
App registration
The app signs in to Microsoft Graph with an app registration in your tenant:
- In Microsoft Entra ID, register a new application.
- Under Certificates & secrets, create a client secret and copy its value. Entra ID shows the value only once.
- Note the Directory (tenant) ID and the Application (client) ID from the app registration's Overview page.
API permissions
Add these Microsoft Graph permissions of type Application, then grant admin consent:
| Permission | Required | Used for |
|---|---|---|
| DeviceManagementManagedDevices.Read.All | Yes | Reading the managed devices from Intune. |
| Device.Read.All | Yes | Reading device information from Entra ID. |
| GroupMember.Read.All | Only with a Group Membership Filter | Finding the groups by name and reading their members. |
Installing the app
- Open the Xurrent App Store and select Microsoft Intune V2 (provider Xurrent).
- On the Configuration tab, fill in the sections described below.
- Select Save. The app then synchronizes the devices on the schedule set under Frequency.

Each run creates and updates CIs, and creates product categories and products when they don't exist yet.
Connection
Enter the values from the app registration:
| Field | Required | Description |
|---|---|---|
| Directory (tenant) ID | Yes | The tenant ID of your Microsoft Entra ID. |
| Application (client) ID | Yes | The client ID of the app registration. |
| Client secret | Yes | The value of the client secret. |
| Group Membership Filter | No | One or more Entra ID group names, one per line. Only devices that are a member of at least one of these groups are synchronized. Leave it empty to synchronize all Intune devices. Needs the GroupMember.Read.All permission. |

Sync Configuration
These settings control when the integration runs and how devices are grouped into products and product categories:
| Field | Description |
|---|---|
| Frequency | How often the synchronization runs: every 24 hours (default), 16 hours or 8 hours. Each run reads only the devices that changed in Intune since the previous run. |
| Complete ReSync | When ticked, the next run reads all devices from Intune instead of only the changed ones. A complete resync runs at most once every 24 hours. Complete ReSync Info shows when the next one can run. |
| Product Category Mapping | Assigns a product category by operating system. Write one mapping per line: the operating systems separated by commas, then = and the category name. For example: iOS, Android = Phone Windows = Laptop Devices whose operating system has no mapping get a category named after their manufacturer and model. |
| Preserve existing products and product categories | When ticked, the synchronization never changes products and product categories that already exist, including their model, brand, service and support team. Mapping values are matched to the existing categories. New products and categories are still created when needed. |
| Keep configuration items on their current product | Shown when Preserve existing products and product categories is ticked. When the model of a device changes in Intune, its CI stays on its current product, with the support team and service it inherited. |
| Default Product Category | Shown when Preserve existing products and product categories is ticked. The name or reference of an existing product category, for example "Laptop PC" or "computer/laptop_pc". Devices whose operating system has no mapping get this category. |


Configuration Item Configuration
These settings decide how each device is written to its CI:
| Field | Required | Description |
|---|---|---|
| Label | Yes | Device Name, Serial Number or Entra ID Device ID. A device without a value for the chosen field is not synchronized. |
| Status | Yes | In Production, In Stock or Installed. The status is set on every run, also on existing CIs, so a status changed by hand is overwritten. |
| Asset ID | No | Device Name, Serial Number or Entra ID Device ID. When left empty, the Asset ID of synchronized CIs is cleared. |
| System ID | No | Device Name, Serial Number, Entra ID Device ID or Intune Device URL. Intune Device URL gives a direct link to the device in the Intune admin center. When left empty, the System ID of synchronized CIs is cleared. |
| Support Team Name | Yes, in practice | The name of the team set as support team of the CIs. Xurrent requires a support team on every CI, so fill this in. Without it, a new CI can only be saved when its product already has a support team. |
| Service Name | No | The name of the service set on the products the integration creates or updates. |

Custom Fields Configuration
These settings write Intune device attributes to custom fields of the product's UI extension. In each setting, enter the ID of the custom field that should receive the value, for example compliance_state. Leave a setting empty to skip that attribute. The custom field must exist on the UI extension with exactly this ID.
| Setting | Intune attribute | Value |
|---|---|---|
| Enrolled | enrolledDateTime | Date and time the device was enrolled in Intune. |
| Device Enrollment Type | deviceEnrollmentType | Text: how the device was enrolled. |
| Entra ID Registered | azureADRegistered | Yes or no: whether the device is registered in Entra ID. |
| Managed Device Owner Type | managedDeviceOwnerType | Text: company, personal or unknown. |
| Compliance State | complianceState | Text, for example compliant or noncompliant. |
| Jail Broken | jailBroken | Text: True, False or Unknown. |
| Is Encrypted | isEncrypted | Yes or no: whether the device is encrypted. |

Product UI Extension: Additional Attributes
This setting adds more Intune attributes to custom fields. Enter the variables, separated by commas, for example {{userPrincipalName}},{{wiFiMacAddress}}.
The integration converts each variable to a custom field ID in lowercase with underscores, and writes the value to the custom field with that ID. Create these custom fields on the product's UI extension:
| Variable | Custom field ID | Value |
|---|---|---|
| {{userPrincipalName}} | user_principal_name | User principal name of the device's primary user. |
| {{phoneNumber}} | phone_number | Phone number of the device. |
| {{wiFiMacAddress}} | wi_fi_mac_address | Wi-Fi MAC address. |
| {{ethernetMacAddress}} | ethernet_mac_address | Ethernet MAC address. |
| {{totalStorageSpaceInBytes}} | total_storage_space_in_bytes | Total storage, as text, for example "256 GB". |
| {{freeStorageSpaceInBytes}} | free_storage_space_in_bytes | Free storage, as text. |
| {{physicalMemoryInBytes}} | physical_memory_in_bytes | Memory, as text. |
Use text fields for the storage and memory values. A variable that matches no Intune attribute is ignored and listed under Unknown Additional Attributes in the Execution Summary.

What the integration synchronizes
Besides the settings above, every run writes these values to each CI:
| Xurrent field | Value |
|---|---|
| Name | Manufacturer and model, for example "Dell Inc. Latitude 5440". |
| Product | One product per manufacturer and model. Its category comes from Product Category Mapping, otherwise from the manufacturer and model. |
| Serial Number | The serial number in Intune. Empty when Intune has none. |
| Source and Source ID | xurrent_apps_intune_v2 and the Entra device ID. CIs created by the earlier Xurrent Intune app are taken over. |
| Last Seen | The last time the device synchronized with Intune. |
| RAM Amount | The memory reported by Intune, in GB. Left empty when Intune reports 0. |
| Operating System | A software CI that matches the operating system. See below. |
| Users | The primary user of the device. See below. |
Operating system
The integration looks for a software CI whose name, or one of its alternate names, is the operating system name and version that Intune reports. For example:
- Intune reports: name Windows, version 10.0.26100.
- The integration looks for a software CI named "Windows 10.0.26100", or with "Windows 10.0.26100" as an alternate name.
- A CI such as "Windows 11 24H2" with the alternate name "Windows 10.0.26100" is linked.
Use each name or alternate name on one CI only. When no CI matches, the CI is saved without an operating system, and the name is listed under Missing OS CI's in the Execution Summary. Create a software CI with that name, or add it as an alternate name, and the next run links it.
Users
The integration looks up the email address of the device's primary user in Intune among the active people in Xurrent. When it finds the person, it sets that person as the user of the CI. When it finds no one, it leaves the users of the CI unchanged.
Execution Summary
These read-only fields show the result of the latest run:
| Field | Shows |
|---|---|
| Last Run Started At | When the latest run started. |
| Execution Status | Running, Completed at <time>, or Failed at <time> with the reason. |
| Execution Output | The number of devices found since the last run, of CIs created or updated, and of errors. |
| Errors | The error message of each CI that could not be saved. |
| Missing OS CI's | Operating systems found on devices that match no software CI in Xurrent. |
| Unknown Additional Attributes | Entries in Additional Attributes that match no Intune attribute. |
| Unresolved Product Category Mapping | Shown when Preserve existing products and product categories is ticked. Mapping values and the Default Product Category that match no single existing product category. |
| Complete ReSync Info | When the next complete resync can run. |

Good to know
- Devices without a manufacturer or model in Intune are not synchronized.
- When a device is removed from Intune, its CI stays as it is. Only Last Seen stops changing.
- On existing CIs, every run overwrites the name, label, status, serial number, last seen, RAM, operating system, System ID and Asset ID, and the user when one is found.
- Run only one Intune integration per account. Switch off any other Intune integration, such as a partner app, before you enable this one. Both would update the same CIs.
- Xurrent allows one CI per brand and serial number. When two devices of one brand report the same serial number, the second one fails with "Serial number has already been taken". The error is listed under Errors.



.webp)










.webp)

















