SkieWhat does fully compliant mean in Insights?
Fully compliant counts the devices where every protection Skie applied has been read back from Android and confirmed in place. It is a strict measure: a device missing one protection is not counted. Use it alongside the average to see whether problems are spread thinly or concentrated in a few devices.
After every apply, a device reads each protection back from Android and reports a compliance score. That is the raw material. Fully compliant is the group of devices where the answer came back clean for every protection.
The word fully matters. A device at almost every protection is not fully compliant, and it will not be in this count. That makes it a good number for deciding whether a fleet is solid, and a useful companion to the average, which is gentler. See average compliance.
Used together they tell a story. A high count of fully compliant devices with a good average means the fleet is in order. A lower count with a high average means many devices are each missing one small thing, which usually points to a policy or app update that has not landed on everyone. A low count with a low average points to something broader, like a Wi-Fi problem stopping policy updates, or a batch of devices that were never fully provisioned.
When a device is not fully compliant, open it and see which protection is off. Some are optional switches that you chose not to enforce, and those are not counted against it. The score reflects the protections your policy actually asks for.
Practical tip: use the figure as a weekly check, not an hourly one. Devices go in and out of compliance during a policy change, so look at it after a sync has had time to finish. If a device is stuck, the breach centre will also list it.