Forum Discussion
Device Compliance
Baljit Aujla I have figured out the solution.
When you have Compliance policy, assigned to All Users, it will reflect all your Azure AD users with those logins. But what about other (local accounts), like "system account" etc.., they are not compliant.
Resolution is to have another additional (same) compliance policy, assigned to Azure AD security group, and add those (shared) windows 10 devices to the group.
In that case, Compliance policy is assigned on device level to the specific device, and then "system account" does not cause the problem.
It is poorly documented, but this is something that Microsoft Support given to me...
Baljit Aujla I have figured out the solution.
When you have Compliance policy, assigned to All Users, it will reflect all your Azure AD users with those logins. But what about other (local accounts), like "system account" etc.., they are not compliant.
Resolution is to have another additional (same) compliance policy, assigned to Azure AD security group, and add those (shared) windows 10 devices to the group.
In that case, Compliance policy is assigned on device level to the specific device, and then "system account" does not cause the problem.
It is poorly documented, but this is something that Microsoft Support given to me...
In our case, our Compliance policy is targeted to an Azure AD Security group with all of our Windows 10 machines in it already, reading this it sounds like I have to duplicate the policy exactly then assign it to a group of Users as well?
dustintadam in that case, I am not sure, you can try and post feedback.
My case, i was assigned to (all) users, and additionally assigned to devices, to resolve system account issue.
Did you have to create a copy of the compliance policy, or simply assign the same policy to multiple groups that included both users and computers?
