Microsoft 365 Copilot User Activity Report Delayed: Fix

The Microsoft 365 Copilot user activity report in the admin center may show data that is several hours or even a full day old. This delay prevents you from seeing real-time adoption metrics and troubleshooting user engagement issues promptly. The root cause is usually a combination of data processing latency in the Microsoft Graph and specific tenant-level configuration gaps. This article explains why the report lags and provides step-by-step fixes to minimize the delay.

You will learn how to check the data freshness setting, verify service health, and adjust the report refresh interval. These steps apply to any Microsoft 365 tenant with a Copilot for Microsoft 365 license. After applying the fixes, your activity report should reflect user actions within two to four hours instead of the default 24-hour window.

Why the Copilot User Activity Report Is Delayed

The Microsoft 365 Copilot user activity report aggregates data from the Microsoft Graph activity logs. These logs record every user interaction with Copilot across Word, Excel, PowerPoint, Outlook, Teams, and other Microsoft 365 apps. The report then processes this raw data into the charts and tables you see in the admin center. A delay occurs when one of three conditions is true: the default refresh interval is set to 24 hours, a service incident is throttling data ingestion, or the admin account lacks the required permission to read audit logs in near-real time.

Microsoft uses a batch processing system for Copilot activity data to reduce server load. By design, the system collects data in 24-hour windows unless you explicitly configure a shorter interval. If your tenant has more than 10,000 active users, Microsoft may also apply a processing queue that adds an extra one to two hours of latency. This is not a bug but a deliberate trade-off between performance and freshness. The fix requires you to change the tenant-level reporting settings and verify that no service issues are blocking data flow.

Default Refresh Interval

The default refresh interval for the Copilot user activity report is 24 hours. This means the report shows data from the previous calendar day, not the current day. To see today’s activity, you must reduce the interval to 2 hours. The setting is located in the tenant admin settings under Reports > Usage > Copilot > Data freshness.

Service Incidents Affecting Data Ingestion

Microsoft occasionally throttles data ingestion for Copilot activity logs during peak usage or maintenance windows. When this happens, the report may show data that is 48 hours old or older. You can verify this by checking the service health dashboard for any active advisory under Copilot.

Missing Audit Log Permission

The admin account that views the Copilot activity report must have the Audit Logs Read permission in the Microsoft 365 compliance center. Without this permission, the report cannot fetch fresh data from Microsoft Graph and falls back to cached data that is up to 24 hours old.

Steps to Reduce the Report Delay

Follow these steps in order. Each step addresses one of the root causes described above. After completing all steps, the report should update within two to four hours.

1. Change the Data Freshness Interval to 2 Hours
   Open the Microsoft 365 admin center at admin.microsoft.com. Go to Reports > Usage > Copilot. Click the Settings icon in the top-right corner of the Copilot report page. In the Data freshness section, select Every 2 hours instead of Every 24 hours. Click Save. This change applies to all admins who view the report.
2. Check for Active Service Incidents
   In the admin center, go to Health > Service health. Look for any advisory or incident under the Copilot service. If an incident is active, click it to see the estimated resolution time. Wait for the incident to resolve before expecting fresh data. If no incident is listed, proceed to the next step.
3. Assign the Audit Logs Read Permission to Your Admin Account
   Go to the Microsoft 365 compliance center at compliance.microsoft.com. Select Permissions > Roles > Audit Manager. Click Add to create a new role group or edit an existing one. Add your admin account as a member. Ensure the role group includes the Audit Logs Read permission. Save the changes. Wait 30 minutes for the permission to propagate.
4. Force a Manual Report Refresh
   After changing the interval and permissions, return to the Copilot user activity report in the admin center. Click the Refresh button in the toolbar. The report will attempt to pull the latest data from Microsoft Graph. If the data still appears stale, wait two hours and check again.
5. Verify the Report Data Freshness
   After two hours, open the Copilot user activity report again. Look at the date stamp at the top of the report. It should show the current date and a time within the last two hours. If the date stamp is still showing yesterday’s date, repeat steps 1 through 4 and contact Microsoft support if the issue persists.

If the Report Still Shows Delayed Data

Even after changing the interval and permissions, some tenants may experience persistent delays. The following issues explain why and provide targeted fixes.

Copilot Activity Report Shows Data From Two Days Ago

This usually indicates that a service incident is actively throttling data ingestion. Check the service health dashboard for any incident that started more than 24 hours ago. If you find one, note the incident ID and contact Microsoft support. They can manually flush the processing queue for your tenant.

Report Shows No Data for the Current Day

If the report shows data only up to yesterday and the refresh interval is set to 2 hours, the admin account may lack the Audit Logs Read permission. Reassign the permission in the compliance center and wait 30 minutes. Then refresh the report manually.

Report Refresh Button Does Not Update the Data

The Refresh button in the Copilot report page triggers a client-side refresh of the cached report data. It does not force a server-side data pull. If clicking Refresh does not show new data, the issue is on the server side. Wait for the next scheduled refresh cycle based on your interval setting.

Copilot User Activity Report: Default vs Optimized Settings

Setting	Default (24-hour delay)	Optimized (2-hour delay)
Data freshness interval	Every 24 hours	Every 2 hours
Admin permission required	Reports Reader	Reports Reader + Audit Logs Read
Data latency (typical)	24 to 48 hours	2 to 4 hours
Service health dependency	None	Must check for active incidents
Manual refresh capability	Client-side only	Client-side only

With the optimized settings, you can view user activity for the current day instead of waiting until the next day. The trade-off is that you must assign the Audit Logs Read permission to all admins who need to view the report. If your organization has strict compliance policies, you may choose to keep the default 24-hour interval to reduce audit log access.

Now you can reduce the Copilot user activity report delay from 24 hours to two hours by changing the data freshness interval in the admin center. You also know how to verify service health and assign the Audit Logs Read permission. As a next step, consider setting up an automated alert in the service health dashboard that notifies you when a Copilot-related incident starts. This way, you can proactively check the report freshness before stakeholders report a delay.