Compliance failing because Firewall not detected

Pavel yannara Mirochnitchenko 13,476 Reputation points MVP
2020-08-18T08:59:43.66+00:00

Win10 cloud-only Intune managed, 1909 and 2004 devices. I get:

"Firewall Error -2016345612"
ERROR CODE
0x87d101f4
ERROR DETAILS
Syncml(500): The recipient encountered an unexpected condition which prevented it from fulfilling the request

I noticed that first when I create the compliance policy, it is green but after some usage, it turns to error. Seems like a bug. I use only Win10 protection, no 3rd party and Firewall is own and Security Center is green in Win10.

Microsoft Security | Intune | Configuration
Microsoft Security | Intune | Other

21 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. HelplessDesk-7647 11 Reputation points
    2022-09-08T16:10:56.907+00:00

    An end user had this issue and we were able to resolve it for them using these instructions:

    1. Windows search for 'Access Work or School' and open it
    2. If there's blue text that says something like 'sign in to fix your account' then select it and sign in with the account used to join that computer to the Azure AD domain. 
    3. Open Company Portal  > Devices > select "This Device"
    4. Select the 'Check Access' button and wait (this takes longer than the sync, usually 5-10 min)
    5. If it completes and still doesn't show green then you should restart your computer and re-check access.

    This was only tested on one user whose computer was showing non-compliant in Endpoint Manager due to Firewall & Antivirus not being detected even though both were present and functioning.

    Was this answer helpful?

    5 people found this answer helpful.
  2. FDST92 1 Reputation point
    2022-12-19T14:56:48.81+00:00

    Does someone knows how to automate the task reported by @HelplessDesk-7647 ? I tried to find some informations in Microsoft Support, Rudy Ooms and other MVPs blogs, ....

    I can't find which action does the "Check Access" button do in background... The "sync" button online doesn't seem to do the same thing.

    We have around 500 devices that have the issues mentionned in this post and we're unable to resolve.

    Was this answer helpful?

    0 comments
  3. Rudy Ooms 726 Reputation points MVP
    2022-12-22T12:58:40.21+00:00

    Funny... Me searching for this error let me here... and noticing my name :) ... funny... I removed the firewall policy from the compliance policy long ago because of this error... but never looked at it... mmm guess I am out of stuff to look at it... soooo let me get my shovel

    Was this answer helpful?

  4. Mikkel Lund Knudsen 116 Reputation points
    2022-12-22T13:23:05.37+00:00

    We still check for these things in our Compliance - and so far no issues.

    Windows 11 AAD - and Co-Managed.

    Antispyware
    Microsoft Defender Antimalware
    Antivirus
    Microsoft Defender Antimalware security intelligence up-to-date
    Trusted Platform Module (TPM)
    Firewall
    Require code integrity
    Real-time protection
    Require BitLocker
    Require Secure Boot to be enabled on the device

    Was this answer helpful?

    0 comments
  5. Pavel yannara Mirochnitchenko 13,476 Reputation points MVP
    2022-12-23T21:45:15.637+00:00

    I read somewhere, that a compliance is something which should be assigned to users instead of devices. Maybe that is a root cause here...

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.