Microsoft Intune to JSM Assets

key:id=id

The keyword “key” refers to using id (from Intune) as a unique identifier. This allows OnLink to update the record.

map:userId=userId

Maps userId from Intune userId text attribute; additional details about user can be imported from Entra ID.

map:emailAddress=Jira User

The emailAddress field containing email address of user associated with the device is mapped to Jira User. Jira User is an attribute of type “User” - OnLink automatically looks-up the Atlassian User object based on the email address.

map:userId=userIdRef|WorkerID=${userId}

This maps userId from Intune to user object. WorkerID is the unique ID on the user object.

map:model=deviceModel

Maps model property from Intune. Any field (string, boolean, date) from Intune API can be used as the source field. Here’s the list of fields: managedDevice resource type - Microsoft Graph v1.0

Here are some common fields:

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

Get Apps Detected with Associated Devices

Create an object for Apps with AppID, AppName and Devices fields. Devices can be a reference to your existing Devices object.

Create an OnLink importer with this mapping. This imports all apps with devices that have those apps installed.

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

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

Optional parameter to add filter to list devices; any valid filter expression can be used here

config:data_limit=100

Optional parameter to limit the number of users to pull from Intune. This can be used for initial testing.