The Compliance issues page lists every device currently reporting a status you flagged as non-compliant. It is a live triage queue: issues appear when a device drifts and disappear when it recovers, with nothing to acknowledge.
Overview
Go to Compliance > Compliance issues.
The list refreshes each time a device syncs. There is no scan to launch and no acknowledge action — it shows what is wrong right now, not a ticket queue.
What the columns show
Column |
What it shows |
Status |
The non-compliant status the device reported, for example NOTENCRYPTED or OFFLINE7_DAYS |
Control name |
The MDM control or rule that raised it |
Type |
The category — encryption, OS update, antivirus, and so on |
Device name |
The affected device |
Date |
When it was last evaluated. Sorted most recent first |
How to use
- Open Compliance > Compliance issues.
- Narrow the list. Filter by Device or Type, hide the columns you do not need, and save the view if you will reuse it. The default is All compliance issues.
- Click a row to open the device drawer.
- Act from the drawer. Review the device's status across every rule, jump to the related MDM control, or run a remediation action such as pushing a profile, locking or wiping.
Sorting and grouping are not available on this table.
A needs attention indicator also appears wherever a device is shown elsewhere, so problems surface without opening this page.
How alerts resolve
Issues clear by themselves. There is no acknowledge, snooze or close. An issue disappears when:
- The device's status changes — encryption completes, the operating system updates, the device comes back online, the missing profile lands.
- You change what that status does in the settings.
Viewing issues requires MDM_READ.
Tips and best practices
- Triage by Type, not by device. Ten devices failing the same rule is usually one configuration problem, not ten problems.
- Save a filtered view per issue type you own. Opening a saved view beats re-filtering every morning.
- Use the device drawer rather than jumping between pages. It carries the full status and the remediation actions in one place.
- If the same issue keeps returning, change the rule, not the device. A status that recurs across the fleet usually should not be flagged at all.
Troubleshooting and FAQ
Troubleshooting
- An issue is still listed after the device was fixed. Issues recompute on device sync, not on demand. Wait for the next check-in.
- You cannot sort or group the table. Neither is available here. Filter and save a view instead.
- The list is overwhelming. Too many statuses are flagged. Set the transient ones back to Off, or use the exceptions and the grace period.
FAQ
-
Can I acknowledge or snooze an issue?
They clear when the device recovers or when you change the rule.
-
How current is the list?
It reflects the last sync of each device.
-
Can I fix a device from this page?
Yes. Open the device drawer and use the remediation actions there.