Microsoft 365 Outage 2026: Why Outlook, Teams and Copilot Stopped Working
The Microsoft 365 outage that started on Thursday, November 12, 2026, cut off Outlook email, parts of Teams and Microsoft 365 Copilot for businesses, schools and government offices on several continents. Microsoft says it restored service early on Saturday, November 14, after an incident that ran for more than 24 hours.
This guide covers the timeline, what Microsoft has said about the cause, what it has not confirmed, who was affected, and what users and IT admins should do next. Microsoft has promised a post-incident report but had not published one in the sources checked, so the cause section may change once it appears.
Last updated: November 14, 2026.
Microsoft 365 Outage at a Glance
| Detail | What is confirmed |
|---|---|
| Start | Thursday, November 12, 2026. User reports surged in the early afternoon, US Eastern time. Outlets give slightly different start minutes. |
| Duration | More than 24 hours. Microsoft said early on Saturday, November 14, that it had restored service to the remaining impacted customers and regions. |
| Incident IDs | EX1550543 (Exchange Online) and MO1550821 (wider Microsoft 365) |
| Services Microsoft listed | Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR |
| Peak user reports | More than 130,000 Outlook problem reports on Downdetector on Thursday, per CBS News and the Associated Press |
| Stated cause | A fault introduced during an earlier network capacity upgrade that surfaced after a recent network change |
| Cyberattack | Microsoft reports no evidence of malicious activity and says the incident was not related to cyber activity or AI agents |
| Post-incident report | Promised by Microsoft. Not found in the sources checked as of November 14, 2026 |
Timeline of the Microsoft 365 Outage
Times below are US Eastern, as each outlet reported them. Outlets differ on the exact start minute, so treat the early rows as approximate.
| When | What happened | Source |
|---|---|---|
| Thursday, Nov 12, earlier in the day | A separate Teams incident hit users in North and South America. Microsoft did not say whether it was related. | BleepingComputer |
| Thursday, Nov 12, just after 1:45 p.m. | Reports of Outlook and Microsoft 365 failures begin to appear on social media and Downdetector. | XDA |
| Thursday, Nov 12, before 3 p.m. | Microsoft says affected servers are failing automated health checks. It tests a workaround that bypasses the component handling those checks and looks into high processor use. | SecurityWeek |
| Thursday, Nov 12, 6:57 p.m. | Limited recovery after Microsoft returns some servers to service. | BleepingComputer |
| Thursday, Nov 12, 9 p.m. | Restarting servers shows signs of improvement. Microsoft begins rolling back a recent network configuration change that coincided with the start. | SecurityWeek |
| Friday, Nov 13, early morning | Microsoft reports no indication of malicious activity. It says recovery is moving in phases and capacity has not fully returned to normal. | CBS News / AP |
| Friday, Nov 13, 8:05 a.m. | Services recover gradually. Email access and delivery improve. | BleepingComputer |
| Friday, Nov 13 | Microsoft apologizes, names an earlier network capacity upgrade as the origin of the fault and says the underlying issue has been addressed. | CNBC, CNN |
| Friday, Nov 13, 7:42 p.m. | Most apps are back online. Outlook is still slow and some features stay degraded. | XDA |
| Saturday, Nov 14, early morning | Microsoft says it has completed work on the underlying issue and restored service to the remaining impacted customers and regions. | CBS News / AP |
Why Did Outlook, Teams and Copilot Stop Working?
Microsoft says a fault introduced during an earlier network capacity upgrade surfaced after a recent network change. On the affected servers, a process that sets up secure connections became overwhelmed, and the servers stopped handling requests. Microsoft has not yet published the full root cause.
Microsoft’s Stated Cause
Microsoft’s explanation became more specific in three steps as the incident went on.
Step 1: Servers Failed Health Checks
Early updates said affected servers were failing automated health checks and dropping out of service. Microsoft traced the extra load to the large number of unavailable servers, which left the remaining systems to carry the traffic. It said total traffic had not increased.
Step 2: The Secure-Connection Process Was Overwhelmed
By Thursday night, Microsoft said a process on the affected servers, the one responsible for establishing secure connections, was becoming overwhelmed. That made the servers stop processing requests.
Step 3: Restarts, a Bypass and a Rollback
Microsoft restarted affected servers, tested a workaround that bypasses the health-check component and began rolling back a recent network configuration change that coincided with the start. Its Friday statement then named an earlier network capacity upgrade as the origin. Microsoft has not said which of these actions or changes was the root cause.
Why Teams and Copilot Failed Too
Microsoft said features across Microsoft 365 that interact with Exchange Online and email were affected, while parts that do not depend on Exchange Online kept working. That shared dependency is how a problem in Exchange Online reached Teams and Copilot.
What Microsoft Has Not Confirmed
| Open question | Status as of November 14, 2026 |
|---|---|
| Final root cause | Microsoft says its post-incident report will give full details of the root cause and repair items. |
| Which change exposed the fault | Microsoft names an earlier network capacity upgrade and a recent network change. It has not published how the two connect. |
| Azure Virtual Network involvement | One report, citing sources, linked the outage to configuration changes in Azure Virtual Network. Microsoft has not confirmed this. RansomNews relays the claim. |
| Link to November Patch Tuesday | Microsoft’s service advisories have not linked the November 10 updates to the outage. |
| Data exposure | No source checked reports data theft, and Microsoft reports no malicious activity. |
| Report date | Microsoft has not given a publication date for the post-incident report. |
Impact by Service: Outlook, Teams and Copilot
Outlook and Exchange Online
Microsoft first said users in the Americas had trouble connecting to Exchange Online mailboxes, then widened the list of affected services. More than 130,000 users reported Outlook problems on Downdetector at the Thursday peak. On Friday, Microsoft said service availability and email delivery were improving across a growing share of affected infrastructure.
Some Google Workspace users also reported trouble reaching Google-hosted email through Outlook desktop and mobile apps, according to SecurityWeek.
Microsoft Teams Outage
A separate Teams incident hit North and South America earlier on Thursday, and Microsoft did not say whether the two were related. During the main outage, some users reported that Teams chat still worked while email and Copilot did not. That matches Microsoft’s statement that parts of Microsoft 365 with no Exchange Online dependency stayed up.
Microsoft 365 Copilot Outage
Copilot Chat
Users might be unable to load Copilot Chat or receive replies in the web and desktop apps.
Access to Work Data
Copilot experiences might be unable to reach work data such as email, calendar and files.
SharePoint Online, Defender XDR and Safe Links
SharePoint Online and Defender XDR were on Microsoft’s list for incident MO1550821. Safe Links, part of Defender for Office 365, might be unable to verify URLs, which could affect people clicking links in Outlook and Teams.
Who Was Affected Worldwide
- Businesses: Workhorse Group delayed a quarterly earnings call. A Hong Kong aluminum firm said its Outlook accounts could not receive updates from US customers.
- Governments: Singapore’s Government Technology Agency said government emails were down. The Philippines’ Supreme Court said some operations, including email replies, were affected. Japan’s Deputy Chief Cabinet Secretary Masanao Ozaki said government IT infrastructure was hit.
- Airlines: Air India said flight operations were unaffected and temporarily rerouted its email services. IndiGo reported disruption to email support, with flights unaffected.
- Schools and events: One school said students could not reach lessons. Delegates at the COP31 climate summit in Antalya, Türkiye, faced coordination problems.
- AI platforms: OpenAI said new connections through its Microsoft connectors might be broken. Anthropic reported trouble with its Microsoft 365 connector.
- Markets: Microsoft shares fell before the open on Friday.
Sources for this list: CBS News / AP, ABC News Australia and Quartz.
Was the Microsoft 365 Outage a Cyberattack?
Microsoft says no. Its status page said it had no evidence of malicious activity, and Charles Lamanna, Microsoft’s executive vice president of Copilot, Agents and Platform, posted on X that nothing pointed to malicious or cyber activity. Microsoft’s Friday statement called it a technical issue not related to cyber activity or AI agents.
Australia’s Home Affairs Minister Tony Burke told reporters that Microsoft did not believe it faced a cyberattack and saw something closer to the 2024 CrowdStrike case, where a faulty update caused the damage.
The outage came two days after Microsoft’s November Patch Tuesday release, which addressed 1,094 vulnerabilities, including CVE-2026-124194, an Outlook spoofing flaw Microsoft says attackers have exploited. Microsoft’s service advisories have not linked that flaw or the updates to the outage. Treat any claim of a hack as unconfirmed until the post-incident report says otherwise.
Is the Outage Fixed? Current Status
Microsoft said early on Saturday, November 14, that it had completed its work on the underlying issue and restored service to the remaining impacted customers and regions. Recovery had been uneven on Friday: Microsoft described “encouraging recovery progress,” yet service health stayed variable and capacity had not fully returned to normal. If you still see problems, check Service Health in your Microsoft 365 admin center for EX1550543 and MO1550821 instead of relying on social posts.
What to Do After the Outage
For Everyday Users
- Check the Microsoft 365 status page and Downdetector before resetting passwords or reinstalling apps. A server-side outage is not fixed from your device.
- Use another channel for urgent messages, and confirm important emails with the recipient before you resend them.
- Expect Outlook to run slowly while recovery finishes.
- Be wary of emails that offer an “outage fix” through a link. Use Microsoft’s own status page for updates.
For IT Admins
- Open Service Health in the Microsoft 365 admin center and follow EX1550543 and MO1550821 until Microsoft marks them resolved.
- Record the start and end times, the affected services and the number of affected users for your tenant while the details are fresh.
- Download the post-incident report when Microsoft publishes it and compare its root cause with your own logs.
- Decide whether to file an SLA claim for each affected service (see the next section).
- Set up a way to reach staff that does not depend on Microsoft 365, such as a phone tree or a separate messaging tool.
Can You Claim a Service Credit?
Possibly. Microsoft’s Online Services SLA sets a 99.9 percent monthly uptime target for services such as Exchange Online, Teams chat and meetings, and SharePoint Online. A 30-day month has 43,200 minutes, so 99.9 percent allows about 43 minutes of downtime. Credits are not automatic: your admin files a claim, and a credit applies only to the service that missed its target, not to your whole plan.
| Monthly uptime for the service | Common service credit |
|---|---|
| Below 99.9% | 25% of the applicable monthly fees |
| Below 99% | 50% of the applicable monthly fees |
| Below 95% | 100% of the applicable monthly fees |
Microsoft Learn’s credit guidance for partners asks for the tenant ID and the outage ID from Service Health, and the ID starts with a service code, such as EX for Exchange Online. These tiers come from a study guide on the August 2026 SLA and Microsoft Learn. Read the current SLA text for your agreement, and check whether Copilot is named in it before you count it.
Earlier 2026 Microsoft Outages
| Date | Services | What was reported |
|---|---|---|
| January 21 to 22, 2026 | Outlook, Teams, Microsoft 365, Defender, Purview | Microsoft pointed to a possible third-party networking issue on January 21 (MO1220495). On January 22, it said part of the dependent infrastructure in the North America region was not processing traffic as expected (MO1221364). Sources: Tom’s Guide, TechRadar. |
| August 31, 2026 | Exchange Online, Purview | A multi-hour Exchange Online outage affected all connection methods, with user reports starting around 8:30 a.m. Pacific. Sources: Tom’s Guide, TechCrunch. |
| November 12 to 14, 2026 | Exchange Online, Teams, SharePoint Online, Copilot, Defender XDR | More than 24 hours of disruption, covered in this guide. |
Microsoft 365 Outage FAQ
Is the Microsoft 365 outage over?
Microsoft said early on Saturday, November 14, 2026, that it had restored service to the remaining impacted customers and regions. Check Service Health in the Microsoft 365 admin center for your own tenant.
What caused the Microsoft 365 outage?
Microsoft says a fault introduced during an earlier network capacity upgrade surfaced after a recent network change. A process that sets up secure connections became overwhelmed on affected servers. The full root cause is due in a post-incident report.
How long did the outage last?
More than 24 hours, according to CBS News and the Associated Press.
Was the outage a cyberattack?
Microsoft says no. It reports no evidence of malicious activity and says the incident was not related to cyber activity or AI agents.
Why did Copilot stop working during the outage?
Some users could not load Copilot Chat, and Copilot experiences could not reach work data such as email, calendar and files. Microsoft said features that interact with Exchange Online were affected.
Where can I check whether Outlook is down?
Admins can check Service Health in the Microsoft 365 admin center. Anyone can check the Microsoft 365 status page and user-report sites such as Downdetector. User-report sites show complaints, not confirmed incidents.
Can I get a refund for the outage?
Possibly. Credits are not automatic, and an admin must file a claim if the affected service fell below its monthly uptime target. See the service credit section above.
Quick Recap of the Outage
- The incident began on Thursday, November 12, 2026, and lasted more than 24 hours.
- Outlook and Exchange Online were hit first, and Teams, SharePoint Online, Defender XDR and Copilot followed.
- Microsoft points to a fault from an earlier network capacity upgrade that surfaced after a later network change.
- Microsoft reports no sign of a cyberattack and says AI agents were not involved.
- The post-incident report with the full root cause is still to come.
- Admins should log impact now and decide on SLA claims for each affected service.
How This Article Was Checked and Sources
Every fact here comes from the outlets listed below, as read on November 14, 2026. Where outlets disagreed, such as on the exact start minute or the number of user reports, this article says so or uses the figure from the named source. This page will be updated when Microsoft publishes its post-incident report.
- BleepingComputer: Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide
- SecurityWeek: Microsoft 365 Outage Disrupts Outlook, Exchange Online and Teams
- CBS News / AP: Microsoft battling major worldwide outage
- CNN live coverage: Microsoft global outage
- CNBC: Microsoft apologizes for massive outage
- ABC News Australia: Microsoft outage hits users worldwide
- ABC7 News: Microsoft reveals cause of massive service outage
- Quartz: Microsoft is still working to fix a 2-day global outage
- XDA Developers: Microsoft’s massive outage is mostly over
- Forbes: Microsoft outage, what happened and what to do next
- RansomNews: Microsoft 365 outage, was it a cyberattack?
- Microsoft Learn: How and when to request a credit from Microsoft
- Open Exam Prep: SLAs and service credits







