Forum Discussion
MrNuggets
Nov 24, 2021Copper Contributor
Built-in Device Compliance Policy - is active - Not Compliant
I have an enrolled windows device (we are using Azure AD, no hybrid), where I changed the primary user. The compliance policy and the build-in device compliance policy for the new primary user is sh...
CutlerTS
Mar 20, 2023Brass Contributor
That makes sense. Computers in corporate environment get shared, so it's not always the same user signing in. I wish Intune can be made to work with any domain users signing in.
Trumalou
Mar 20, 2023Copper Contributor
CutlerTS We have this issue quite often in our Shared PC environment. The device has a shared policy, has no primary user and has a valid compliance policy with active devices. They somehow STILL get marked as non-compliant. I logged in with the original administrative account that enrolled the device. This made no difference, despite much syncing and rebooting. The only thing that worked was to reenrol the device again. This isn't an acceptable solution, as this issue crops up randomly and frequently. It's really frustrating, as it's a constant upkeep. If it was a valid flag, it wouldn't be so bad, but it gets to the point where there is so much 'noise', the valid issues are lost in the haystack. Microsoft, you need to sort this out!