Forum Discussion
Issues on-boarding to MDE
Hello folks, A common or not so common question 🤔 Is it mandatory for a device to be 'Azure AD Joined' in order to be on-boarded to MDE? I am using 'Configuration Profile ' to deploy the MD...
Actually, I realized today that it's not even about 'Joined' or 'Registered'. I managed to get the device Azure AD joined, still can't see it in MDE. I can fully manage the device from Intune apart from 'Updating the intelligence' (not sure why). I tried deploying the onboarding agent through the EDR policy as well and it shows 'Success' there, but no idea why the device won't appear in MDE. Ran the MDE client analyzer as well, all good there.
Did you check to see if the Sense service is running on the device?
If not, the onboarding did not succeed.
Also, did you use regular configuration profiles, or did you use the endpoint security policy?
https://learn.microsoft.com/en-us/mem/intune/protect/endpoint-security-edr-policy
Using the endpoint security EDR policy might be worth a try if you used the configuration profile.
If not, the onboarding did not succeed.
Also, did you use regular configuration profiles, or did you use the endpoint security policy?
https://learn.microsoft.com/en-us/mem/intune/protect/endpoint-security-edr-policy
Using the endpoint security EDR policy might be worth a try if you used the configuration profile.
Jonhed Yes, mate. I got to know the status of SENSE from the client analyzer and the logs didn't had any 'Error' entry. I used both configuration profile with the MDE template and then a EDR policy as well. These are separate time to avoid any conflicts.