Microsoft 365 Copilot Graph API returns outdated data compared to Admin Center

Question

Microsoft 365 Copilot Graph API returns outdated data compared to Admin Center

Maier Marco 20

Microsoft 365 Copilot Reports API Returns Stale Data Compared to the Admin Center

Hello,

I have identified a discrepancy between the data displayed in the Microsoft 365 Copilot Admin Center and the data returned by the Microsoft Graph Copilot Reports API.

Environment

Microsoft 365 Copilot
Microsoft Graph API v1.0
Copilot Usage Reporting APIs
Data consumed for internal reporting and analytics

Issue Summary

The Microsoft 365 Copilot Admin Center shows more recent usage data than the Microsoft Graph Copilot Reports API.

As of 23 July 2026, the Admin Center displays data refreshed through 20 July 2026 (UTC), while the Graph API only returns data through 17 July 2026.

This results in a discrepancy of:

3 days behind the Admin Center
6 days behind the current date

Microsoft 365 Admin Center

The Copilot dashboard displays:

Last refresh date: 2026-07-20 (UTC)

Screenshot from Microsoft 365 Copilot Admin Center

Benutzerbild

Endpoint 1

GET https://graph.microsoft.com/v1.0/copilot/reports/getMicrosoft365CopilotUsageUserDetail(period='D7')

Example response:

Report Refresh Date = 2026-07-17

Endpoint 2

GET https://graph.microsoft.com/v1.0/copilot/reports/getMicrosoft365CopilotUserCountSummary(period='D7')

Example response:

Report Refresh Date = 2026-07-17

Screenshot from Graph API Response

Screenshot 2026-07-23 093417

Both endpoints return successful responses (HTTP 200), but the latest available data is limited to 17 July 2026.

Additionally, activity-related fields such as:

last_activity_date
copilot_chat_last_activity_date
teams_copilot_last_activity_date
excel_copilot_last_activity_date

also stop at 2026-07-17, suggesting that the underlying dataset itself has not been refreshed beyond that date.

Expected Behavior

We would expect the Microsoft Graph Copilot Reports API to provide data that is aligned with the Microsoft 365 Copilot Admin Center.

Since the Admin Center already contains usage information through 20 July 2026 (UTC), we would expect the Graph API to expose the same data or at least have a similar refresh date.

Business Impact

We use the Microsoft Graph Copilot Reports API as the source for internal adoption, usage, and impact reporting.

Because the API data is behind the Admin Center, our reports currently contain incomplete and outdated information, leading to inaccurate reporting of Copilot usage and adoption metrics.

Questions

Is there a known synchronization delay between the Microsoft 365 Copilot Admin Center and the Microsoft Graph Copilot Reports API?
Is this difference in refresh dates expected behavior?
Why does the Admin Center already contain newer data than the Graph API?
Are there alternative APIs or endpoints that provide the latest Copilot usage information?
Is this a known issue and, if so, is there an estimated resolution timeline?

Summary

This means the Graph API is currently:

3 days behind the Admin Center
6 days behind the current date

The issue is consistently reproducible across multiple Copilot reporting endpoints.

Any clarification regarding expected refresh timelines, known delays, or recommended alternatives would be greatly appreciated.

Thank you for your assistance.

0 Kommentare

Antwort, die vom Frageautor angenommen wurde

0 zusätzliche Antworten

Ihre Antwort

Answer 1

Please note that this is a DE-DE forum, all thread should be posted in German, but I will still use English for your case today.

Hi Maier Marco

Thanks for providing detailed evidence. Based on the reported refresh dates, the Microsoft 365 Copilot Admin Center is showing data through 2026-07-20, while the Microsoft Graph Copilot Reports APIs are returning data through 2026-07-17. Microsoft documentation indicates Copilot usage reporting is not real-time and recent updates are intended to improve refresh times, but I could not find documentation stating that a persistent gap between the Admin Center and Graph API is expected behavior.

Given that the discrepancy is reproducible across multiple Copilot reporting endpoints, this may require confirmation from Microsoft support or the Copilot reporting engineering team. I recommend opening a support case and including the affected endpoints, API responses showing the Report Refresh Date, request IDs, timestamps, and screenshots demonstrating the difference between Admin Center and Graph API data.

If you're a Microsoft 365 administrator, you can open a support case as follows:

Sign in to the Microsoft 365 Admin Center: Microsoft 365 Admin Center
Select Help & support (top-right corner).
Enter a brief description such as: "Microsoft Graph Copilot Reports API returns stale data compared to Microsoft 365 Copilot Admin Center."
Review any suggested articles, then select Contact Support if the issue remains unresolved.
Create a support request and include:
- Tenant ID
- Affected Graph API endpoints
- Report Refresh Date from API responses
- Screenshots showing the Admin Center and API date discrepancy
- Request IDs and timestamps from Graph API calls

Since this is a public forum, no one here can investigate what's running behind the scene, only official support can. It's best that you reach out to them and receive further help.