How to Import Jamf, Intune, and Entra ID Data to Assets using OnLink

In this article, we’ll walk through how to import data from Jamf, Intune, and Entra ID (formerly Azure AD) into Assets all using a single app, OnLink. Assets is Jira Service Management’s configuration management database (CMDB). It lets you map and manage your organization’s users, devices, software, and entitlements, so your teams always know who owns what and what connects to what. Keeping that data current, though, is often the hardest part. Many teams still rely on manual CSV uploads or custom scripts that quickly go stale. That’s exactly what OnLink solves. It automates synchronization between your existing systems and Assets.  

Scenario: Onward Technologies

To make it concrete, let’s imagine a fictional scenario Onward Technologies, a 1,200-person app development company operating across North America and Europe. Their setup:

• Apple devices managed in Jamf
• Windows and Android devices managed in Intune
• Users, roles, and licenses managed in Entra ID
• Jira Service Management as the central ITSM platform

Each system worked well alone but none of them shared data causing inconsistencies in device ownership, user records, and license tracking. We will show how OnLink, helped Onward connect all three systems to JSM Assets, creating a single, live source of truth.  

Connect Jamf to JSM Assets

Goal: Import Apple device, user, and application data from Jamf into JSM Assets. Setup:

1. In Jira, open OnLink → Connections.
2. Click Add System → IdM/Device Asset Sources → Jamf.
3. Enter your API credentials. You can create them using Jamf’s API Roles and Clients Guide.
4. Create a new Assets import configuration in OnLink.
5. Choose your API type — Classic or Pro — depending on your environment.

  Example mapping (Classic API – mobile devices):

key:mobile_device.id=Device ID
map:mobile_device.serial_number=Serial Number
map:mobile_device.device_name=Device Name
map:mobile_device.model=Model
config:api=JSSResource/mobiledevices

✅ Mapping:

• key: defines the unique ID used for updates
• map: links Jamf fields to your Asset attributes
• config: defines which API endpoint to pull from

OnLink automatically syncs data on a schedule with no manual uploads required. Documentation Link.  

Connect Intune to JSM Assets

Goal: Import Windows and mobile device data managed in Intune. Setup:

1. Connect OnLink to Entra ID (this also enables Intune access).👉 Follow this Entra ID setup guide.
2. Create a new Assets import configuration and set Microsoft Intune as the source.
3. Define your Asset schema and object type.
4. Configure your schedule and mappings.

  Example 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

To also link apps detected in Intune with the devices they’re installed on:

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

  Documentation Link.  

Connect Entra ID to JSM Assets

Goal: Sync user records, groups, licenses, and organization attributes from Entra ID. Setup:

1. In OnLink, choose Azure AD (Entra ID) as your source system.
2. Define your Asset schema and object type (e.g., Users).
3. Map your attributes and enable optional features for Groups or Licenses.

  Example mapping:

key:userPrincipalName=WorkerID
map:userPrincipalName=Email
map:displayName=DisplayName
map:companyName=CompanyName
map:department=Department
map:jobTitle=JobTitle
config:export_azure_groups=true
config:export_azure_licenses=true

You can extend this to include:

• Manager hierarchy (config:expand=manager)
• Cost center and division references
• Group and license schemas linked to your user objects

OnLink can even pull attributes like hire date, office location, and preferred name giving you complete employee context inside Assets.   Documentation Link.

The Payoff: Unified Data in JSM Assets

After integrating Jamf, Intune, and Entra ID, Brightwave achieved something powerful: a live, accurate, interconnected CMDB — all visible directly inside Jira Service Management. Benefits:

• Single source of truth: Devices, users, and licenses all tied together.
• Smarter automation: Auto-assign, route, and audit based on real data.
• Simplified audits: Real-time compliance and license visibility.
• Better service context: Every issue shows who owns what and how it’s configured.

End to End Demo

 

Try It Yourself

If your organization uses Jamf, Intune, or Entra ID, you can connect all three to Jira Service Management Assets with OnLink — no custom code or middleware needed. 👉 Learn more and try OnLink