AssetPilot Connect MDM sources and sync behaviour
AssetPilot Connect syncs devices from Microsoft Intune, Jamf Pro and Kandji into AssetPilot for Jira. Review source requirements and sync behaviour before configuring a connection.
AssetPilot Connect is not on Atlassian Marketplace yet. It requires AssetPilot's app REST API, which is not in production. This page describes the release candidate.
Source requirements
| Source | What you need | Hosts Connect calls |
|---|---|---|
| Microsoft Intune | A Microsoft Entra app registration with the DeviceManagementManagedDevices.Read.All application permission | login.microsoftonline.com, graph.microsoft.com |
| Jamf Pro | An API client with read access to computers and mobile devices | <tenant>.jamfcloud.com |
| Kandji | An API token with device read access, US or EU tenant | <tenant>.api.kandji.io, <tenant>.api.eu.kandji.io |
| Demo | Nothing. 40 sample devices to try the flow. | None |
Connect must be connected to AssetPilot before you can add sources. You can add up to 10 sources.
Add a source
- Open MDM sources and select Add source.
- Pick Microsoft Intune, Jamf Pro, Kandji or Demo devices.
- Name the source and enter its credentials:
- Intune: directory (tenant) ID, application (client) ID and client secret from Microsoft Entra admin center → App registrations → Certificates & secrets.
- Jamf Pro: Jamf Pro URL, API client ID and client secret.
- Kandji: subdomain, region (US or EU) and API token.
- Demo: no credentials needed.
- Choose a schedule, map device kinds to asset types and set the options below.
- Select Save changes, then Preview before the first Run now.
Schedule
Turn on Sync on schedule and choose Hourly, Every 6 hours or Daily. For daily syncs, pick the hour (00–23 UTC).
Type mapping
Map each device kind in the MDM (Laptops, Desktops, Phones, Tablets, TVs and displays, Other devices) to an AssetPilot asset type. Kinds without a type use the Default type. If the default is Don't create (skip), those devices are skipped and listed in the run's errors.
Options
| Option | Effect |
|---|---|
| Create assets for devices that aren't in AssetPilot yet | New devices become new assets |
| Overwrite asset names with the device name from the MDM | Off by default, so names you edited in AssetPilot are kept |
| Check available devices out to their MDM user (matched by email) | Assigns devices to people. Existing assignments are never changed. |
| Location for new assets | Where newly created assets are placed |
How sync behaves
- Preview first. Preview shows the first 20 devices and what would be created, updated or skipped. Nothing is written to AssetPilot.
- Matching. Devices match existing assets by MDM id, then by serial number.
- Existing values. Sync fills empty fields only. You choose whether names may be overwritten.
- Assignments. Devices are checked out to their MDM user only if you turn this on. Existing assignments are never changed.
- Required fields. A device that would leave a required field empty is skipped with the reason
REQUIRED_FIELDS_MISSING. - Schedule. Hourly, every 6 hours or daily.
- Run log. Connect keeps the last 50 runs per source, with created, updated, unchanged and skipped counts and a reason for every skipped device.
Run log
The Runs table at the bottom of the editor lists each run with its trigger (Schedule or Manual), status and counts: Fetched, Created, Updated, Unchanged, Skipped, Assigned and Errors. Expand a row to see the message and the first 50 errors.
| Status | Meaning |
|---|---|
| Succeeded | Every device was processed |
| Partial | Some devices were skipped or failed. Expand the run for reasons. |
| Failed | The run could not complete, for example because credentials are wrong |
While a run is in progress, the table refreshes every few seconds. Runs from every source also appear in Activity → Sync runs.
Delete a source
Select ⋯ → Delete source in the editor. Syncing stops and its run history is deleted. Assets that were already synced stay in AssetPilot.
Review Data and privacy for credential storage and log retention.