Live status of all services Incident · resolved

Users may be unable to connect to, or experience degraded functionality with Exchange Online

Exchange Online EX1464935

Users may have been unable to connect to, or experienced degraded functionality with Exchange Online.

Status
Post-incident report published
Feature
All clients
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:46 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:34 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:05 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:23 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:23 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:23 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:14 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:21 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:23 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:16 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:21 CEST

    We continue to observe positive recovery trends through ongoing monitoring, with most affected users no longer experiencing disruption. We remain focused on identifying and resolving any remaining issues while implementing targeted mitigations to support a stable and consistent user experience.

  19. Sep 3, 2026, 00:00 CEST

    We've confirmed that the majority of users remain mitigated. We're continuing to advance several workstreams as we work toward full resolution for all users and in parallel, we're maintaining enhanced monitoring throughout this work to ensure service stability.

  20. Sep 2, 2026, 22:31 CEST

    We’ve completed a restart of affected Outlook on the web infrastructure, and service telemetry indicates that the majority of users have recovered. We’re continuing to closely monitor service health as we roll out more durable fixes designed to address the underlying conditions contributing to the impact.

    In parallel, we’re working directly with affected users and examining reports of continued impact to gather additional diagnostic information and identify any remaining issues.

    We remain focused on fully restoring service for all affected users and will continue deploying our fixes, investigating reports of impact, and monitoring service health until we’re confident the issue is fully resolved.

  21. Sep 2, 2026, 20:29 CEST

    We recognize that while service is restored for most customers, the remaining issues are disruptive for those still impacted. We are prioritizing fully resolving the issue for all customers.

  22. 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.

  23. Sep 2, 2026, 18:22 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.

  24. 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.

  25. 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.

  26. Sep 2, 2026, 05:31 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.

  27. Sep 2, 2026, 03:30 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.

  28. Sep 2, 2026, 00:30 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.

  29. Sep 2, 2026, 00:30 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.

  30. Sep 1, 2026, 20:59 CEST

    We’re continuing to advance multiple workstreams to restore service and prevent additional impact. We’re prioritizing infrastructure that requires the most immediate attention while carefully expanding corrective actions across additional regions, with continued monitoring throughout this process. In parallel, we’re investigating remaining reports of impact and evaluating additional actions to support full service recovery.

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.