Managing devices assigend to employees is not just about inventory management. It comprises of compliance, data security and conformance. When your IT team is fielding service requests, tracking compliance, and keeping a growing fleet of MacBooks, iPhones, and iPads healthy, the last thing they need is lack of context. That's where bringing Apple device data from Jamf into Assets empowers agents with context.
In this post, we'll cover the use cases and automations you unlock by syncing Apple device data into Assets.
Jamf is the industry-leading Apple device management platform, purpose-built for managing, securing, and deploying macOS, iOS, iPadOS, tvOS, and visionOS devices at enterprise scale. Jamf API Documentation Link.
Iru (formerly Kandji) is a unified platform combining MDM, endpoint detection and response, and identity management in a single product. OnLink supports Iru integration Assets.
Addigy focuses on Apple device management for managed service providers (MSPs) and IT consultancies, offering multi-tenant management and a strong remote support experience. OnLink supports Addigy integration to Assets.
Once your Apple device inventory flows into Atlassian Assets, it stops being a static spreadsheet and becomes an active participant in your IT service delivery workflows. Here are the key use cases and automations this enables.
When an employee raises a service request — "my MacBook is running slow" or "I need a replacement charger" — the support agent can instantly pull up the relevant device asset directly within the Jira Service Management ticket.
Jira Service Management's automation engine becomes dramatically more powerful when it has access to real-time device data from Assets. Here are some practical automations you can build.
Atlassian's Rovo agents bring AI-powered intelligence directly into your JSM workflows, and they become significantly more useful when Assets is populated with rich device data. You can now have AI agents that help answer questions on replacements, warranties and other device related queries.
Getting device data from Jamf into Assets shouldn't require a custom integration, middleware or manua import. That's exactly the problem OnLink solves.
OnLink connects to your Jamf instance using API credentials (configured through API Roles and Clients in Jamf Pro).
Once connected, you define a field-level mapping that tells OnLink exactly which Jamf attributes should flow into which Assets attributes.
Here's an example of how OnLink maps Jamf mobile device data to Assets attributes:
| Jamf Field | Assets Attribute | Purpose |
|---|---|---|
mobile_device.id |
Device ID | Unique identifier (used as the key for updates) |
mobile_device.serial_number |
Serial Number | Hardware serial number |
mobile_device.device_name |
Device Name | User-facing device name |
mobile_device.name |
Name | Device name in Jamf |
mobile_device.model |
Model | Hardware model |
For computer inventory using the Jamf Pro API, the mapping looks like this:
| Jamf Field | Assets Attribute | Purpose |
|---|---|---|
id |
ID | Unique identifier |
general.name |
Name | Computer name |
general.platform |
Platform | Operating system platform |
groupMemberships |
Group Memberships | Jamf smart/static group memberships |
The mapping syntax is straightforward: key: designates the unique identifier used to match and update records, map: defines attribute-to-attribute mappings, and config:api= specifies which Jamf API endpoint to pull from.
For full technical details and setup instructions, visit the OnLink Jamf to JSM Assets documentation.
If your organization runs Apple devices through Jamf and manages IT services with Jira Service Management, connecting the two through Assets is one of the highest-impact improvements you can make to your ITSM implementation.
Try OnLink today to import your Jamf device data into JSM Assets.
We're excited to share that an upcoming OnLink integration will allow you to import data directly from Apple's Device Management Service into JSM Assets. Stay tuned!
Prabhu Palanisamy _Onward_
0 comments