Microsoft 365 users are dealing with continued service disruptions on Wednesday, September 2, 2026, as Microsoft works to resolve an incident affecting multiple services across its cloud productivity platform.
The issue has been classified as a service degradation, meaning users may experience interruptions, slower performance or failures with certain features rather than a complete shutdown of Microsoft 365.
For businesses that depend on Microsoft 365 for email, collaboration, document management, security and administration, even partial problems can quickly become disruptive. The latest information indicates that Microsoft has made significant progress, but some users and organizations may still encounter problems while the company continues its recovery work.
Microsoft’s incident information says users may experience issues when using multiple Microsoft 365 services. The company has also highlighted an unusual complication: some Microsoft 365 administrators may be unable to access the admin center itself, making it harder for affected organizations to view service-health information through the usual route.
What is happening with Microsoft 365?
The current incident began on August 31 and expanded beyond the initial problems reported with Exchange Online.
According to Microsoft’s incident updates, the underlying problem is connected to a core authentication configuration used by multiple Microsoft 365 services. Microsoft has been working on mitigation measures and redeploying targeted fixes across affected infrastructure.
As of the latest update available on September 2, Microsoft said service availability had recovered to above 99% across affected environments and that most previously affected users should no longer be experiencing the disruption.
However, that does not necessarily mean every user is back to normal.
Microsoft continues to balance the deployment of fixes across remaining infrastructure while monitoring the platform for persistent recovery. Some scenarios can therefore remain degraded even as overall availability improves.
For businesses, this distinction matters. A service can appear largely operational while individual functions — such as search, authentication, synchronization or administrative tools — continue to experience problems.
Which Microsoft 365 services are affected?
The disruption has extended across a number of Microsoft 365 products and features.
Exchange Online has been among the most visible areas of impact. Users may have experienced difficulties connecting to the service or using certain functions, including search.
Microsoft Teams has also been affected. Reported problems have included search issues, stale presence information, problems with location updates, calendar functionality and difficulties involving Teams Rooms and desktop phones. Some administrators have also experienced issues with creating, editing or deleting Teams channels.
The impact has not been limited to communications.
OneDrive for Business and SharePoint Online users may encounter partial page failures, missing or outdated information, search problems, synchronization issues and difficulties opening files. Some users may also see repeated retries or timeouts instead of a complete service failure.
Microsoft 365 Copilot has also been part of the wider impact. Certain Copilot prompts that depend on Microsoft 365 data, including information from Exchange Online, may fail or perform poorly.
Security and compliance services have also been mentioned in the incident information. Microsoft Defender XDR and Microsoft Purview users may encounter intermittent authorization problems.
Universal Print is another affected area, with some users potentially unable to create, upload or retrieve print jobs.
Why authentication is such a big deal
At the heart of the incident is authentication.
Authentication is the process used to establish that a user or service is authorized to access a particular resource. In a cloud platform as interconnected as Microsoft 365, authentication is not simply about signing into Outlook.
Multiple Microsoft services depend on shared authentication components and infrastructure. If a problem occurs in a common authentication layer, its effects can spread across products that otherwise appear unrelated.
That helps explain why an issue that initially drew attention because of Exchange Online could subsequently affect Teams, SharePoint, Copilot, Purview, Defender and administrative functions.
Microsoft has said the issue involves a core authentication configuration and that affected authentication components did not deploy as expected to part of the infrastructure. The company has been applying targeted fixes and monitoring the recovery process.
For everyday users, this can produce confusing symptoms.
One person may be able to open Outlook but find that search is not working. Another may be able to send messages but have trouble accessing a SharePoint document. A Teams user may see stale presence information, while an administrator encounters authentication problems when trying to manage the environment.
In other words, a service degradation does not necessarily look the same for everyone.
Microsoft 365 administrators face an additional problem
Perhaps one of the most frustrating aspects of this incident is that administrators themselves may have difficulty accessing the Microsoft 365 admin center.
Normally, the admin center is one of the first places an IT team would go when users report problems. Microsoft’s Service health dashboard provides information about known incidents, affected services, current status and mitigation work. Microsoft recommends checking this dashboard before spending significant time troubleshooting an issue that may already be known.
But during this incident, administrators may be unable to authenticate into the admin center.
That is why information about the incident has been made available through Microsoft’s public service-status channels. Microsoft specifically notes that this approach is important because administrators may not be able to access the normal Service health experience.
For IT teams, the situation is a reminder that cloud-service monitoring needs more than one source of information.
Is Microsoft 365 completely down?
No — describing the situation as a total Microsoft 365 outage would be misleading.
The incident is classified as a service degradation, and Microsoft’s latest update indicates that service availability has recovered to above 99% across affected environments.
However, “99% available” does not mean every feature is functioning perfectly for every customer.
Some users may still encounter isolated problems, particularly with functionality that depends on the affected authentication infrastructure. Microsoft has said that a small subset of users could continue to experience impact while mitigation work progresses.
This is particularly important for large organizations. A relatively small percentage of affected users can still represent hundreds or thousands of employees in a large enterprise.
What should Microsoft 365 users do?
For most users, the best approach is to avoid making unnecessary changes to accounts or devices simply because a Microsoft 365 feature is temporarily failing.
If Outlook, Teams, SharePoint or another Microsoft 365 application is behaving strangely, users should first determine whether the problem is part of the wider incident.
Administrators who can access the Microsoft 365 admin center should check Health > Service health for tenant-specific information. Microsoft says the Service health dashboard displays the current health of cloud services and provides details about active incidents and advisories.
If the admin center cannot be accessed, Microsoft recommends using its service-status information to check for known login-related problems.
Users should also be careful about repeatedly changing passwords, reinstalling applications or making major configuration changes while a known cloud-side incident is still being investigated.
A temporary failure to access a Microsoft service does not automatically mean there is a problem with an individual account or computer.
What happens next?
Microsoft’s focus is now on completing mitigation across the remaining affected infrastructure and ensuring that the recovery remains stable.
The company has indicated that it is monitoring telemetry and carefully balancing the rollout of fixes to avoid creating additional disruption.
That final stage can sometimes take longer than the initial recovery. Restoring access is one thing; confirming that all dependent services, authentication paths and connected features are behaving normally is another.
For businesses, the priority should therefore be monitoring rather than assuming that every issue has disappeared simply because the major symptoms have improved.
The September 2 incident also highlights an important reality of modern cloud computing: when organizations consolidate email, collaboration, file storage, security, administration and AI tools onto one ecosystem, a problem in a shared underlying component can have consequences across many parts of the workplace.
Microsoft 365 remains broadly operational, but some customers may continue to experience isolated problems as Microsoft completes its recovery work.
For now, organizations should keep an eye on Microsoft’s service-health communications, communicate clearly with employees about known issues and avoid treating every individual symptom as a separate technical problem.
The latest information suggests that recovery is well underway. But until Microsoft declares the affected services fully restored, businesses should expect that some Microsoft 365 features may continue to behave inconsistently.
As cloud services become increasingly central to everyday work, incidents like this are a reminder that availability is not simply about whether an application opens it is also about whether the individual features and authentication systems behind it are working as expected.
