25,130 questions
Unable to onboard some devices in MS Defender
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 80%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Ashutosh Batham
15
Reputation points
I have 6 devices enrolled in Intune, but only 3 devices are showing as onboarded in the Microsoft Defender portal. The other 3 devices are displaying a status of "Not applicable" in Intune. I am unable to identify any issues causing this discrepancy. When I checked the status of one of these devices is showing that "Onboarding blob from Connector is Not applicable" Please help me to resolve this issue asap
Microsoft Security | Microsoft Entra | Microsoft Entra ID
Microsoft Security | Intune | Other
5,570 questions
Community Center | Not monitored
46,243 questions
{count} votes
-
Rahul Jindal [MVP] 10,911 Reputation points MVP2024-06-25T09:28:43.95+00:00 Do the devices in question have restricted access to Intune and Defender? You can check this by running the MDE connection analyzer. Also, have you tried running the onboarding script on the devices in question to check if they onboard or not?
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 6%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMH%3C/text%3E%3C/svg%3E)
Mark Hetherington 10 Reputation points2025-05-18T23:03:33.9166667+00:00 I have a similar case. In my case the device is marked as compliant in Intune, and seems to have no issues communicating with Intune. However, it won't on board to Defender, with the configuration policy showing as "Not Applicable". I do not think MDE connectivity issues are relevant - if the policy is Not Applicable, I don't think the device is even attempting to onboard.
Here is a guide to manually on boarding: https://knowledge.sittadel.com/manual-windows-local-script-mde-onboarding
For completeness for future visitors, here is a guide to running the MDE connection analyzer: https://learn.microsoft.com/en-us/defender-endpoint/run-analyzer-windows
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 74%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKP%3C/text%3E%3C/svg%3E)
Krunal Patel 5 Reputation points2025-05-19T03:50:56.4433333+00:00 Hi Ashutosh,
it Could be due to multiple reason
- Restricted Access: Some devices may have restricted access to Intune and Defender, preventing them from onboarding. Running the MDE connection analyzer can help determine if connectivity issues exist.
- Have you tried running the onboarding script manually on the affected devices?
- If the configuration policy in Intune is showing as "Not Applicable," it may indicate that the devices are not even attempting to onboard. This could be due to missing prerequisites or incorrect policy targeting.
Thanks,
KP
Sign in to comment
Sign in to answer