Blog Post

Intune Customer Success
2 MIN READ

Resolved: Incorrect count for onboarded Microsoft Defender for Endpoint devices report

Intune_Support_Team's avatar
Oct 17, 2023

Update 12/13: This issue is resolved with Intune's 2312 service release. Additionally, the reporting visualization has been updated to align with the newer reports in the Intune admin center. Learn more: Updated reports for Policy compliance and Setting compliance are now generally available.

 

We were recently alerted to an issue where devices onboarded to Microsoft Defender for Endpoint are not properly reflected in the Microsoft Intune admin center report for devices with/without the Defender for Endpoint sensor. We've identified a bug that is causing incorrect counts for the number of devices onboarded to Defender for Endpoint and are working on a fix that is expected to be released later this year. The report is located under Endpoint security > Microsoft Defender for Endpoint and on the connector page.

 

Note: This is a reporting bug only. It does not impact onboarding to Defender for Endpoint.

 

A screenshot highlighting the Devices with/without Microsoft Defender for Endpoint sensor report in Endpoint security.

 

Temporary workaround


As a temporary workaround, check for the Defender for Endpoint onboarding status in the Antivirus agent status report under Reports > Microsoft Defender Antivirus. Look for the columns for MDE Onboarding Status and MDE Sense Running State for more information.

 

We’ll update this post when the fix has rolled out or as more information becomes available. If you have any questions, let us know though comments on this post, or by tagging @IntuneSuppTeam on Twitter.

 

Post updates:

12/13/23: This issue is resolved with Intune's December (2312) service release. Additionally, the reporting visualization has been updated to align with the newer reports in the Intune admin center. Learn more: Updated reports for Policy compliance and Setting compliance are now generally available.

Updated Dec 15, 2023
Version 6.0
  • This issue is resolved with Intune's 2312 service release. Additionally, the reporting visualization has been updated to align with the newer reports in the Intune admin center. Learn more: Updated reports for Policy compliance and Setting compliance are now generally available. Should anyone have any further questions or issues, please let us know by sending us a message with more information about your scenario, so we can flag with the appropriate folks in Intune. Thanks!

  • fspruijt's avatar
    fspruijt
    Copper Contributor

    Tried the setting (disabled) and still no objects appear in Defender for Cloud, so this setting seem to be limited to the security portal only...

  • AlexandrosAP's avatar
    AlexandrosAP
    Brass Contributor

    Did you read this documentation and setting?

     

    Hide potential duplicate device records

    When turned on, this setting will hide duplications that might occur for the following reasons:

    • Devices that were discovered more than once
    • Discovery of onboarded devices
    • Unintentionally discovered onboarded devices

      These duplications will be hidden from multiple experiences in the portal to create a more accurate view of the device inventory. The affected areas in the portal include the Device Inventory, Microsoft Defender Vulnerability Management screens, and Public API for machines data. Notably, you will still be able to view these devices in global search, advanced hunting and alert and incidents pages.

    When activated, this heuristic might hide some discovered devices in certain cases. You can always come back here and choose to view all devices.

  • fspruijt's avatar
    fspruijt
    Copper Contributor

    Might this also relate to the direct onboarded machines not being visible in Defender for Cloud inventory ?

    We see this every day, missing resources in the morning and after some time the resources are coming back in.

  • tiagosantosAV's avatar
    tiagosantosAV
    Copper Contributor

    If we use the link to create the sensor below for the devices, this count is correct. However, I also don't understand the reason for not counting it if we create it via the police EDR.