Devices flagged non‑compliant under default compliance policySolved

That’s weird. I’ve seen compliance warnings before when a device leaves the geo‑fence. If yours are still in the office, maybe the geo‑fence is set up a bit off? I don’t know much about this “Default Android Compliance policy” though, but I think Hexnode adds it automatically.

Yeah, I’ve seen that default compliance thing too. It shows up even if you don’t manually add it. Pretty sure Hexnode applies it to every device by default.

Hello everyone!

As the name suggests, the Default Android Compliance policy is automatically applied when a device is enrolled and includes a set of baseline criteria for compliance. One of these criteria is location compliance, which works in conjunction with the Geofencing policy.

Since you mentioned that you have only set up a Geofencing policy, the non‑compliance warning is being reported under the default compliance policy because location compliance is enforced through it. If the geo‑fence boundaries or coordinates are not configured correctly, devices may be flagged as outside the permitted area even when they are physically inside the office.

Please review the Geofencing policy and verify that the location and coordinates match your actual office boundaries. Once corrected and updated, the devices should reflect as compliant.

Regards,
Simon Scott
Hexnode UEM

Ah, I got it! The geo‑fence region was set up incorrectly and thanks for clarifying the default compliance policy.