Pio Software logo.

Pio Software

How-to guide

Track device compliance with Microsoft Intune Importer

Use the compliance dashboard and automatic Jira issues to find non-compliant devices and get them fixed, with your Intune data in JSM Assets.

4 Nov 2026 · 5 min read

Microsoft Intune Importer for Assets brings your managed devices, applications, Autopilot devices and Endpoint Analytics scores into JSM Assets. Once the data is there, the app can also help you act on it: it shows compliance over time and opens Jira issues for devices that fall out of compliance.

What gets imported

Managed Devices is the central object. Each device links to its Manufacturer, Model, Operating System and version, Device Category and User, and to its Applications, Autopilot record and Endpoint Analytics scores. You get 10 object types and over 100 attributes in total.

1. Grant the Graph permissions

As with all our Microsoft importers, the permissions must be Application permissions with admin consent granted on your app registration.

PermissionNeeded for
DeviceManagementManagedDevices.Read.AllManaged Devices and Users (required)
DeviceManagementServiceConfig.Read.AllWindows Autopilot Devices
DeviceManagementConfiguration.Read.AllWindows Autopilot Devices

Endpoint Analytics doesn't need an extra Graph permission, but your tenant must have a Microsoft Endpoint Analytics licence.

2. Run your first import

Enter your app registration details in the importer, choose the object types you want and run a test import. When it succeeds, run a full import. It usually finishes in under five minutes.

3. Read the compliance dashboard

The compliance dashboard shows the compliance status of your whole device fleet at a glance, and trends show how it changes over time. Use it to:

  • spot a sudden drop in compliance after a policy change or OS update,
  • report progress to security or audit teams without exporting anything,
  • check that remediation work is actually moving the numbers.

4. Turn on automatic Jira issues

You can have the importer open a Jira issue automatically for each non-compliant device, so remediation goes into your service desk's normal queue.

  • Smart deduplication means a device that stays non-compliant across several imports gets one issue, not a new one each time.
  • Auto-resolve closes the issue once the device is compliant again.

Tips

  • Start with automatic issues in a dedicated project or queue to check the volume before sending them to your main service desk.
  • Link the issues to the device object in Assets so agents can see the device's model, OS version and owner right away.

More guides

All articles →