Fix a non-compliant device
Clearing an alert, from finding to green.
Time needed: usually five minutes plus a message to the device's user.
1. Find out what is actually wrong
- Open Alerts.
- Find the device and read its findings. Each one names the rule that is not met.
- Note the severity — deal with high first.
Do not guess from the red badge alone. "Non-compliant" could mean a missing PIN or an unencrypted disk, and those need different fixes.
2. Decide who fixes it
| Finding | Who fixes it |
|---|---|
| No screen lock, weak PIN | The person holding the device. |
| Not encrypted | The person, by leaving it plugged in until it finishes. |
| Out-of-date operating system | The person, by running updates on Wi-Fi. |
| Blocked app installed | Either — the person removes it, or you remove it from the console. |
| Rule the device cannot meet | You, by changing the policy or moving the device to a different group. |
3. Ask clearly
A message that works looks like this:
Hi Sam — your work tablet (serial ABC12345) needs a screen lock before it can be used for work email. Go to Settings → Security → Screen lock and set a PIN of at least six digits. It should take a minute. Reply here if you get stuck.
Say what to do, where to tap, and why it matters. "Your device is non-compliant" tells people nothing.
4. Confirm the fix
- Open the device and select Sync now.
- Wait a few minutes and refresh.
- The compliance badge should turn green and the alert should disappear on its own.
Alerts clear themselves. There is nothing to dismiss by hand.
5. If it will not clear
- The device has not checked in since the fix → see Device is not checking in.
- The person fixed something different from what the finding asked for → read the finding again with them.
- The rule genuinely does not apply to this device — for example a control the platform does not support — → talk to an admin about the policy for that group.
6. If the same finding keeps coming back
One device with a recurring finding is a user problem. Twenty devices with the same finding is a policy problem. Check the Alerts filters by group before you chase twenty people.
