Update, Friday 13 November 2026, 17:50 UTC: The Microsoft 365 outage was not a cyberattack. Microsoft says it was a technical issue introduced during a network capacity upgrade and that the underlying fault has been fixed. Outlook, Teams, SharePoint and Copilot were disrupted worldwide for a day from Thursday 12 November. Microsoft reports broad recovery, but it is still restoring service for the remaining customers and regions and has not closed the incident. It has promised a full post-incident report. The latest developments are set out below, followed by the original report and an extended timeline.
Microsoft 365 went down for users around the world on Thursday 12 November 2026, taking Outlook, Teams, SharePoint, Copilot and Defender XDR with it. Microsoft says the cause was a large number of its own servers becoming unexpectedly unavailable, not a surge in traffic, and nothing it has published points to a cyberattack. By 3:30 p.m. ET (20:30 UTC) it was restarting servers and restoring service.
Outage trackers also lit up for Amazon Web Services, Google and Gmail, which is why the day felt like half the internet had failed. Their own status pages did not agree. This is what is confirmed, what is not, and why an outage like this is still a security problem.
Cause: a problem during a network capacity upgrade, according to Microsoft. It says the outage was not a cyberattack and was not related to AI agents.
Duration: a day. Microsoft opened the incident at 16:20 UTC on Thursday 12 November and had not closed it at 17:50 UTC on Friday 13 November.
Services hit: Exchange Online and Outlook, Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR, plus Planner, To Do, Intune and Defender for Office 365.
Scale: nearly 140,000 Outlook problem reports on Downdetector at the peak, and reports from more than 70 countries.
Email: delayed messages are being delivered late. Microsoft extended its email timeout to 48 hours to protect them.
Still to come: Microsoft’s post-incident report with the full root cause.
What has changed since Thursday?
The outage ran through the night and the first fixes did not hold. Recovery began on Friday morning and spread region by region through the day. At 17:50 UTC on Friday 13 November, Microsoft reported broad recovery and said the underlying issue had been fixed, but it was still restoring service for the remaining customers and regions and had not declared incidents EX1550543 and MO1550821 over. This section was added on 13 November. The sections after it are the report as published on Thursday, except where an update is marked.
The health-check fix failed under load. Servers that Microsoft brought back on Thursday afternoon stopped responding again once traffic reached them.
Microsoft found a deeper fault. A process that sets up secure connections on the affected servers becomes overwhelmed and the servers stop handling requests, according to a status update relayed by ABC7 . Microsoft has not said why.
A network change is being rolled back. Microsoft said it was reverting a recent network change, Australia’s ABC reported , then that the changes meant to improve service were not taking effect.
A blocker overnight. In a detailed update at 05:00 UTC, Microsoft said some machines were stuck in a faulty state that stopped its changes from syncing, and that it was adding virtual machines to raise capacity, Android Authority reports .
A new patch is showing results. At 06:56 UTC Microsoft reported only “marginal success” after patching and restarting servers, CNN reported . Half an hour later it said a patch applied to part of its infrastructure was improving server stability, and that it was extending the patch to servers in the regions now in use.
The outage carried into the European working day. At 07:00 UTC on Friday, Downdetector had at least 43,000 Outlook problem reports from users in 72 countries, Al Jazeera reported .
Recovery is slow and uneven. At 09:24 UTC Microsoft reported early stabilisation and more capacity. An hour later it said recovery was moving in phases : several services were improving, but service health still varied and capacity had not returned to its normal level.
Delayed email is being protected. Microsoft has extended its email timeout to 48 hours to preserve delayed messages and says it is giving priority to clearing the backlog. Expect mail sent since Thursday to arrive late.
Regions came back one after another. At 11:11 UTC Microsoft said recovery work was complete on parts of its infrastructure and traffic was being gradually restored. By 12:09 UTC it reported progress in Europe, and at 13:32 UTC broader improvement in North America and early signs of recovery in Asia Pacific.
Email queues are close to normal. At 14:17 UTC Microsoft said email queues were much smaller and approaching normal levels , while warning that some users could still see intermittent access problems or delayed email. Delayed messages have started to arrive, BleepingComputer reported .
A first report on the cause. The Verge’s Tom Warren reported that his sources link the outage to configuration changes in Azure Virtual Network, Microsoft’s cloud networking service. Tony Burke, Australia’s affairs minister, said Microsoft believes it is dealing with an update that went wrong, the Associated Press reported, as cited by GeekWire . Microsoft has not confirmed either account.
Microsoft has expressed regret. Charles Lamanna, an executive vice president at Microsoft, told Forbes that the company regrets the impact on customers and that its teams are reviewing what happened and how to prevent a repeat.
Microsoft has named a cause. In a statement on Friday, Microsoft apologised and said the incident was introduced during an earlier network capacity upgrade and surfaced after a recent network change. It said the outage was “not related to cyber or AI / agents”, that the underlying issue has been fixed and that a full post-incident report will follow, TIME and TechRadar reported.
The question in the headline now has a direct answer from Microsoft. A company spokesperson told the ABC there was “no indication” of a cyberattack, and a later status update said the same of malicious activity. Australia’s affairs minister, Tony Burke, said after a briefing from Microsoft and the national cyber security coordinator that neither believed it was a cyber event. That fits the reading in this article on Thursday: lost capacity, not an attack. Microsoft has still not published a root cause. Its status page promises one in a post-incident report once the outage is contained.
Two of the risks described further down have already appeared. The bank ING warned customers scammers offering to fix the problem, the ABC reported. And readers whose login codes arrive by email told the broadcaster they were locked out of other business apps. That is the weakness of email-based two-factor authentication: it fails when the mailbox does.
The list of affected services has grown as well. Microsoft’s advisory now names Planner, To Do, Intune and Defender for Office 365 alongside the services listed on Thursday. Its own record also shows the trouble starting before the public noticed: incident EX1550543 was first posted for administrators at 16:20 UTC, 79 minutes before problem reports began to climb on Downdetector, according to a copy of Microsoft’s incident reports kept by the University of Pennsylvania .
What caused the Microsoft 365 outage?
A problem during a network upgrade, according to Microsoft. On Friday 13 November the company said a fault introduced during an earlier upgrade to its network capacity came to the surface after a more recent network change. It called the outage a technical issue with no link to cyber activity or to AI agents, said the underlying fault had been fixed and apologised to customers, CNN reported .
Microsoft’s status updates describe how that became a day-long outage. Servers behind Exchange Online began failing automated health checks and dropping out of service, which pushed their work onto the servers that were left. A core process on those servers was then overwhelmed, and servers that had been restarted failed again as soon as traffic reached them. Stability returned only after Microsoft paused deployments, rolled back a network change and patched a component that handles authentication and routing. It then brought service back in stages, which it says took longer but made the recovery stable.
The statement fits what had already been reported. The Verge’s Tom Warren said his sources linked the outage to configuration changes in Azure Virtual Network, and Australia’s affairs minister said Microsoft believed an update had gone wrong. What is still missing is the detail: which change it was, why safeguards did not contain it and why recovery took a day. Microsoft says a full post-incident report will follow. This section was added on 13 November.
Is Microsoft down right now?
Mostly not. At 17:50 UTC on Friday 13 November, Microsoft reported broad recovery and said the underlying issue was fixed, but it was still restoring service for the remaining customers and regions and had not closed the incident. Some users may still see delayed email. The fix described in the rest of this paragraph was Thursday’s first attempt and did not hold overnight. On Thursday, its 4 p.m. ET status update said a different way of checking server health had returned some of the failed servers to service and was being applied more widely, and that automated restarts were being prepared for servers that stop responding. Administrators can follow it in the Microsoft 365 admin center under EX1550543 and MO1550821.
Was the Microsoft outage a cyberattack?
No. On Friday 13 November Microsoft said the outage was a technical issue, not related to cyber activity or to AI agents, and traced it to a problem during a network capacity upgrade. The rest of this section is the analysis published on Thursday, before Microsoft gave a cause.
Nothing Microsoft has said points to one. Its first diagnosis was that part of its infrastructure was under elevated load in several regions. It then narrowed that down: the load did not come from more traffic, it came from “a number of servers being unexpectedly unavailable”, as ABC News reported , which pushed the work onto the machines that were left.
How does your own site score?
Run the same forty passive checks against your own domain: TLS and certificates, security headers, SPF and DMARC, cookies before consent, and what your stack quietly reveals. A grade out of 100 in fifteen seconds.
No signup. Nothing installed. We only request what your site already serves publicly.
That detail matters. A denial-of-service attack shows up as a flood of traffic, and Microsoft is describing the opposite, lost capacity under normal demand. What Microsoft has not yet explained is why the servers dropped out. Until it publishes a post-incident review, the honest answer is that there is no evidence of an attack and no full root cause either.
What went down, and when?
Microsoft’s advisory lists Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR, according to BleepingComputer . The timeline shows when users noticed the problem and what Microsoft said at each step.
Thursday 12 November: the outage begins
Morning Microsoft A separate Teams incident hits users in North and South America. Microsoft says it is resolved and has not said whether the two are linked.
11:20 a.m. ET 16:20 UTC Microsoft Microsoft opens incident EX1550543 for administrators, saying it is investigating a possible problem with mailbox access, its incident record shows .
12:39 p.m. ET 17:39 UTC User reports Outlook problem reports start to climb on Downdetector, Variety reports .
12:54 p.m. ET 17:54 UTC Microsoft In its first public post, Microsoft says it is investigating failed access to Exchange Online mailboxes in the Americas. It later says users in any region may be affected.
1:09 p.m. ET 18:09 UTC User reports Downdetector has logged more than 129,000 Outlook reports. CP24 counted nearly 140,000 by 1:30 p.m.
1:35 p.m. ET 18:35 UTC Microsoft Microsoft blames elevated load on part of its infrastructure in several regions. 15 minutes later it starts spreading connections across the rest of its network.
2:12 p.m. ET 19:12 UTC Microsoft Microsoft pauses all deployments, moves more traffic off the affected systems and starts restarting servers.
2:31 p.m. ET 19:31 UTC Microsoft Microsoft rules out a traffic surge . The load comes from servers that became unexpectedly unavailable, which strains the ones still running. Why it matters: a denial-of-service attack looks like a flood of traffic. This is the opposite.
2:50 p.m. ET 19:50 UTC Microsoft The servers are failing automated health checks, Microsoft says. It tests a configuration change and restarts all of them.
3:15 p.m. ET 20:15 UTC User reports More than 63,000 Outlook reports remain on Downdetector.
3:19 p.m. ET 20:19 UTC Microsoft No recent change lines up with the start of the outage, Microsoft says. It suspects the component that processes server health.
4:00 p.m. ET 21:00 UTC Microsoft A different way of checking server health brings some servers back. Microsoft starts applying it more widely.
Thursday evening: the fixes do not hold
5:09 p.m. ET 22:09 UTC Microsoft The steps taken so far have not brought the relief it expected, Microsoft says . It finds that a core process on the affected servers is being overwhelmed.
5:41 p.m. ET 22:41 UTC User reports Just over 37,000 Outlook reports remain on Downdetector, according to Tom’s Guide.
6:04 p.m. ET 23:04 UTC Microsoft Some servers are back in service and holding steady, with limited recovery in places.
6:56 p.m. ET 23:56 UTC Microsoft A Microsoft spokesperson tells Australia’s ABC there is no indication of a cyberattack. A later status update says the same malicious activity. Why it matters: this is Microsoft’s first direct answer to the question in the headline.
7:06 p.m. ET 00:06 UTC Fri Microsoft The restored servers stop responding again once traffic reaches them. Microsoft limits which kinds of traffic can reach them in some locations.
8:59 p.m. ET 01:59 UTC Fri Microsoft Restarting parts of the infrastructure in isolation is showing positive results, Microsoft says.
10:13 p.m. ET 03:13 UTC Fri Microsoft The latest changes are not working as planned , Microsoft says. It looks for other ways to add capacity.
11:00 p.m. ET 04:00 UTC Fri User reports 20,000 Outlook reports remain on Downdetector, Newsweek reports .
11:36 p.m. ET 04:36 UTC Fri Microsoft Changes to how traffic is handled bring partial recovery in some regions, but it does not last.
12:01 a.m. ET 05:01 UTC Fri Microsoft Microsoft says it is working on several fronts and on a blocker: some machines are stuck in a faulty state and will not take its changes.
12:46 a.m. ET 05:46 UTC Fri Microsoft Microsoft’s public status page says the company is not aware of any malicious activity behind the outage, and promises a post-incident report with the root cause once it is contained.
1:56 a.m. ET 06:56 UTC Fri Microsoft After patching and restarting servers, Microsoft reports only “marginal success”, CNN reports . It adds virtual machines to raise capacity.
2:00 a.m. ET 07:00 UTC Fri User reports As Europe starts work, Downdetector has at least 43,000 Outlook reports from users in 72 countries, Al Jazeera reports .
2:25 a.m. ET 07:25 UTC Fri Microsoft A patch applied to part of the infrastructure is improving server stability, Microsoft says. It starts extending the patch to servers in the regions now in use.
Friday 13 November: services start to return
4:24 a.m. ET 09:24 UTC Fri Microsoft Microsoft reports early stabilisation and more capacity. It extends its email timeout to 48 hours to protect delayed mail.
5:28 a.m. ET 10:28 UTC Fri Microsoft Recovery is moving in phases, Microsoft says . It reports “incremental improvement” in several services, but says service health still varies and capacity is not back to its normal level.
6:11 a.m. ET 11:11 UTC Fri Microsoft Recovery work is complete on parts of the infrastructure and traffic is being gradually restored , Microsoft says. Mailbox access and delayed email are improving.
7:09 a.m. ET 12:09 UTC Fri Microsoft Service availability and email delivery are improving on a growing of the infrastructure, Microsoft says , with Europe ahead and North America following.
8:32 a.m. ET 13:32 UTC Fri Microsoft Microsoft reports broader improvement in North America, sustained improvement across much of Europe and early signs of recovery in Asia Pacific.
9:17 a.m. ET 14:17 UTC Fri Microsoft Email queues are much smaller and “approaching normal levels”, Microsoft says . It warns that some users may still have intermittent access problems or delayed email while it restores the remaining infrastructure.
Before noon ET by 16:58 UTC Fri Microsoft Microsoft apologises and names a cause : a problem during an earlier network capacity upgrade that came to the surface after a recent network change. It says the underlying issue is fixed, that the outage was “not related to cyber or AI / agents”, and that it is still restoring service for the remaining customers and regions. Why it matters: this is the first cause Microsoft has given, and it rules out an attack.
Status Now Microsoft reports broad recovery and says the underlying issue is fixed. It has not closed the incident and is still restoring the last customers and regions. Checked at 17:50 UTC on 13 November.
Why does Downdetector show AWS, Google and Gmail too?
Because Downdetector counts what users report, not what providers measure. When email and meetings stop working, people report whatever they were using at the time, and the charts for unrelated services rise together.
The providers’ own dashboards told a different story. PCWorld checked during the outage and found no issues on Cloudflare Radar or Google’s cloud status page, and only a local problem in Tokyo on the AWS Health Dashboard. The scale was different too: CP24 saw 1,350 reports for AWS and 1,000 for Gmail, against well over 100,000 for Outlook.
Why is an outage a security problem?
For three reasons, none of which need an attacker to have caused it.
Defender XDR was on the list. For a few hours, security teams could not rely on the console many of them use to see alerts and run investigations. Anything that happened in that window deserves a second look once the portal is stable.
Outages make good phishing lures. Expect emails and texts offering to “restore your mailbox” or “re-verify your Microsoft 365 account”. Cheap, fluent lures are easier to write than ever, as we covered in how large language models are reshaping phishing .
Workarounds outlive the outage. Staff move work to personal email and chat apps, and administrators relax sign-in rules to get people back in. Both leave gaps that stay open after service returns.
What should admins and users do?
Follow the official record. Use the Microsoft 365 admin center entries EX1550543 and MO1550821, not social media screenshots.
Do not loosen MFA or conditional access to work around sign-in errors. If you changed a policy today, change it back.
Review the gap. Once Defender XDR is healthy, check alerts and sign-in logs for the hours it was unavailable.
Warn staff recovery scams. Microsoft will not email a link to restore a mailbox. A stolen session is enough to get past MFA, which is why session-cookie theft is the attack to watch after an event like this.
Pull work back from personal accounts and unofficial channels, and delete what was copied there.
Can customers claim compensation for the Microsoft 365 outage?
Business customers may be able to claim a service credit, but it is not automatic. Microsoft’s service level agreement promises 99.9% uptime in each calendar month, and its published credit table gives 25% of the monthly fee for the affected service below 99.9% uptime, 50% below 99% and 100% below 95%.
November has 43,200 minutes, so the 99% line is crossed after 7 hours and 12 minutes of downtime and the 95% line after 36 hours. A tenant whose users could not reach their mailboxes for 20 hours would be at 97.2% for the month, which falls in the 50% band. Microsoft measures downtime by the users affected, so the figure will differ from one organisation to the .
An administrator has to file the claim, and Microsoft decides each one. If licences were bought through a reseller, the claim usually goes through that partner. Under the agreement, a claim must reach Microsoft by the end of the month after the incident, which for this outage is 31 December 2026. Keep the incident numbers, EX1550543 and MO1550821, and a record of when your users were affected.
Frequently asked questions
Mostly not. At 17:50 UTC on 13 November 2026, a day after the outage began, Microsoft reported broad recovery and said the underlying issue was fixed. It was still restoring service for the remaining customers and regions and had not closed the incident. Email delayed by the outage is being delivered late.
No. Microsoft said on 13 November 2026 that the outage was a technical issue, not related to cyber activity or to AI agents. It traced the fault to a problem during a network capacity upgrade and said the underlying issue has been fixed.
A problem during a network capacity upgrade, according to Microsoft. The company says the fault came to the surface after a recent network change. Servers behind Exchange Online then failed health checks and dropped out of service, which overloaded the servers that were left. A full post-incident report is still to come.
a day. Microsoft opened incident EX1550543 at 16:20 UTC on Thursday 12 November 2026, and users began reporting problems at 17:40 UTC. Recovery started on Friday morning, and at 17:50 UTC on Friday 13 November Microsoft was still restoring the last customers and regions.
Business customers may be able to claim a service credit. Microsoft’s service level agreement promises 99.9% monthly uptime, with credits of 25%, 50% or 100% of the monthly fee for the affected service when uptime falls below 99.9%, 99% or 95%. An administrator has to file the claim, and Microsoft decides it.
Microsoft’s advisory lists Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR. Users also reported problems with Outlook, OneDrive, Azure and the Microsoft Store on Downdetector.
Their status pages did not show it. Downdetector recorded 1,350 reports for AWS and 1,000 for Gmail, but Google’s cloud status page reported no issues and the AWS Health Dashboard showed only a local problem in Tokyo.
Microsoft has not given a number. Downdetector logged more than 129,000 Outlook problem reports by 1:09 p.m. ET and nearly 140,000 by 1:30 p.m., and those are user reports, not a count of affected accounts. For scale, Microsoft said in January that it had more than 450 million paid Microsoft 365 commercial subscriptions, the Associated Press reported.
Administrators can check the Microsoft 365 admin center under incident EX1550543 and advisory MO1550821. Everyone else can use Microsoft’s service health status page. Do not follow links in emails that offer to restore your account.
Sources and further reading
BleepingComputer: Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide (12 November 2026)
ABC News: Outlook outage, Microsoft reports issues with Teams and email (12 November 2026)
Variety: Outlook outage, Microsoft’s email service goes down nationwide (12 November 2026)
XDA: Microsoft is suffering a major outage (12 November 2026)
PCWorld: Outlook’s outage may be cascading across the internet, users report (12 November 2026)
CP24: Widespread issues reported with Microsoft products, Downdetector (12 November 2026)
Microsoft 365 Status on X: updates on incident EX1550543 (12 November 2026)
Tom’s Guide: live updates on the Microsoft 365 outage (12 November 2026)
ABC News (Australia): live blog on the Microsoft outage (13 November 2026)
ABC7: Microsoft outage live updates (13 November 2026)
Android Authority: Outlook, Teams and other Microsoft 365 services are still down (13 November 2026)
Newsweek: Is Microsoft Outlook still down? (13 November 2026)
University of Pennsylvania: Microsoft’s incident reports for PennO365, including EX1550543 and MO1550821
CNN: Microsoft outage live updates (13 November 2026)
UC Today: Microsoft 365 outage, Outlook down and the fix won’t hold (13 November 2026)
Al Jazeera: Microsoft hit by global outages, what happened and why? (13 November 2026)
Tom Warren (The Verge) on X: sources link the outage to Azure VNet configuration changes (13 November 2026)
GeekWire: Microsoft 365 starts to recover after a day of global email turmoil (13 November 2026)
Forbes: Microsoft outage, what happened and what to do (13 November 2026)
TIME: Microsoft struggles to repair worldwide outage, what you need to know (13 November 2026)
TechRadar: Microsoft outage live updates (13 November 2026)
Microsoft Learn: service level agreements and service credits for Microsoft 365
Related reading on Ransomnews: the ransomware incident response runbook .
The Ransomnews Monthly
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
