Import Microsoft Intune Data into JSM Assets with OnLink

Use OnLink to import devices, applications, users, and related attributes from Microsoft Intune into Jira Service Management (JSM) Assets.

Overview

This guide explains how to configure an OnLink import from Microsoft Intune to JSM Assets. You will connect OnLink to Entra ID (formerly Azure AD), create an Assets import configuration, define field mappings, test the import, and confirm the required Microsoft Graph permissions.

Prerequisites

OnLink is installed and available in Jira from Manage your apps.
You have access to the target JSM Assets schema and object type.
OnLink is connected to Entra ID (formerly Azure AD). Follow the setup guide: Entra ID (formerly Azure AD).
The registered Entra ID application has the Microsoft Graph permissions listed in the Required Azure/Entra permissions section.

Reference video

The following demo shows the Microsoft Intune and JSM Assets integration in OnLink:

https://www.loom.com/share/1067e65526244ee890c9cb37360414d1

Set up the Assets import configuration

First, create the base Assets import configuration. Review the setup guide: Assets import configuration.

After the base configuration is created, open OnLink from Manage your apps and configure the Intune source and field-level mappings.

Configure the Intune importer

Use the following procedure to configure the importer.

Enter a descriptive name for the mapping.
Set Source system to Microsoft Intune.
Confirm the Asset Schema. OnLink pre-fills this value from the JSM Assets schema where you started the configuration.
Select the target Object Type within the schema.
Select the schedule frequency for automated production runs.
Add the attribute mappings. Use the mapping examples below as a starting point.

Mapping examples

Sample Intune object schema

Device mapping

Use this mapping to import Intune managed devices into a JSM Assets device object type.

key:id=id
map:userId=userId
map:emailAddress=Jira User
map:deviceName=deviceName
map:model=deviceModel
map:operatingSystem=operatingSystem
map:complianceState=complianceState
map:managementAgent=managementAgent

Mapping reference

Use the following reference to understand each mapping entry.

Mapping item	Purpose	Notes

Mapping item	Purpose	Notes
`key:id=id`	Uses the Intune `id` value as the unique key for the Assets object.	Required. This lets OnLink update existing records instead of creating duplicates.
`map:userId=userId`	Maps the Intune `userId` field to a text attribute in JSM Assets.	Use this when you only need to store the raw Intune user ID. Additional user details can be imported from Entra ID.
`map:emailAddress=Jira User`	Maps the device user email address to a JSM Assets attribute named Jira User.	Jira User must be an Assets attribute of type User. OnLink looks up the Atlassian user by email address.
`map:userId=userIdRef\|WorkerID=${userId}`	Maps the Intune `userId` value to a referenced user object.	Use this when the target user object has a unique WorkerID attribute that matches the Intune `userId`.
`map:model=deviceModel`	Maps the Intune device `model` property to the Assets attribute deviceModel.	Any supported Microsoft Graph managed device property can be used as a source field. See the https://learn.microsoft.com/en-us/graph/api/resources/intune-devices-manageddevice?view=graph-rest-1.0#properties.

Common Intune source fields

userId
complianceState
deviceName
enrolledDateTime
operatingSystem
jailBroken
osVersion
azureADRegistered
activationLockBypassCode
deviceCategoryDisplayName
isEncrypted
model
manufacturer
serialNumber
managedDeviceName
managementAgent

Import detected apps with associated devices

To import detected applications and their associated devices, create an Apps object type with attributes such as AppID, AppName, and Devices. The Devices attribute can reference your existing Devices object type.

key:id=AppID
map:displayName=AppName
map:devices=Devices|ID=${devices}
config:data_source=/v1.0/deviceManagement/detectedApps?$top=999
config:section=devices

Optional configuration parameters

Parameter	Description

Parameter

Description

config:filter=deviceName eq null or deviceName eq ''

Adds a Microsoft Graph filter when listing devices. You can use any valid filter expression.

To pull only registered devices
config:filter=deviceRegistrationState eq 'registered'

To pull only mobile devices
config:filter=deviceCategoryDisplayName eq 'mobile'

The above assume mobile is set in the device category in Intune

To pull only devices that has serialNumber
config:filter=serialNumber ne null

To pull only company managed devices
config:filter=managedDeviceOwnerType eq 'company'

config:data_limit=100

Limits the number of Intune records pulled. Use this for initial testing before enabling a full production import.

Test and validate the import

OnLink processes data in two separate steps: Get Data and Import Data.

Click Get Data to pull records from Microsoft Intune into OnLink staging.
Open the job logs and wait for the message: No more pending records. Data will be imported on next Import run.
Click Import Data to create or update objects in JSM Assets.
Review the target object type in JSM Assets and confirm that objects, attributes, and references were imported as expected.

Production runs are fully automated based on the schedule selected in the importer configuration.

Required Azure/Entra ID permissions

Ensure the application registered in Entra ID (formerly Azure AD) has the Microsoft Graph permissions required to read Intune device and application data. Grant admin consent after adding the permissions.