1. Help
  2. Integrations
  3. Intune CMDB
  1. Help
  2. Integrations
  3. Intune CMDB
purple icon for coordination.
We’ve moved!
Our Help Center has a new home and our URLs have changed. Please update your bookmark to this page before April 30, 2026

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:

  1. In Microsoft Entra ID, register a new application.
  2. Under Certificates & secrets, create a client secret and copy its value. Entra ID shows the value only once.
  3. 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:

PermissionRequiredUsed for
DeviceManagementManagedDevices.Read.AllYesReading the managed devices from Intune.
Device.Read.AllYesReading device information from Entra ID.
GroupMember.Read.AllOnly with a Group Membership FilterFinding the groups by name and reading their members.

Installing the app

  1. Open the Xurrent App Store and select Microsoft Intune V2 (provider Xurrent).
  2. On the Configuration tab, fill in the sections described below.
  3. Select Save. The app then synchronizes the devices on the schedule set under Frequency.
Microsoft Intune V2 app, Configuration tab

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:

FieldRequiredDescription
Directory (tenant) IDYesThe tenant ID of your Microsoft Entra ID.
Application (client) IDYesThe client ID of the app registration.
Client secretYesThe value of the client secret.
Group Membership FilterNoOne 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.
Connection settings

Sync Configuration

These settings control when the integration runs and how devices are grouped into products and product categories:

FieldDescription
FrequencyHow 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 ReSyncWhen 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 MappingAssigns 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 categoriesWhen 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 productShown 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 CategoryShown 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.
Sync Configuration settings
Product category settings

Configuration Item Configuration

These settings decide how each device is written to its CI:

FieldRequiredDescription
LabelYesDevice Name, Serial Number or Entra ID Device ID. A device without a value for the chosen field is not synchronized.
StatusYesIn 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 IDNoDevice Name, Serial Number or Entra ID Device ID. When left empty, the Asset ID of synchronized CIs is cleared.
System IDNoDevice 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 NameYes, in practiceThe 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 NameNoThe name of the service set on the products the integration creates or updates.
Configuration Item Configuration settings

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.

SettingIntune attributeValue
EnrolledenrolledDateTimeDate and time the device was enrolled in Intune.
Device Enrollment TypedeviceEnrollmentTypeText: how the device was enrolled.
Entra ID RegisteredazureADRegisteredYes or no: whether the device is registered in Entra ID.
Managed Device Owner TypemanagedDeviceOwnerTypeText: company, personal or unknown.
Compliance StatecomplianceStateText, for example compliant or noncompliant.
Jail BrokenjailBrokenText: True, False or Unknown.
Is EncryptedisEncryptedYes or no: whether the device is encrypted.
Custom Fields Configuration settings

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:

VariableCustom field IDValue
{{userPrincipalName}}user_principal_nameUser principal name of the device's primary user.
{{phoneNumber}}phone_numberPhone number of the device.
{{wiFiMacAddress}}wi_fi_mac_addressWi-Fi MAC address.
{{ethernetMacAddress}}ethernet_mac_addressEthernet MAC address.
{{totalStorageSpaceInBytes}}total_storage_space_in_bytesTotal storage, as text, for example "256 GB".
{{freeStorageSpaceInBytes}}free_storage_space_in_bytesFree storage, as text.
{{physicalMemoryInBytes}}physical_memory_in_bytesMemory, 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.

Additional Attributes setting

What the integration synchronizes

Besides the settings above, every run writes these values to each CI:

Xurrent fieldValue
NameManufacturer and model, for example "Dell Inc. Latitude 5440".
ProductOne product per manufacturer and model. Its category comes from Product Category Mapping, otherwise from the manufacturer and model.
Serial NumberThe serial number in Intune. Empty when Intune has none.
Source and Source IDxurrent_apps_intune_v2 and the Entra device ID. CIs created by the earlier Xurrent Intune app are taken over.
Last SeenThe last time the device synchronized with Intune.
RAM AmountThe memory reported by Intune, in GB. Left empty when Intune reports 0.
Operating SystemA software CI that matches the operating system. See below.
UsersThe 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:

FieldShows
Last Run Started AtWhen the latest run started.
Execution StatusRunning, Completed at <time>, or Failed at <time> with the reason.
Execution OutputThe number of devices found since the last run, of CIs created or updated, and of errors.
ErrorsThe error message of each CI that could not be saved.
Missing OS CI'sOperating systems found on devices that match no software CI in Xurrent.
Unknown Additional AttributesEntries in Additional Attributes that match no Intune attribute.
Unresolved Product Category MappingShown 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 InfoWhen the next complete resync can run.
Execution Summary

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.