Live status of all services Incident · resolved

Users may experience issues when utilizing multiple Microsoft 365 services

Microsoft 365 suite MO1465074

Users may have experienced issues when utilizing multiple Microsoft 365 services.

Status
Post-incident report published
Feature
Company or User Administration
Region
Not specified (all regions)
Started
Aug 31, 2026, 16:56 CEST
Resolved
Sep 3, 2026, 12:00 CEST
Duration
2 days 19 h

Message

A post-incident report has been published.

Timeline

Every update Microsoft posted for this issue, newest first.

  1. Nov 17, 2026, 00:40 CET

    A post-incident report has been published.

  2. Nov 17, 2026, 00:40 CET

    A post-incident report has been published.

  3. Sep 11, 2026, 02:47 CEST

    A post-incident report has been published.

  4. Sep 10, 2026, 19:28 CEST

    A post-incident report has been published.

  5. Sep 10, 2026, 19:11 CEST

    A post-incident report has been published.

  6. Sep 8, 2026, 11:35 CEST

    A post-incident report has been published.

  7. Sep 5, 2026, 21:48 CEST

    A post-incident report has been published.

  8. Sep 3, 2026, 22:04 CEST

    Based on our telemetry all previously impacted services have remained healthy since impact was remediated on Thursday, September 3, 2026, at 10:00 AM UTC, and this issue is resolved.

  9. Sep 3, 2026, 20:24 CEST

    All user impact scenarios are now resolved as we rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of our infrastructure. We will continue to monitor our telemetry to ensure all services remain healthy and plan to close this communication by our next scheduled update.

  10. Sep 3, 2026, 18:24 CEST

    We discovered an issue in less than one percent of our infrastructure, where our additional mitigation efforts to resolve impact for Exchange Online did not successfully deploy. The vast majority of impact remains remediated; however, those serviced from the impacted portion of infrastructure may be unable to access previously recovered Outlook connection methods. We remain committed to restoring all services to all users and will continue to carefully monitor our telemetry to ensure recovery.

  11. Sep 3, 2026, 16:26 CEST

    While monitoring service telemetry closely, we identified a small volume of errors affecting mail flow functionality. We're conducting targeted restarts to reduce the number of errors and alleviate impact. In parallel, we're continuing to analyze service health telemetry to determine if any additional mitigation actions are required to restore normal functionality.

  12. Sep 3, 2026, 14:27 CEST

    We're continuing to implement further mitigation actions where required to resolve any outstanding impact associated with this incident. Customer feedback and reports from our telemetry remain positive, and service health is stable. While this work is underway, we're actively monitoring the service closely to ensure stability is consistent.

  13. Sep 3, 2026, 12:25 CEST

    We're performing additional remediation efforts where necessary to address any remaining impact from this incident. Reports from telemetry data and customer feedback are aligned, indicating a sustained recovery. We're actively monitoring the situation closely to ensure impact is completely mitigated.

  14. Sep 3, 2026, 10:25 CEST

    We're continuing to closely monitor the service to ensure sustained stability, and signals from telemetry and customer feedback remain positive. In parallel, we're conducting additional remediation actions where required to resolve any lingering residual impact.

  15. Sep 3, 2026, 08:20 CEST

    We've confirmed that our services remain stable, and both telemetry and customer reports indicate that the issue has been largely mitigated. We're continuing to address any lingering issues while we remain engaged in an extended monitoring period to validate sustained recovery.

  16. Sep 3, 2026, 06:16 CEST

    Our recovery metrics remain positive, with monitoring continuing to indicate that the service is stable and there is a constant reduction in the number of affected users. We’re continuing to validate recovery through targeted remediation actions and service health checks. We’ll maintain targeted monitoring and validation actions to confirm recovery outcomes and identify any remaining impact.

  17. Sep 3, 2026, 04:21 CEST

    Ongoing monitoring continues to show positive recovery progress, with impact no longer observed for most previously affected users. We’re continuing to monitor service health and implement targeted remediation efforts to validate recovery progress and help ensure ongoing service stability.

  18. Sep 3, 2026, 02:28 CEST

    We continue to confirm through ongoing monitoring that recovery efforts are progressing successfully across the affected services, with most impacted users no longer experiencing disruption. We’re remaining focused on identifying and resolving any remaining isolated scenarios while closely monitoring service health and implementing targeted mitigation measures to maintain stability and deliver a consistent, reliable user experience.

  19. Sep 3, 2026, 00:00 CEST

    We continue to see sustained recovery across the affected services, with most users no longer experiencing impact. We’re continuing to focus on the remaining areas of impact and are progressing our mitigation efforts to address these residual scenarios. We’re closely monitoring service health throughout this work to maintain stability.

  20. Sep 2, 2026, 22:03 CEST

    The majority of services are restored for most users, and we continue to observe broad service recovery. We recognize that some users may still experience residual impact, and addressing these remaining scenarios continues to be our highest priority. We’re actively progressing our mitigation efforts and closely monitoring service health as we work to ensure full recovery for all users.

  21. Sep 2, 2026, 20:30 CEST

    We've confirmed that impact related to OneDrive for Business, SharePoint Online, and Universal Print are now resolved. We recognize that while the majority of services are restored for most users, the remaining issues are disruptive for those still impacted. We're continuing to address residual impact with the highest priority so we can ensure resolution for all users.

  22. Sep 2, 2026, 19:36 CEST

    We’ve confirmed after a period of monitoring that impact related to OneDrive for Business and SharePoint Online is now resolved.

    OneDrive for Business and SharePoint Online:
    - Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
    - Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
    - Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.

    This quick update is designed to give the latest information on this issue.

  23. Sep 2, 2026, 19:23 CEST

    We’re working on additional mitigation measures for the portion of infrastructure which have not yet returned to healthy service levels after deployment of our primary remediation. Service availability remains above 99 percent and our monitoring shows impact is resolved for the majority of users. We remain engaged and committed to fully resolving this issue for all users.

  24. Sep 2, 2026, 18:21 CEST

    Service availability remains stable above 99%, and telemetry indicates sustained recovery across the affected environments. The primary remediation has been deployed across the majority of impacted infrastructure, with remaining deployment and validation activities progressing as expected. Most previously affected users should no longer experience issues related to this event, though a small subset may continue to see intermittent impact while final recovery validation is completed. Our remaining efforts are focused on validating sustained recovery and identifying any remaining infrastructure requiring remediation. Enhanced monitoring remains in place as we continue recovery validation activities.

  25. Sep 2, 2026, 15:37 CEST

    We're continuing to observe positive recovery trends across the affected environments, with service availability remaining stable above 99 percent. Based on our telemetry, we expect the vast majority of previously impacted users should no longer be experiencing issues related to this event. Our deployment activities are progressing as expected, and we're continuing to implement the remaining portions of our remediation across affected infrastructure to help ensure recovery is sustained over time. We remain focused on validating end-to-end service health, monitoring for any residual impact, and confirming that recovery is maintained for scenarios that rely on REST and Graph API connection methods. While a small subset of users may still encounter intermittent impact as the deployment continues to progress, current telemetry indicates continued improvement and no signs of broader service degradation. We're maintaining enhanced monitoring and will provide further updates as recovery work continues.

  26. Sep 2, 2026, 08:44 CEST

    Our telemetry indicates service availability remains stable above 99 percent, and we expect the majority of users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery, with added attention on ensuring withstanding recovery of scenarios dependent on REST and Graph API connection methods.

    This quick update is designed to give the latest information on this issue.

  27. Sep 2, 2026, 06:39 CEST

    We're observing service availability recovering to above 99 percent across the affected environments, and we expect the majority of previously affected users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery.

    This quick update is designed to give the latest information on this issue.

  28. Sep 2, 2026, 05:30 CEST

    Based on our telemetry, we expect a small subset of users may still see impact across the listed scenarios, though we're continuing our work to balance the implementation of our fixes across the infrastructure to achieve withstanding recovery.

  29. Sep 2, 2026, 03:31 CEST

    We're continuing to closely monitor service health as we carefully expand our reiterative corrective actions across additional regions. This work involves re-deploying our targeted fixes to the dependent authentication components to ensure service resilience, while balancing ongoing traffic patterns to avoid additional residual impact. Most users should see recovery across the majority of impacted scenarios, though some scenarios, including those reliant on Graph API and Representational State Transfer (REST) connection methods, will remain degraded until our mitigation efforts are complete.

  30. Sep 2, 2026, 00:29 CEST

    Most users should see recovery across the majority of impacted scenarios, though some scenarios will remain degraded until our mitigation efforts are complete. We're continuing to progress our mitigation efforts across multiple workstreams as we work to restore the service to healthy levels. We understand the challenges incidents such as these have on your organization and we’ll continue to closely monitor service health and prevent further impact.

When Microsoft 365 goes down

The live overview shows the current state of every Microsoft 365 service, refreshed every minute from Microsoft Graph.

To see whether your own tenant is affected, check Service health in the Microsoft 365 admin center. Only a backup outside Microsoft protects against data loss, and only a tested break-glass account against locked-out admins. We set up both in fixed-scope sprints.

Source: Microsoft Graph, Service Communications API. This is the view of a Swiss Microsoft 365 tenant: services not licensed there are missing, and individual issues may affect your tenant differently. Microsoft names the region only in the issue text. The Switzerland view shows issues for Switzerland, for Europe in general and those without a region, but not issues that only name other countries such as Germany or the UK. This page is not provided by Microsoft.