Resolved: Incorrect count for onboarded Microsoft Defender for Endpoint devices report
Published Oct 17 2023 09:09 AM 12.7K Views

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.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.

6 Comments
Version history
Last update:
‎Dec 15 2023 02:28 PM
Updated by: