Same problem here! Any solution Microsoft? resetting the PCs is not a popular one
2016345612(Syncml(500) - Intune Compliance Policy Error
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
43 answers
Sort by: Most helpful
-
-
Florian Obradovic 11 Reputation points
2024-03-04T14:15:06.9166667+00:00 Same here, only a few devices. Firewall is active (Via Intune Policy), AV = Defender (Managed).
We have a culprit, not sure.... will see if it helps:
- Our compliance policy was assigned to all users & all devices.
Resetting firewall defaults didn't help.
Checking compliance via Companyportal (last checkin 40 minutes ago) takes forever, reboot doesn't help.
-
Anthony Yeshan Isuru De Silva 5 Reputation points
2024-04-05T04:24:06.85+00:00 Hi Guys, i have had this issue for several users. fix is to turn off the windows firewall and turn it back again. then go to company portal click once on check access and wait 2-3mins until it completes. do not click again and again as it will then take more time. if its taking way too long turn off the conditional access policy that check for compliance. then once company portal check is ok you can turn on the conditional access.
To verify further you can check azure ad portal devices and select the device you are checking on. check if its compliant. Then you can go to intune portal check if it shows compliant. it may be compliant on azure ad and not in intune. give it some time and then it will show compliant on intune as well.
-
Kodi Rozanski 5 Reputation points
2024-06-27T12:33:41.33+00:00 Microsoft, get it together. This seems to be a recurring issue. This is now happening to us
-
David Gorman 5 Reputation points
2024-07-12T08:09:52.4833333+00:00 Oh, this is still a problem. How frustrating.
Maybe there should be a Grant Access check on Conditional Access policies to at least check if it's a company device, which would be comparable to hybrid join criteria.