OnLink · Device data

Importing Device Data from Microsoft Intune to Assets

OnLink imports Microsoft Intune device data into Jira Service Management Assets through the Microsoft Graph API: one Entra ID app registration with two read-only permissions, a mapping keyed on the Intune device ID, and optional detected-apps import for a software inventory.

This guide covers why Intune data belongs in Assets (ticket lookups, onboarding, offboarding), the connection and permissions, the field mapping, and the filter and data-limit options.

Why bring Microsoft Intune data into JSM Assets

When you populate Assets with device data from Intune, we can enable high-impact ITSM use cases.

Look Up Asset Data for Device Issues and Replacements

When an end user raises a ticket saying "my laptop is slow" or "I need a replacement," the service desk agent needs answers fast. With Intune data in Assets, the agent can look up the device directly from the ticket and see the model, OS version, compliance state, management agent, and whether encryption is enabled.

Assign Devices During Employee Onboarding

Onboarding a new hire involves provisioning the right hardware and ensuring it is enrolled and compliant before day one. When your Assets database reflects the current Intune inventory, HR and IT workflows in JSM can reference available devices, match them to the new employee, and update the assignment. Linking the Intune user ID or email address to a Jira user means the device-to-person relationship stays accurate and auditable.

Collect Devices for Offboarding Requests

When an employee leaves the organization, IT needs to know exactly which devices are assigned to them so that hardware can be collected, wiped, and returned to inventory. Having Intune data synchronized into Assets gives the offboarding workflow a reliable source of truth.

Start with Intune, end with every source in one app

Most teams come to Assets with one narrow job: get Intune devices in. That is the right first step, but devices are only useful in a ticket when they are linked to the person who owns them and the account they sign in with. With OnLink the same app that imports Intune also imports the HR system (Workday, BambooHR, Personio, HiBob) and the identity provider (Entra ID, Okta), so People, Devices and Accounts land in one schema and link to each other.

Diagram: employee data (Workday, BambooHR, Personio, HiBob), device data (Intune, Jamf, NinjaOne, Apple Business) and identity data (Entra ID, Okta, Google Workspace) flow through one OnLink app into linked People, Devices and Accounts object types in JSM Assets.
Employee, device and identity data through one OnLink app into linked People, Devices and Accounts in Assets.

One price as sources grow

Per-source importers charge per app, and the bill climbs with every new system. OnLink is one license at your Jira user tier whether you connect Intune alone or Intune, Workday and Entra ID together.

One app to manage

One place for credentials, schedules, run logs and alerts instead of a different admin screen, support contact and security review for every source.

One mapping syntax

The same key:, map: and config: lines work for every source, so employee-to-device and manager links are defined once and reused across HR, device and identity imports.

See every source OnLink connects and how the one-app price compares with per-source importers as connections grow.

How OnLink imports Intune device data into Assets

OnLink connects to 100+ sources be it HRIS, Identity Provider or Devices. OnLink is all you need to import to Assets.

One App for All Your Asset Integration Needs.

Connecting OnLink to Entra ID

Because Intune is part of the Entra ID, OnLink authenticates through an Entra ID (Azure AD) app registration. The setup involves three steps:

  1. Register an application in the Azure portal (Azure Active Directory → App registrations → New registration). Give it a descriptive name such as “OnLink Connection.”
  2. Grant API permissions. Under the app’s API permissions blade, add Microsoft Graph application permissions (not delegated).
  3. Create a client secret under Certificates & secrets. Copy the secret value immediately — it will not be visible again.

You will need three values to complete the connection in OnLink: the Directory (tenant) ID, the Application (client) ID, and the Client Secret — all available from the app registration’s Overview and Secrets pages.

OnLink API credentials for connecting to Microsoft Intune through Entra ID
OnLink: API credentials for connecting to Microsoft Entra ID and Intune (tenant ID, application ID, client secret).

Full step-by-step instructions are available in the OnLink Entra ID documentation.

Permissions required

The Entra ID app registration must have the following Microsoft Graph application permissions granted (with admin consent):

Microsoft Graph permission
What it allows
DeviceManagementApps.Read.All
allows OnLink to read Intune app data, including detected applications on managed devices.
DeviceManagementManagedDevices.Read.All
allows OnLink to read managed device properties such as model, OS, compliance state, and enrollment details.

Field mapping

Once the connection is established, you create an import configuration in OnLink and define the field mapping between Intune device properties and your JSM Assets object type attributes. OnLink uses a straightforward key/map syntax.

Supported fields

Below are the commonly mapped Intune fields. Any property exposed by the Microsoft Graph managedDevice resource can be used as a source field.

Intune Field
Description
id
Unique device identifier in Intune
userId
ID of the user associated with the device
emailAddress
Email of the user associated with the device
deviceName
Name of the device
model
Device hardware model
manufacturer
Device manufacturer
serialNumber
Device serial number
operatingSystem
Operating system (Windows, macOS, iOS, Android)
osVersion
OS version number
complianceState
Compliance status (compliant, noncompliant, etc.)
managementAgent
Management channel (mdm, eas, etc.)
enrolledDateTime
Date and time the device was enrolled
azureADRegistered
Whether the device is Azure AD registered
isEncrypted
Whether disk encryption is enabled
jailBroken
Jailbreak/root detection status
activationLockBypassCode
Activation lock bypass code (iOS)
deviceCategoryDisplayName
Device category assigned in Intune
managedDeviceName
Managed device display name

Sample mapping

				
					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
				
			

A few things to note about the mapping:

  • The key line tells OnLink which field to use as the unique identifier, enabling upsert behavior (insert new records, update existing ones).
  • When you map emailAddress to a JSM Assets attribute of type User, OnLink automatically looks up the matching Atlassian user account — no manual matching required.
  • You can also map userId to a reference object (e.g., an Employee object) using the syntax map:userId=userIdRef|WorkerID=${userId}, which creates a relationship link between the device and the user object in your schema.

How to get apps associated with devices

Beyond device hardware details, OnLink can import the list of applications detected on each managed device. This is useful for software license tracking, compliance auditing, and security reviews.

To set this up, create a separate object type in your Assets schema for Apps with at least three attributes: AppID, AppName, and Devices (a reference to your Devices object type). Then create an OnLink importer with the following mapping:

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

This pulls detected applications from the Intune API and links each app to the devices where it is installed, giving you a complete software inventory inside JSM Assets.

Additional features: filters and data limit

OnLink offers several configuration options that help you tailor the import to your needs.

You can use the config:filter parameter to apply a filter expression to the Intune API query. For example, to exclude devices without a name:

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

Any valid OData filter expression supported by the Graph API can be used here, letting you narrow the import to specific device types, compliance states, or operating systems.

The config:data_limit parameter caps the number of records pulled from Intune in a single run. This is particularly useful during initial setup and testing — for example, config:data_limit=100 lets you validate your mapping against a small dataset before trying the full dataset.

The app makes syncing assets so easy but any time I have a question, I put a ticket in and they get me taken care of either with clear direction or a call to walk me through things.
Iris Alvarado
OnLink customer · Atlassian Marketplace review, Sep 2026
Ready to bring Intune devices into Assets?

Install OnLink from the Atlassian Marketplace and have your Intune fleet in JSM Assets today.

FAQ

No. Intune is part of Microsoft Entra ID, so one app registration with the Intune Graph permissions covers both. The same connection can also import Entra ID users, groups and licenses into Assets.

Two application permissions: DeviceManagementManagedDevices.Read.All for device properties and DeviceManagementApps.Read.All for detected applications. Both are read-only; OnLink never writes to Intune.

Map emailAddress or userPrincipalName to a JSM Assets attribute of type User and OnLink resolves the Atlassian account automatically. To link to an Employee object type instead, map userId with the reference syntax shown in the sample mapping.

Yes. Add a config:filter line with any OData expression the Graph API supports, for example operatingSystem eq ‘Windows’ or complianceState eq ‘compliant’. Use config:data_limit during testing to validate the mapping on a small batch first.

OnLink imports those through the same app: see the Jamf Pro guide. Key both imports on serial number into one Devices object type and you get a single hardware inventory in Assets. All sources and how OnLink compares.

On this page

Intune data in Assets

Start a free trial of OnLink on the Atlassian Marketplace. Intune is one of 100+ device, identity and HR sources in the same app.

Try OnLink for Intune to JSM Assets

Install OnLink from the Atlassian Marketplace and try the Intune-to-Assets integration today. 

With Intune device data in Assets, your team can: