Built-in Device Compliance Policy - Is active / Device Not Compliant

Question

Hi

We are experience something strange. Someone's Devices are "Not Compliant" and I cant really understood way, maybe some have a Idea, that would be great.

So let see:

• the Device is "Not Compliant"...... Why...?
  It look like because the Setting "is Active" , all other settings are compliance, only this one is "no compliance"
  

but... the Device already sync today :(

and the Build-in Policy look also good... 30 days.......

..... so, the big Question, Why this Device are not compliance.....?
We have many Devices like this one (Full Managed and also same Model). Some ones are compliance and other not :(

What we find till now is, that many Apps updates are pending and not installing automatically, also if I have already set up to auto update the Apps trough the Device Configuration. After the updates, you can make a sync and the device become compliance.

Also if the User manually start the Intune App and sync the Device, it will become compliance :(. But that can't be the Solution..... The Intune App need to sync in the background automatically, what really look like to work, because the "Last check-in time" ..... :(

very appreciate if some one have an Idea.

Answer 1

@Mela Germier Thanks for posting in our Q&A.
If this is a specific device's problem, is the version of OS running on this device same as the other devices?
As far as I know, the usual solution is to manually sync the company portal app on the device and wait 15-30 minutes for it to become compliant. I see that you have also tried this.
Have you tried to re-enroll the device? if it's still not compliant, it looks like that this is an issue scoped on the Intune service side.

I would recommend to create an online support ticket by following the steps in the article below. Thanks for your understanding.

https://learn.microsoft.com/en-us/intune/get-support

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

For this one who maybe experience the same or something like that.

The Problem look like to be resolve, at less all the 25 Device with this Problem, do not have it any more, I will for sure keep this on eyes, but for now look everything good again.

What was...? I do really don't know, but what I do: I have change the Setting "Compliance status validity period (days)" from the default "Compliance policy settings", to 15 days, wait one day and back to 30 Days.

This setting, I have it since the beginning to 15, because according the Documentation we can use it from 1 to 120 days. I don’t know if a lower value to 30, can cause this issue, but now, all looks good again.