Forum Discussion
DefaultDeviceCompliancePolicy.RequireRemainContact
- The Default Device Compliance policies have 3 requirements for a Device to be Compliant in Microsoft Intune:
1. A Custom Compliance Policy needs to be assigned => DefaultDeviceCompliancePolicy.RequireDeviceCompliancePolicyAssigned
2. The primary user needs to be Active within 30 days, after 30 days the device will become Non-Compliant => DefaultDeviceCompliancePolicy.RequireRemainContact
3. The Primary user needs to exist in Azure AD, otherwise the device will become Non-Compliant, for example, an "old" enrolled device from a user who's deleted from Azure AD => DefaultDeviceCompliancePolicy.RequireUserExistence
Hi Nicky. Thanks for the advice. How do you achieve compliance when it has failed?
craigS1967 It's not compliant because it hasn't been in contact for set amount of days. It depends on the reason and type of device. Check if device can communicate over the internet - WiFi, mobile network. Open Company Portal and check if user is logged in. If not log in. If yes go and sync device.
- I'm having this issue as well. Whenever I go to the Company Portal to login, it says I cannot use my work account and wants me to use a personal account. I'm setting up a beta machine for testing at work, so I'm a little stuck. Any advice would be much appreciated.
For the one PC we have issues we remove them completely from AzureAD and then delete the PC. The we readd them back into AzureAD. It's the only way we can get it to sync back up. Running sync from the PC is like a blink of an eye. I can monitor the device and see that check in happens every day but at 30 days we get the non-compliant. It's a very irritating issue.
- I have the same question - anyone know?
