Takeaway: This is a retrospective of the November 12–14, 2026, Microsoft 365 outage, not a report of an active incident. At 2:09 p.m. Saturday, November 14, 2026, Asia/Shanghai, Microsoft 365 Status said it had “completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions,” and pointed admins to incident MO1550821 in the Microsoft 365 admin center. A Monday, November 16, 2026, recheck found that official restoration wording unchanged. The public Microsoft 365 status page no longer described an active Microsoft 365 service degradation, and the consumer products section showed as Operational, with Azure still listed as having no issues. That Saturday afternoon restoration post came after a Saturday morning (8:30 a.m. Asia/Shanghai) recheck when the Service Health Status page and the Microsoft 365 status page had still shown an active Microsoft 365 service degradation, including consumer products. In official posts on Friday, Microsoft and Microsoft 365 Status apologized, said the incident was “a technical issue not related to cyber or AI / agents,” and attributed it to “an issue during an earlier network capacity upgrade that surfaced following a recent network change.” If you still cannot sign in or mail is delayed, check the live status page and your tenant’s admin-center incident notes rather than assuming a local app fix.
The outage began on Thursday afternoon, November 12, in U.S. time. CNBC, citing Downdetector, said problems started shortly before 1 p.m. and that about 130,000 users reported Outlook issues. ABC News later reported a Downdetector US peak of more than 120,000 Outlook reports and more than 45,000 Microsoft 365 reports around 4:20 a.m. Australian Eastern time. Those tracker counts are not Microsoft’s official impact numbers, and they move as the incident does.
What Microsoft says is affected
The official status page lists this as a service degradation, not a complete global shutdown of every Microsoft product. The user-impact line is broader than any single app: people “may be unable to connect to multiple Microsoft 365 services.” The potentially impacted services Microsoft named are:
- Exchange Online, which is the service behind Outlook on the web and work email
- Microsoft Teams
- SharePoint Online
- Microsoft Copilot 365
- Microsoft Defender XDR and Microsoft Defender for Office 365
- Microsoft Planner and Microsoft To Do
- Microsoft Intune
- Microsoft Purview, including Authorization, Auto Labelling, Data Loss Prevention (DLP), Communication Compliance, and Data Classification
- Power BI, specifically intermittent failures exporting reports with MIP sensitivity labels to PDF
- Microsoft 365 Apps Admin Center, including Cloud Update, Cloud Policy, and Inventory
- Universal Print, where users may see errors submitting print jobs or using admin features
- Windows 365, for customers who configured their tenant and Cloud PCs to use Microsoft Purview Customer Key, who may be unable to connect to those Cloud PCs
OneDrive is not named on that official list, even though some organizations and users have reported file-access problems alongside Outlook and Teams. We are sticking to Microsoft’s list unless the status page adds OneDrive. The same page also says the degradation covers Microsoft 365 (Business or Enterprise) and Microsoft consumer products, but the detailed service list is written in Microsoft 365 terms.
Microsoft’s public status page says “No Azure issues detected at this time.” CNBC also reported that Amazon Web Services said it was “operating normally” and that some reports of AWS trouble were inaccurate. This article is about the Microsoft 365 incident, not a multi-cloud event.
What went wrong, in Microsoft’s own updates
Microsoft’s early public comments, reported by CNBC, said the company was investigating issues with Microsoft 365 services, “primarily issues with Exchange Online.” Later official updates, also quoted there, walked the diagnosis forward. Microsoft first pointed to elevated load across multiple regions, then said the elevated load was not from an overall traffic spike. A large number of servers were “unexpectedly unavailable,” which shifted load onto the remaining infrastructure. Some servers were also failing automated health checks.
The 12:08 a.m. UTC status update is more specific about why recovery has been uneven. Microsoft says servers it has already returned to service “initially remain healthy,” but “they can become unresponsive again once they begin receiving traffic.” Engineers are analyzing diagnostic data with networking and platform teams to find what triggers that behavior.
By late morning in Australia and around noon on Friday in Asia/Shanghai, The Guardian was quoting a later Microsoft website update: “We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected.” Microsoft also said it was “identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances.” In earlier updates summarized in the same live blog, Microsoft said a process on affected servers that establishes a secure connection can become overwhelmed and stop processing requests; it was preparing a configuration change to test on a subset of servers, and rolling back a recent configuration change that had correlated with the start of the outage. The same coverage said Microsoft described Teams chats and online meetings as remaining “largely functional,” while meeting scheduling and creating chats could still be affected because of Exchange, and users might still be unable to access an Outlook inbox. Those mid-incident details are attributed to The Guardian’s account of Microsoft’s updates. Our Friday noon recheck of the public status pages still showed an active degradation, but did not independently display those newer sentences in the public HTML.
Later on Friday, Microsoft published a clearer official account in its own posts. In a 12:40 a.m. Saturday, Asia/Shanghai statement from the main Microsoft account, later repeated by Microsoft 365 Status, the company said: “We are deeply sorry for the disruption this incident has caused our customers and partners.” It added: “This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. We have addressed the underlying issue and continue to restore service to remaining customers and regions.” Microsoft also said that, given the scale of demand, it restored services gradually, “validating stability at each stage,” and that it will provide a full post-incident report once its review is complete. An earlier Friday afternoon post from both accounts had already said there was “no indication this is the result of malicious or cyber activity.”
Recovery still was not complete overnight. In a 4:05 a.m. Saturday, Asia/Shanghai update, Microsoft 365 Status said: “As infrastructure stabilizes, we’re still draining queued messages and rebalancing traffic, so customers may see improved sign-in/access while delivery and processing continue to catch up. We do not have an ETA for full recovery yet. Service access can recover before mail flow fully normalizes.” A follow-up at 5:55 a.m. Saturday, Asia/Shanghai said the company continued to observe “sustained service recovery across the previously affected environments,” was “monitoring for an extended period to ensure no additional mitigative actions are required,” and was “monitoring the backlog of email messages accrued during this event to ensure all process successfully before considering the issue resolved.” Our Saturday morning recheck of the public status pages, around 8:30 a.m. Asia/Shanghai on November 14, still showed the same active Microsoft 365 service degradation and the same user-impact line. Then, at 2:09 p.m. Saturday, Asia/Shanghai (6:09 a.m. UTC), Microsoft 365 Status said: “We have completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions. Further updates can be found at MO1550821 in the Microsoft 365 admin center.”
Those three bullets were not in the Saturday afternoon restoration post, which only announced that the underlying issue had been addressed and that remaining customers and regions had been restored. Earlier in the incident, before that post, Microsoft’s public updates described three recovery steps:
- Protective traffic management is already in place. Microsoft is also temporarily limiting which types of traffic can reach affected infrastructure in specific locations, to see whether a particular request type is contributing to the impact and to restore service incrementally.
- A subset of affected servers is being rebuilt with a previous software configuration, to test whether that stops them from becoming unresponsive. Microsoft says it will expand that approach if the results are positive.
- Earlier in the incident, Microsoft had already begun returning a portion of affected servers to service, shifting traffic and connections to alternative pathways, and implementing protective traffic management in a specific location, with plans to widen those measures if they helped. As capacity comes back, Microsoft says users “may experience a gradual recovery as their clients reconnect to the service.”
That last point matters for anyone staring at a spinning Outlook or Teams window: even when Microsoft restores capacity, clients may take time to reconnect. A still-broken session is not, by itself, proof that the incident is unchanged.
If you still have problems after the restoration
Microsoft now says service has been restored to remaining impacted customers and regions. If you still cannot reach Outlook, Teams, SharePoint, or Copilot 365, the practical steps are simple and limited:
- Check Microsoft’s Service Health Status page or the Microsoft 365 status page before opening a pile of support tickets. Microsoft’s latest official public update says the incident was restored on November 14; use the live status page to see whether a new issue has been posted.
- If you are a Microsoft 365 admin, use the Service health view in the Microsoft 365 admin center for tenant-specific messages and incident IDs. The public page is a summary, not a substitute for your tenant’s own health messages.
- Plan for delayed mail, meeting joins, and file access rather than assuming a local Outlook or Teams reinstall will fix a service-side outage.
- Do not treat unofficial workarounds circulating on social media as official guidance. Microsoft has not published a customer-side fix on the public status page; the work it describes is on its own servers, traffic paths, and software configuration.
- If you also use Azure, do not assume this outage extends there. Microsoft’s public status page listed no Azure issues during the incident and still listed none in the November 16 recheck.
Newsrooms including The Guardian and the BBC have also been covering the disruption as a global connectivity problem across Microsoft 365 apps. Those reports are useful context for how widely the issue was felt. For any later incident or residual tenant-specific issue, prefer Microsoft’s timestamped status updates and admin-center notes over this retrospective.
How to read this retrospective
This article is a retrospective snapshot as of Monday, November 16, 2026, two days after Microsoft 365 Status’s 2:09 p.m. Asia/Shanghai update on Saturday, November 14, in which the company said it had completed work on the underlying issue and restored service to remaining impacted customers and regions. A November 16 recheck found that official wording unchanged, and the public status page no longer described an active Microsoft 365 service degradation. This is not a substitute for Microsoft’s promised post-incident report. Microsoft has said the incident was a technical issue, not related to cyber activity or AI agents, introduced by a problem during an earlier network capacity upgrade that surfaced after a recent network change. A Saturday morning recheck of the public status pages, at 8:30 a.m. Asia/Shanghai, had still listed an active degradation. If Microsoft later publishes the post-incident report, that will belong in a further update.
Microsoft 365 outage facts at a glance
| Item | What official and contemporaneous sources said |
|---|---|
| Status as of Nov 16, 2026 | Official Microsoft 365 Status post at 2:09 p.m. Asia/Shanghai on Nov 14 still stood: the company had “completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions,” with further updates in admin-center incident MO1550821. A Monday, Nov 16 recheck found that wording unchanged; the public status page no longer described an active Microsoft 365 degradation, and consumer products showed as Operational. A Saturday morning (8:30 a.m. Asia/Shanghai, Nov 14) recheck of the public status pages had still shown an active degradation, including consumer products; Azure was listed with no issues then and in the Nov 16 recheck |
| Official / contemporaneous sources | Microsoft Service Health Status; the Microsoft 365 status page; official posts from Microsoft, Microsoft 365 Status (early Saturday), and the 2:09 p.m. Asia/Shanghai restoration update |
| User impact | During the incident, users may have been unable to connect to multiple Microsoft 365 services. Microsoft now says service has been restored to remaining impacted customers and regions |
| Named services | Exchange Online, Teams, SharePoint Online, Copilot 365, Defender products, Planner, To Do, Intune, Purview, Power BI (label-to-PDF export), Apps Admin Center, Universal Print, and some Windows 365 Customer Key configurations |
| Microsoft’s current diagnosis | Official Friday posts: a technical issue “not related to cyber or AI / agents,” introduced by “an issue during an earlier network capacity upgrade that surfaced following a recent network change.” Earlier in the incident, Microsoft also said a large number of servers became unexpectedly unavailable and that some restored servers became unresponsive again under traffic |
| What Microsoft is doing | In the official Saturday afternoon post, Microsoft 365 Status said it had completed efforts to address the underlying issue and restored service to remaining impacted customers and regions. Earlier Saturday posts described draining queued messages, rebalancing traffic, and monitoring the email backlog before considering the issue resolved. Microsoft has also said it will provide a full post-incident report once its review is complete |
| Azure | No Azure issues detected on the public status pages at the Saturday morning, November 14, Asia/Shanghai recheck |
| Downdetector figures (not official) | CNBC reported about 130,000 Outlook reports; ABC News reported a US peak above 120,000 Outlook reports |
FAQ
Is Microsoft 365 still down?
Not according to Microsoft’s latest official public update. At 2:09 p.m. Asia/Shanghai on Saturday, November 14, 2026, Microsoft 365 Status said it had completed work on the underlying issue and “restored service to the remaining impacted customers and regions.” A Monday, November 16 recheck found that wording unchanged, and the public status page no longer described an active Microsoft 365 service degradation. A Saturday morning recheck of the public status pages had still shown an active degradation. If you still see errors, check the live status page and, for work accounts, incident MO1550821 in the Microsoft 365 admin center.
Which apps are affected by the November 2026 Microsoft outage?
Microsoft’s official list includes Exchange Online (Outlook email), Teams, SharePoint Online, Microsoft Copilot 365, several Defender and Purview services, Planner, To Do, Intune, parts of Power BI export, the Microsoft 365 Apps Admin Center, Universal Print, and some Windows 365 Cloud PCs that use Purview Customer Key. OneDrive is not named on that list.
What is causing the Microsoft Outlook and Teams outage?
In official Friday posts, Microsoft said this was “a technical issue not related to cyber or AI / agents,” introduced by “an issue during an earlier network capacity upgrade that surfaced following a recent network change.” Earlier in the incident, it also said a large number of servers became unexpectedly unavailable and that some restored servers became unresponsive again under traffic. Microsoft has said it will provide a full post-incident report once its review is complete.
Is Azure down too?
Not according to the same public status page, which said “No Azure issues detected at this time.” A Microsoft 365 outage can feel like “the cloud is down” without Azure itself being in incident status.
Should I reinstall Outlook or clear my Teams cache?
Microsoft’s public updates describe a service-side incident, not a client bug, and they do not list a reinstall as the fix. Now that Microsoft says service has been restored, restarting Outlook or Teams is reasonable if a client still looks stuck. That will not fix a remaining service-side problem if one still exists in your tenant.
When will the Microsoft 365 outage be over?
Microsoft said the outage was over on Saturday, November 14, 2026. At 2:09 p.m. Asia/Shanghai that day, Microsoft 365 Status said it had restored service to remaining impacted customers and regions. Earlier the same morning, it had said it did not have an ETA for full recovery and was still monitoring the email backlog. A November 16 recheck found the official restoration wording unchanged and no active public Microsoft 365 degradation posted. If sign-in works but mail still looks delayed, or if a work tenant still shows errors, check the live status page and admin-center incident MO1550821 rather than relying on this snapshot.
Are consumer Microsoft accounts affected, or only work accounts?
During the incident, the public status page said the degradation covered Microsoft 365 (Business or Enterprise) and Microsoft consumer products. Microsoft’s Saturday restoration update said service was restored to remaining impacted customers and regions, without separating consumer accounts from work accounts in that post. If a personal Outlook.com or Microsoft 365 account still fails, check the live status page.
Where should I check for the latest official update?
Start with msit.status.cloud.microsoft or status.cloud.microsoft/m365. Official incident posts also appear on the Microsoft 365 Status account. Microsoft 365 admins should also watch Service health in the admin center, including incident MO1550821, which can carry tenant-specific information that the public page does not show.
