From 6d56bfd3d124248be086ded8290e8a352ee0da50 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Thu, 29 Sep 2016 15:27:37 +1000 Subject: [PATCH] Revert "intune mdm issue" This reverts commit 3a1a92fcd68fe3bd067f65e5a15e0e85f2c38601. --- ...ot-onboarding-windows-defender-advanced-threat-protection.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md b/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md index 4f9c6eefd3..7e351ee5aa 100644 --- a/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md @@ -72,8 +72,6 @@ Event ID | Error Type | Resolution steps 65 | Insufficient privileges| Run the script again with administrator privileges. ## Troubleshoot onboarding issues using Microsoft Intune -If the policy that you configured using Intune does not get propagated on the endpoint, you might need to go to the Azure Active Directory portal settings to configure automatic MDM enrolment. For more information see, - You can use Microsoft Intune to check error codes and attempt to troubleshoot the cause of the issue. Use the following tables to understand the possible causes of issues while onboarding: