Forum Discussion

Narmatha_svk's avatar
Narmatha_svk
Copper Contributor
Mar 09, 2026

Intune Graph API deviceStatuses missing device shown in portal

Hello,

 

I am retrieving device status for an Intune configuration profile using Microsoft Graph API.

 

API request:

 

GET https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations/{policyId}/deviceStatuses

 

Issue:

 

In the Intune portal, a device shows Success status for the configuration profile under:

 

Devices → Configuration profiles → Device status

 

However, when retrieving the same data using the Graph API endpoint above, that device does not appear in the API response.

 

Observations:

 

In the Intune portal, the policy shows one device with Success status.

 

But the Graph API response returns different devices and does not include the device visible in the portal.

 

Example response (sanitized):

 

deviceDisplayName: Device-A

status: unknown

 

deviceDisplayName: Device-B

status: unknown

 

Questions:

 

Why would a device appear in the Intune portal device status but not in the Graph API deviceStatuses response?

 

Is there a delay in data synchronization between the Intune portal and Graph API?

 

Is there another Graph endpoint recommended for retrieving all device configuration status results?

 

Additional details:

 

Graph API version: beta

Permission used: DeviceManagementConfiguration.Read.All

Tested using Graph Explorer

 

Any insights would be appreciated.

intune

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Jul 17, 2026

    The permission is sufficient, so first rule out paging. Graph can return a partial collection; follow every @odata.nextLink exactly until none remains, then compare IntuneDeviceId rather than display name.

    There is also a reporting-model mismatch. The admin center's current Device and user check-in and Device assignment reports use Intune's newer reporting service, while deviceConfigurations/{id}/deviceStatuses returns the legacy deviceConfigurationDeviceStatus resource. Microsoft now marks that entity deprecated from May 2026, so it should not be treated as the authoritative replacement for the portal report. Data can also differ briefly because device check-in and report generation are asynchronous.

    For automation, use deviceManagement/reports/exportJobs with the DeviceConfigurationPolicyStatuses, or current V3, report and explicitly select PolicyId, IntuneDeviceId, DeviceName, PolicyStatus, and PspdpuLastModifiedTimeUtc. Filter where supported, poll the export job, and compare timestamps. If one device remains missing after a fresh sync and report generation, capture the request-id and timestamps for Microsoft support.