Microsoft 365 experienced a major service disruption beginning on August 31, affecting businesses that depend on Microsoft’s cloud platform for email, collaboration, file access, administration, and security.
Exchange Online was the most visibly affected service, but the outage quickly expanded beyond email. Microsoft confirmed that the incident impacted multiple Microsoft 365 services because of a problem involving a shared authentication configuration.
As of September 2, Microsoft reports that service availability has recovered to above 99 percent across affected environments. Most users should no longer be experiencing problems, although Microsoft is still working through residual issues and has not yet marked incident MO1465074 as fully resolved.
What Caused the Microsoft 365 Outage?
Microsoft identified the cause as an issue involving a core authentication configuration used by multiple Microsoft 365 services.
Authentication sits at the center of many Microsoft cloud services. It determines whether users, devices, applications, and connected services can access Microsoft 365 resources.
Because the affected authentication component supported multiple services, the failure created a ripple effect throughout Microsoft’s cloud environment rather than remaining isolated to Exchange Online.
Microsoft lists the start of the incident as August 31, 2026, at 3:08 PM UTC, or 10:08 AM Central Time.
Exchange Online Was Hit Particularly Hard
Exchange Online became one of the most noticeable areas of disruption.
Users could experience problems such as:
- Delayed or failed email delivery
- Problems connecting to Exchange Online
- Authentication errors
- Incomplete or failed mailbox searches
- Administrative access problems
- Intermittent mailbox-operation failures
- Delays sending or receiving email through Outlook for iOS and Android
Microsoft tracked the Exchange-specific portion of the incident as EX1464935, while the broader Microsoft 365 outage is tracked under MO1465074.
Microsoft later confirmed that core Exchange Online mail flow and search functionality had recovered, although other dependent services continued experiencing residual problems during the recovery process.
The Outage Went Beyond Outlook and Email
One of the biggest lessons from this incident is how interconnected Microsoft’s cloud services have become.
The outage affected or degraded functionality across services including:
- Microsoft Exchange Online
- Outlook
- Microsoft Teams
- SharePoint Online
- OneDrive for Business
- Microsoft 365 Copilot
- Microsoft Defender XDR
- Microsoft Purview
- Microsoft 365 Admin Center
- Universal Print
- Microsoft Graph and REST-dependent integrations
Microsoft reported that SharePoint and OneDrive users could experience problems loading information, accessing files, retrieving search results, synchronizing OneDrive content, and performing other cloud operations.
Teams users also experienced issues involving search, calendars, presence information, channels, and some Teams Room devices.
Security and Administration Tools Were Affected Too
The incident was particularly significant for IT departments because productivity applications were not the only services affected.
Microsoft Defender XDR experienced intermittent authorization problems, while Microsoft Purview experienced access and processing issues during the outage. Both services were later reported as recovered.
That highlights an important consideration for businesses:
A cloud outage can impact not only the applications employees use, but also the security and administrative tools IT teams depend on to monitor those applications.
Organizations that rely heavily on cloud-based security platforms should understand what monitoring and response capabilities remain available when portions of the cloud environment become unavailable.
Was This a Cyberattack?
Based on the information Microsoft has released, there is currently no indication that the outage was caused by a cyberattack.
Microsoft has attributed the incident to a configuration problem involving its authentication infrastructure.
However, the symptoms demonstrate why outages and security incidents can sometimes look similar from the user’s perspective.
Employees may suddenly be unable to log in. Administrators may lose access to management portals. Applications may display authorization errors, and security platforms may become unavailable.
When that happens, IT teams should confirm whether a widespread vendor outage is occurring while still reviewing their own security monitoring for signs of suspicious activity.
Recovery Has Reached More Than 99 Percent
Microsoft’s latest telemetry indicates that service availability has recovered to above 99 percent across the affected environments.
The company says the majority of previously affected users should no longer see an impact.
Independent reporting on September 2 also noted that Microsoft continued to see availability remain stable above 99 percent, with only a smaller subset of users potentially experiencing residual problems.
However, Microsoft has continued to classify MO1465074 as a service degradation, meaning the incident was not yet officially closed at the time of this article.
Why Businesses Should Pay Attention
Microsoft 365 has become essential infrastructure for many organizations.
A typical business may rely on Microsoft for:
- Email through Exchange Online
- Communication through Teams
- Files through SharePoint and OneDrive
- Identity through Microsoft Entra
- Security through Microsoft Defender
- Device management through Intune
- Compliance through Microsoft Purview
- AI functionality through Microsoft 365 Copilot
That creates tremendous convenience and efficiency, but it also creates dependencies.
Moving business systems to the cloud does not eliminate outages. It changes how businesses need to prepare for them.
Even highly redundant global cloud platforms can experience service interruptions.
The goal should not be to assume an outage will never happen. Organizations should instead have procedures in place so employees and IT teams know what to do when one occurs.
Avoid Unnecessary Changes During a Confirmed Cloud Outage
One of the easiest mistakes an IT department can make during a major cloud outage is attempting to fix something that is not actually broken inside the organization.
If Microsoft has already confirmed a widespread service incident, administrators should be careful about making unnecessary changes such as:
- Resetting large numbers of passwords
- Rebuilding Outlook profiles
- Changing DNS configurations
- Reinstalling Office applications
- Modifying Conditional Access policies
- Removing and recreating Microsoft 365 accounts
- Changing authentication settings
These actions will not resolve an upstream Microsoft outage and may create additional problems after Microsoft restores service.
Check Microsoft Service Health Early
When multiple employees suddenly begin reporting similar Microsoft 365 problems, checking Microsoft’s Service Health information should be one of the first troubleshooting steps.
The Microsoft 365 Admin Center provides service-health information for administrators, including active incidents and advisories affecting an organization’s tenant.
Microsoft also provides public status information for situations where administrators cannot access the Admin Center.
For an IT department or managed service provider, knowing that Microsoft is experiencing an outage can prevent hours of unnecessary troubleshooting.
Microsoft 365 Backup Still Matters
The August 31 outage does not mean Microsoft lost customer data.
However, service availability and data protection are two different concerns.
Organizations should maintain appropriate backup and recovery strategies for important Microsoft 365 data, including:
- Exchange Online mailboxes
- SharePoint sites
- OneDrive files
- Teams-related data
- Other business-critical cloud information
Independent backups can provide additional protection against ransomware, accidental deletion, compromised accounts, malicious activity, retention problems, and other situations where information may need to be recovered separately from the primary Microsoft environment.
Every Business Should Have a Cloud-Outage Plan
Organizations that rely on Microsoft 365 should consider having a documented cloud-service continuity plan.
That plan should include:
- Alternative communication methods
- Microsoft 365 service-health monitoring
- Independent backups
- Emergency administrator access procedures
- Cybersecurity incident-response procedures
- Clear internal communication processes
- Business-continuity and disaster-recovery planning
Employees should also know where to receive company updates if Teams or Exchange Online becomes unavailable.
The Bigger Lesson
The August 31 Microsoft 365 outage demonstrates how interconnected modern cloud environments have become.
A problem involving one shared authentication component was able to disrupt email, file access, collaboration, administrative systems, security platforms, and AI-powered services.
For businesses, that means technology resilience can no longer focus on only servers, computers, and internet connections.
Organizations also need to consider what happens when a critical third-party cloud provider experiences an outage.
Cloud reliability is important. Cloud preparedness is equally important.
How MicroAdvantage Can Help
MicroAdvantage helps organizations manage, secure, monitor, and protect their Microsoft 365 environments.
Our Microsoft cloud and cybersecurity services can help with:
- Microsoft 365 administration
- Exchange Online
- Microsoft Teams
- SharePoint and OneDrive
- Microsoft Entra identity security
- Multi-factor authentication
- Conditional Access
- Microsoft Defender
- Microsoft Intune
- Microsoft 365 backup and recovery
- Cybersecurity monitoring
- Business continuity planning
If your organization depends on Microsoft 365, this outage is a good reminder to make sure your environment is secure, properly backed up, and prepared for the next unexpected service interruption.
Contact MicroAdvantage to discuss Microsoft 365 management, cybersecurity, backup, and business-continuity solutions for your organization.
Sources & References
Microsoft 365 Incident MO1465074 / Exchange Online Incident EX1464935
Incident reporting and Microsoft service-health updates documenting the outage, affected services, root cause, and recovery progress.
View Microsoft incident updates
BleepingComputer — Massive Microsoft 365 Outage Causes Authentication Issues and Service Failures
Independent reporting covering the initial outage and Microsoft’s subsequent recovery updates.
Read the BleepingComputer report
Microsoft Learn — Microsoft 365 Service Health
Microsoft guidance for administrators on reviewing active incidents and service advisories.
Microsoft 365 Service Health documentation
Information in this article reflects the status available on September 2, 2026. Incident MO1465074 remained under Microsoft service-health monitoring at the time of publication.