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...
I've onboarded my personal devices, Windows and Linux, into MDE. None of them were joined to any AD or domain. I would say if you have a device that seems fine but isn't appearing in your MDE, check the SENSE event log.
Depends on what method you used. I can use the local script and get it on-boarded quickly. But that would be too easy. I want to know what's preventing the device to be on-boarded via Intune. And yes, I'm also doing this with my personal device.
This really sounds like a weird situation, since the SENSE service running means it is onboarded to something.
Are you assigning the policies to devices in Intune, or users?Is the registered device running a supported edition of Win10/Win11( Pro, Education, Enterprise Edition)
Also real long-shot question, but did you check to make sure that the MDE organization ID on the device matches your M365D tenant?
Not that there would be a reason for this being different, especially if you are using the same policies for both the Azure AD Joined device and the Registered device..
