Microsoft Outage: Microsoft 365, Outlook, Teams, Azure and Microsoft Store Hit by Service Disruptions

Update (16 Sep): Microsoft is having a major outage. Teams, Outlook, Microsoft 365 and more down. Live status below.

Update (13 Sep): Multiple Reports of Outlook Outage. Live Status Below.

Microsoft services are experiencing widespread disruption today, with users reporting problems affecting Microsoft 365, Outlook, Teams, Azure and the Microsoft Store.

The disruption is developing across multiple Microsoft services, with Microsoft 365 administrators reporting Exchange Online problems under tracked incident EX1464935.

At the same time, users are reporting connectivity and availability problems involving Microsoft Azure, while reports of issues with Outlook, Microsoft Teams and the Microsoft Store are also circulating.

The exact relationship between these service disruptions has not yet been confirmed by Microsoft.

LIVE STATUS: Microsoft continues to work on EX1464935 and MO1465074. The outage began affecting Exchange Online and later expanded to multiple Microsoft 365 services. Microsoft says mitigation is producing gradual recovery, but some users may continue experiencing degraded functionality and mail delays. September 2 – Xbox live, Outlook, 365, Microsoft Store and Minecraft facing widespread outage.

Timeline of the entire incident is posted below (Ongoing Incident)

Microsoft 365 outage: Outlook users report email problems

The most clearly identified Microsoft 365 incident is EX1464935, which affects Exchange Online.

Users affected by the incident may experience problems sending or receiving email, authentication errors when accessing Exchange Online, intermittent mailbox failures and difficulties with related administration functions.

Reports from Microsoft 365 administrators indicate that the impact is not necessarily universal. Some organizations remain operational while others are experiencing significant problems.

Community reports include failures to send or receive messages, Outlook on the web connectivity problems and synchronization failures. Some administrators have reported that classic Outlook continues working while newer Outlook experiences problems.

Microsoft incident EX1464935

Microsoft’s tracked incident is:

• Incident: EX1464935
• Service: Exchange Online
• Status: Investigating
• Impact: Some users may be unable to connect to or experience degraded functionality with Exchange Online
• Potential symptoms: Email delays, failed sending or receiving, authentication errors and intermittent mailbox-operation failures

Microsoft is continuing to investigate the incident and determine its full scope.

Azure users also reporting problems

The disruption extends beyond Microsoft 365 reports, with a significant increase in user reports involving Microsoft Azure.

Independent monitoring currently shows elevated Azure outage reports from multiple regions. StatusGator recorded more than 160 user-submitted Azure outage reports over the previous 24 hours, including reports of service outages, slow performance and connectivity problems.

Reports have come from users in locations including the United States, United Kingdom, India, Vietnam, Australia and other regions.

However, Azure’s overall official status can differ from individual service or regional conditions. A third-party status tracker currently reports Azure as operational despite the elevated number of user reports.

This means the situation may involve specific Azure services, regions or workloads rather than a complete global Azure outage.

Is Microsoft Teams down?

Microsoft Teams is also generating outage reports today.

Users have reported Teams failing to load or connect, although current monitoring does not indicate that Teams is universally unavailable. StatusGator’s latest check showed Teams operational while still recording user-submitted outage reports.

There is also a separate ongoing Teams issue affecting users running the application in Virtual Desktop Infrastructure environments. Microsoft reference TM1463371 relates to Teams optimization failures for certain VDI users following a newer Teams release.

That Teams incident should not automatically be attributed to EX1464935.

Microsoft Store outage reports

Users are also reporting problems accessing the Microsoft Store.

At this stage, Microsoft has not publicly established that Microsoft Store problems are directly caused by the Exchange Online incident EX1464935.

The simultaneous appearance of problems across several Microsoft services has nevertheless raised concerns among users about a broader Microsoft infrastructure disruption.

More information will be needed from Microsoft’s service-health systems before the different incidents can be definitively linked.

September 2 – Xbox and Minecraft Down too

Microsoft Services Outage Timeline

August 31, 2026

UTC	Event
15:08 UTC	Microsoft records the start of the Exchange Online impact associated with EX1464935. The issue involves degraded Exchange Online functionality and authentication problems.
~16:01 UTC	Microsoft 365 Status publicly begins reporting the Exchange Online issue, asking administrators to follow EX1464935.
16:16 UTC	Microsoft says it is reviewing telemetry and diagnostic data after an increase in user reports.
16:33 UTC	Microsoft identifies a common failure pattern associated with authentication and protocol connectivity and begins analyzing the underlying cause.
17:23 UTC	Microsoft identifies a potential corrective action and begins evaluating deployment options.
18:18 UTC	Microsoft says it is testing its remediation strategy while investigating whether other Microsoft 365 services are also affected.
18:41 UTC	Microsoft continues fine-tuning its remediation strategy and says it will provide an estimated remediation time when available.
19:43 UTC	Microsoft says it is conducting comprehensive testing and exploring alternative remediation options.
20:36 UTC	Microsoft begins examining recent service changes and whether authentication components are failing to deploy correctly. A rollback of a recent update is considered as one possible recovery option.
21:27 UTC	Microsoft says testing of mitigation strategies is producing positive results, but the incident remains active.
~22:00 UTC	Microsoft expands its investigation and continues working on targeted remediation for the affected infrastructure.
22:55 UTC	Microsoft begins deploying a targeted mitigation to re-apply core authentication components across affected environments. Users may begin seeing gradual recovery.
23:53 UTC	Microsoft reports residual impact, particularly affecting downstream scenarios such as search. Engineers begin incrementally restarting affected infrastructure.

September 1, 2026

UTC	Event
00:01 UTC	Microsoft continues the mitigation and keeps EX1464935 open because Exchange Online remains the most heavily affected service.
01:01 UTC	Microsoft confirms that the authentication component problem affects services beyond Exchange Online and directs administrators to MO1465074 for the broader Microsoft 365 impact.
02:39 UTC	Microsoft reports continued work to restart affected infrastructure and re-apply the targeted authentication fix. Exchange Online remains degraded and the incident has no end time.
~03:00 UTC	Microsoft continues mitigation and says users can still experience varying degrees of impact and mail delays. The official Microsoft 365 Status account reports gradual improvement but no full resolution.
18:29 UTC	Microsoft says most users should see recovery across the majority of affected scenarios, although some scenarios remain degraded while mitigation continues.
21:30 UTC	Microsoft says most users should see recovery, but some scenarios, particularly those relying on Graph API and REST connection methods, remain degraded.

September 2, 2026

UTC	Event
00:39 UTC	Microsoft reports that service availability has recovered to above 99% across affected environments, with the majority of previously affected users expected to no longer experience impact. Work continues on remaining infrastructure to ensure persistent recovery.
12:30 UTC	User reports of Xbox Live connectivity/service problems begin appearing along with Microsoft store, Minecraft, Outlook, Microsoft 365.
13:30 UTC	Users report increasing errors in Outlook
14:40 UTC	Xbox Online issues resolved

September 14, 2026

UTC	Event
10:25 UTC	Initial Reports of Outlook and SharePoint Outage
10:35 UTC	Microsoft Confirms Outage for Japan
11:30 UTC	Incident Tracked as SP1471596 and OD1471597
11:35 UTC	Microsoft Confirmed Recovery
12:15 UTC`	Multiple Reports of Outlook Outage

September 16, 2026

14:10 UTC	Microsoft has acknowledged this issue. Tracked under MO1472904
12:55 UTC	Initial Reports of Microsoft 365, Outlook, Teams, Azure, Entra and more outage

What is happening with Microsoft right now?

The current situation appears to involve several overlapping service disruptions:

Microsoft service	Current situation
Microsoft 365	Users reporting service problems
Outlook / Exchange Online	EX1464935 under investigation
Microsoft Teams	User reports of connectivity/loading problems. Mostly Fixed
Azure	Elevated outage reports across multiple regions/services Update: Fixed Now
Microsoft Store	Users reporting availability problems
Microsoft 365 administration	Some administrators reporting access/functionality problem. Mostly fixed
Xbox Live	Multiple users are reporting connection issues Update: Fixed Now

When did the outage spread beyond Outlook?

As the incident progressed, Microsoft confirmed that the authentication problem extended beyond Exchange Online. The company opened broader incident MO1465074 covering multiple Microsoft 365 services, including OneDrive for Business, SharePoint Online, Microsoft Teams, Microsoft Purview and Microsoft Defender XDR.

The latest Microsoft incident information says the underlying problem was an issue within a core authentication configuration used by multiple Microsoft 365 services. Microsoft subsequently worked on re-applying the affected authentication components and restarting portions of the affected infrastructure.

Why this could be a major Microsoft outage

Microsoft’s cloud ecosystem is highly interconnected. Exchange Online powers email and calendar functionality for Microsoft 365 customers, while Azure provides infrastructure and services used by Microsoft’s own products as well as millions of third-party applications.

A disruption affecting a shared dependency can therefore produce symptoms across seemingly unrelated products.

However, it would be premature to conclude that today’s Outlook, Teams, Azure and Microsoft Store reports all originate from one common infrastructure failure.

Microsoft’s investigation into EX1464935 should provide more information about the Exchange Online portion of the incident.

What should Microsoft 365 and Azure users do?

If your organization is experiencing problems, administrators should first check Microsoft’s official service-health dashboards rather than immediately changing configurations or credentials.

Users can also:

1. Check whether Outlook works through both the desktop application and web interface.
2. Test whether Microsoft Teams can connect.
3. Check Microsoft 365 Service Health if they have administrator access.
4. Check Azure Service Health for affected subscriptions and regions.
5. Determine whether the problem affects all users or only specific accounts.
6. Avoid repeatedly changing passwords or reinstalling applications while Microsoft investigates a service-side issue.

Microsoft outage still developing

The Microsoft outage situation is still developing.

The clearest confirmed Microsoft 365 issue at this point is Exchange Online incident EX1464935, while reports involving Azure, Teams and the Microsoft Store are being observed separately.

The scale of today’s reports means this could become a significant Microsoft service disruption, but the available evidence does not yet establish a single root cause connecting every affected product.

Microsoft users experiencing Outlook, Teams, Azure or Microsoft Store problems should expect intermittent failures or degraded functionality while the situation develops.

We will update this article as Microsoft publishes additional information about EX1464935 and any related service incidents.