Forum Discussion

Dan_Reichenbach's avatar
Dan_Reichenbach
Copper Contributor
Aug 31, 2025
Solved

Error getting Device Data

Have an issue with Device data not displaying in the Defender XDR portal.

On the Assets/Devices menu I can search and find a device, but when I click in it to see the properties- the page displays only 50% of the time. Mostly it stays loading for about 30 secs then displays the error "Error getting Device Data"

Occurs regardless of what permissions are applied, occurs regardless of the browser or incognito modes, regardless of who is logged in.

Done basic troubleshooting from MS and even MS support cannot find the answer so far.

Has anyone seen this before?

Cheers 

microsoft defender for endpoint
  • vimal_raj1984hotmail's avatar
    vimal_raj1984hotmail
    Sep 07, 2025

    Most likely Backend issue

     Ask Support to Check for Backend Service Health Incidents for Your Tenant ID: Standard service health dashboards don't always show localized issues. Ask them to specifically check for any known issues, performance degradations, or "throttling events" tied to your tenant's specific region and instance. Provide your Tenant ID

    Use Advanced Hunting as a Workaround and Diagnostic Tool:

    While the device page is broken, you can still get almost all the same information directly via KQL queries in Advanced Hunting. This is both a practical workaround and a diagnostic step.

    Example Query: To get details for a specific device:kql

    let deviceName = "YOUR_DEVICE_NAME"; DeviceInfo | where DeviceName == deviceName | project DeviceId, DeviceName, OSPlatform, OSVersion, PublicIP, LastSeen, HealthStatus, OnboardingStatus

     

     

     

     

2 Replies

  • vimal_raj1984hotmail's avatar
    vimal_raj1984hotmail
    MCT
    Sep 07, 2025

    Most likely Backend issue

     Ask Support to Check for Backend Service Health Incidents for Your Tenant ID: Standard service health dashboards don't always show localized issues. Ask them to specifically check for any known issues, performance degradations, or "throttling events" tied to your tenant's specific region and instance. Provide your Tenant ID

    Use Advanced Hunting as a Workaround and Diagnostic Tool:

    While the device page is broken, you can still get almost all the same information directly via KQL queries in Advanced Hunting. This is both a practical workaround and a diagnostic step.

    Example Query: To get details for a specific device:kql

    let deviceName = "YOUR_DEVICE_NAME"; DeviceInfo | where DeviceName == deviceName | project DeviceId, DeviceName, OSPlatform, OSVersion, PublicIP, LastSeen, HealthStatus, OnboardingStatus

     

     

     

     

Resources