Microsoft 365 outage enters its second day with Outlook still unstable

The Microsoft 365 outage has reached its second day with gradual improvements, but Outlook and other business services have not yet fully returned to normal. According to available information, Microsoft attributes the problem to a misconfiguration of authentication that affected components of its infrastructure.

• Microsoft reported that the availability of its services is improving, although it still maintains an extended monitoring period.
• The outage affected Outlook, SharePoint, Copilot, Teams, Purview, Defender XDR, the Admin Center, and Universal Print.
• The company identified a misconfiguration in Exchange Online that caused issues with email, authentication, and search.

The outage affecting Microsoft 365 entered its second day on Tuesday, September 1, 2026, without the company declaring a full recovery. The incident began with issues in Exchange Online, the service that supports much of Outlook's email functionality, and then reached other products used by business customers. According to TechCrunch, users experienced delays and failures in email, as well as difficulties authenticating and accessing various tools normally.

Microsoft communicated that its mitigation measures were progressing within the part of the infrastructure that remained affected, while telemetry indicators showed positive signs. The company also confirmed that service availability was improving, although it chose to maintain extended monitoring before considering the incident resolved. This caution means that some users may already observe a gradual recovery, but they could still encounter degraded functions or irregular behaviors in the coming hours.

A central failure affecting multiple services

The scope of the problem was greater than a simple email outage, although Outlook garnered most of the public attention. The Microsoft 365 status page for Business and Enterprise customers indicated impacts on SharePoint, Copilot, Teams, Purview, Defender XDR, the Microsoft 365 Admin Center, and Universal Print, products that serve different functions within corporate environments.

Microsoft attributed the incident to a failure in a central authentication configuration used by multiple Microsoft 365 services. When such a piece does not function as expected, the consequences can extend beyond a single application, as several components rely on it to validate identities, authorize sessions, and allow access to business resources.

Internal investigation determined that the origin was a misconfiguration that prevented authentication components from deploying as expected in part of the infrastructure. The explanation did not point to an isolated outage of a single mailbox or a problem limited to a specific region, but rather to a configuration failure capable of disrupting the coordinated operation of several connected services.

During the night, Microsoft explained that it first reviewed recent changes that could have triggered the incident and then tested different mitigation measures. The company implemented these actions progressively to alleviate the impact on end users, a process that also aimed to reduce the risk of introducing new problems while restoring the affected components.

Outlook improves, but recovery remains incomplete

As mitigations began to roll out, Microsoft indicated that Outlook users should perceive a gradual recovery in their message flow. Email started to show signs of improvement, but the company warned that the search functionality remained degraded, a significant limitation for those who rely on large message histories and need to locate information quickly.

By 10:00 PM Eastern Time on Monday, August 31, Microsoft reported that email flow was improving, while search continued to be affected. Shortly after 3:00 AM on Tuesday, September 1, the company communicated that it was also observing progress in that function, although it did not provide a statement confirming the full restoration of Outlook.

The difference between an improvement in availability and a complete resolution is significant in a business platform, where users may regain basic access while still facing partial failures. An email arriving late, a search returning incomplete results, or an authentication process that is interrupted can keep a service operational in appearance but hinder everyday tasks and corporate workflows.

In its latest update, Microsoft stated that telemetry indicators remained positive and that availability was improving. The company said it was entering an extended monitoring period to ensure a complete resolution, meaning the next step was not just to apply changes but to verify that the infrastructure remained stable under normal customer use.

What the Incident Means for Business Users

Microsoft 365 brings together email, collaboration, storage, security, management, and artificial intelligence tools within a single ecosystem. This integration offers convenience to organizations but can also broaden the impact radius when a central authentication configuration affects services that share technical dependencies.

In this case, the issues described by Microsoft included access failures, authentication problems, and delays in Outlook email. The presence of SharePoint, Teams, Copilot, Purview, Defender XDR, the Admin Center, and Universal Print on the list of affected services shows that the disruption could impact both internal communication and document management, security, and device or print administration.

The incident also illustrates why companies often distinguish between the overall availability of a platform and the full functioning of each of its features. The recovery of messages does not guarantee that search, authentication, or connected tools have returned to the same level of service, especially when the cause lies in a shared layer.

Microsoft did not announce in the available information that the disruption was fully resolved nor did it provide a definitive time for the incident's closure. For now, the company maintains a gradual advancement and prolonged observation stance while users await confirmation that the reported improvements hold and that all functions return to normal levels.

The Mitigation Process and Next Steps

The sequence described by Microsoft began with a review of recent changes potentially related to the failure. Afterward, its teams tested and implemented several mitigations, a strategy that allows addressing the impact while seeking to correct the configuration that prevented the expected deployment of the authentication components.

This progressive approach explains why the company communicated a gradual recovery instead of an immediate reset. By applying measures within the remaining affected infrastructure, Microsoft was able to observe the behavior of its systems through telemetry and adjust its actions as signs of improvement appeared or degraded functions persisted.

The search for Outlook occupied a particular place in the evolution of the incident, as it continued to present issues even after the flow of mail began to recover. The subsequent report of progress in that function was a favorable sign, although it did not replace the confirmation that all of Microsoft 365 had returned to normal operation.

Extended monitoring will be the mechanism by which Microsoft will attempt to verify a complete resolution and prevent a temporary improvement from being confused with a definitive closure. While that process continues, the available information describes a situation in recovery, but still open, with varying levels of impact depending on the service and function each customer uses.

The disruption leaves a clear conclusion for users of enterprise platforms: availability may improve before the experience fully returns to normal.