We have the same issue, no third party AV, laptops updated re-synched multiple times.
It happens to Win11 laptops only!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have had this recurring issue for a long time now, and despite searching the error all over the place, there seem to be a lot of other IT professionals in the same boat, but no obvious answers.
The error is on the Anti-Virus setting on the default compliance policy.
2016345612(Syncml(500): The recipient encountered an unexpected condition which prevented it from fulfilling the request)
The compliance policy in question is assigned to all users.
This is a very annoying issue as it stops users from being able to access any MSFT apps as it marks the device as non compliant.
we are forced to add users to the exclusion list of the policy until the error clears on it's own days/weeks later.
If anyone has any ideas on what could be the cause or any possible fixes, it would be greatly appreciated
We have the same issue, no third party AV, laptops updated re-synched multiple times.
It happens to Win11 laptops only!
I can confirm we are a Defender shop and seeing this as well, specifically for the Firewall setting within Device Compliance. It seems to resolve itself after a few hours, but OP mentions, it locks users out.
Facing the same issue here.
Apparently intune thinks (defender firewall) real time or cloud protection setting is not enabled while in reality it is.
As I mentioned before, retire the machine from intune, delete from azure, than try to reset windows on the machine, let it re enrol to both azure and intune and chances are the issue will be gone. No more compliance errors.
Resetting machine apparently does not resolve the issue, that's just a workaround on win11 machines. MS need to fix that.
Let me know if the above procedure helped.
Thanks
What is your current AV solution and what is it status locally, any warnings?
I would suggest to re-create and re-deploy the compiance policy to test it our, will that solve your problem.