Admins may see multiple usage reports not updating in the Microsoft 365 admin center

Timeline

Every update Microsoft posted for this issue, newest first.

1. Oct 16, 2026, 20:54 CEST

   Our enablement of the optimizations to resolve the delayed Microsoft 365 Apps Active Users reports, Overview, and Forms reports is still ongoing, and we'll provide a timeline for the completion of our resolution as one becomes available.

2. Oct 15, 2026, 22:09 CEST

   After our optimizations addressed the delays for Mailbox usage, Microsoft Teams User activity, and Microsoft 365 Group activity reports, we've determined that our pipeline is also producing delays for Microsoft 365 Apps Active Users reports, Overview, and Forms reports. We're enabling the same optimizations to affected users which we're expecting to remediate the impact.

3. Oct 14, 2026, 22:50 CEST

   We've identified that additional server-side optimizations are needed to fully remediate the impact. We're applying these optimizations to the remaining affected users and continuing to monitor the affected report types to validate full recovery.

4. Oct 13, 2026, 22:40 CEST

   We've completed our additional service-side optimizations and received some reports from impacted users that this issue has been remediated. We're continuing to monitor the final impacted report types to validate recovery.

5. Oct 12, 2026, 22:07 CEST

   We've updated the "More info" section to reflect the current processing delays for the impacted report types. While we've remediated the issues which led to the majority of delays across the listed report types, we're completing additional optimization to ensure that the data reporting delays for the remaining three report types recover as quickly and efficiently as possible.

6. Oct 9, 2026, 22:51 CEST

   We've updated the More info section of this communication to indicate that a portion of some of the reports with stale data since October 3, 2026 now include data through October 5, 2026. We'll continue to update that portion of our messaging while the remediation actions progress through the backlog of data ingestion. need to monitor in order to provide a better timeline for remediation is taking longer than expected. We continue to monitor as the backlog of data processes. We anticipate that a better timeline will be available with our next communication.

7. Oct 8, 2026, 21:58 CEST

   We've enabled our long-term fix, but we're continuing our monitoring of service health as the backlog processes to ensure that this fully remediates the issue. We anticipate that our monitoring will also help us provide more information on our timeline by our next scheduled communications update,

8. Oct 7, 2026, 21:50 CEST

   While our efforts to enable our long-term fix are ongoing, we're continuing to rebalance service traffic to provide an interim improvement to data freshness for impacted users.

9. Oct 6, 2026, 22:21 CEST

   Following our traffic optimizations to the affected subset of service infrastructure, we're monitoring their recovery and the reduction of data reporting delays. We're expecting clarity into our mitigation timeline by our next scheduled communication update.

10. Oct 5, 2026, 22:45 CEST

    We've continued to observe significant recovery in data reporting delays for the impacted report types. However, our monitoring of service health telemetry has allowed us to identify a portion of service infrastructure that is underperforming and which is resulting in continued impact. We're analyzing our next steps so that we can develop a timeline for full remediation.

11. Oct 2, 2026, 19:24 CEST

    We've verified that a significant portion of the scenarios listed in the "More info" section have recovered. We're continuing to monitor the remaining impacted report types, which we anticipate will recover by the time of our next scheduled communications update on Monday, October 5, 2026.

12. Oct 1, 2026, 20:49 CEST

    While our investigation into the combination of issues that are resulting in impact is ongoing, we're continuing to monitor as additional reporting is generated and made available to admins. Most scenarios are showing improvement, and we'll provide a complete remediation timeline once available.

13. Sep 30, 2026, 18:21 CEST

    We've identified that there are multiple issues impacting different groups of usage report types in the Microsoft 365 admin center. We're working to isolate all underlying causes of impact, and at this time, we're aware of a code issue occurring within an upstream dependency service that's causing impact to a portion of the affected reports. While we work to confirm which reports are affected by the upstream code issue, we've successfully implemented mitigation and restored Email Activity reports, Email Apps usage reports, and Active User reports to expected functionality. Our investigation is still ongoing to identify what caused these three reports to be impacted, and which other reports are facing a similar issue where this mitigation strategy can be implemented.

14. Sep 29, 2026, 23:57 CEST

    Our investigation into the underlying cause is ongoing, while in parallel looking into methods to improve reporting throughput.

15. Sep 29, 2026, 01:27 CEST

    After further review, we've validated that more tenants are impacted than initially diagnosed, and we've expanded communications to all potentially affected tenants. We've updated the "Title", "User impact", and "Scope of impact" fields of our communications to reflect this change and we've outlined the delayed usage report types in the "More info" section of this communication. We're analyzing delayed report types to isolated potential discrepancies and to determine our next troubleshooting steps.

16. Sep 29, 2026, 00:45 CEST

    We've received reports from your representatives that the impact scenario documented in MO1476333 is still ongoing. We're reviewing the latest reports of impact to further our understanding of the current impact scenario and to determine our next troubleshooting steps.