Forum Discussion
Device compliance 65001 (Not Applicable) and Defender Security centre weirdness
Hi Tech community. I have 2 questions, related to some work I am doing with a customer who's devices are Azure Hybrid AD joined and using Windows 10 1909. 1. The windows 10 devices do not hav...
HI
For question one, there is a setting 'Mark devices with my compliance policy assigned as', yours will be set to 'non-compliant'.
https://techcommunity.microsoft.com/t5/microsoft-intune/device-compliance-65001-not-applicable-and-defender-security/m-p/1343120#M4083
I would advise to keep it this way. This makes sure all computers have a good compliance policy assigned
For your second question, yes TVM in MDATP is slow :). No workaround here unfortunately. You just have to be patient
For question one, there is a setting 'Mark devices with my compliance policy assigned as', yours will be set to 'non-compliant'.
https://techcommunity.microsoft.com/t5/microsoft-intune/device-compliance-65001-not-applicable-and-defender-security/m-p/1343120#M4083
I would advise to keep it this way. This makes sure all computers have a good compliance policy assigned
For your second question, yes TVM in MDATP is slow :). No workaround here unfortunately. You just have to be patient
Please be clear. This error 65001 (not applicable)
1. means something or means nothing
2. This statement of yours: 'Mark devices with my compliance policy assigned as', yours will be set to 'non-compliant'. Seems to indicate that devices with a compliance policy assigned will be marked "non-compliant." This seems contradictory. Please explain tis logic.
I have this issue as well, and I've not found a satisfactory explanation on line at all. Thanks for your help.
- Check this out https://docs.microsoft.com/en-us/mem/intune/protect/device-compliance-get-started#compliance-policy-settings
What is the value of 'Mark devices with no compliance policy assigned as' for you
