Microsoft declares the 36-hour Microsoft 365 outage resolved and names a network-upgrade fault
Microsoft has declared the global Microsoft 365 outage resolved, saying services have fully recovered and the email backlog has been processed — about 36 hours after the first errors, with a network-capacity upgrade blamed for the fault.
The News
Microsoft has declared the global Microsoft 365 outage resolved. Its final service-health update, at 04:17 UTC on Saturday November 14 — 11:17 p.m. ET on Friday — says services across the previously affected environments have fully recovered and the backlog of email messages has been processed, with the status reading "serviceRestored" and the end time given as 4:10 p.m. UTC on Friday November 13. The consumer incident, covering Outlook.com and Hotmail, was declared remediated at 03:51 UTC on November 14, and the Microsoft 365 business incident was cleared from the public status page at 05:42 UTC.
Microsoft's preliminary cause is a fault introduced during an earlier upgrade to network capacity, which surfaced after a more recent network change. The company described it as "a technical issue not related to cyber or AI / agents" — a direct answer to the first question everyone asks when a cloud service goes dark. The outage began at 16:17 UTC on Thursday November 12, so roughly 36 hours elapsed from the first errors to the all-clear, spanning parts of two working days for many users.
Microsoft says it will publish a preliminary post-incident report within two working days and a final report within five. The Microsoft 365 suite — email, documents and collaboration tools — is the daily working environment for hundreds of millions of people, and the outage was global in scope. Microsoft shares closed Friday at $523.88, up 0.17% on the day, a muted market reaction to an incident that was still unresolved when the market closed.
Thirty-six hours without email is not a glitch — it is a reminder of how much of the working world runs on one company's cloud.
Why It Matters
Microsoft 365 is not just an app — it is the daily working environment for hundreds of millions of people, covering email, documents and collaboration. When it goes down globally, the outage is not a technology story but a work story: meetings, deadlines and decisions all stall. A 36-hour outage spanning two working days is long enough to matter, even if the services are now back.
The cause matters as much as the duration. A fault introduced during an earlier upgrade to network capacity, surfacing only after a more recent network change, is the kind of failure that points at process, not at an attacker. Microsoft was explicit that this was not related to cyber or AI, and that distinction matters: a cyberattack would raise questions about the security of the cloud itself, while an internal upgrade fault raises questions about testing and change management. Both are serious, but they are different kinds of serious.
The muted market reaction — Microsoft shares up 0.17% on Friday, closing at $523.88 — tells its own story. Investors treated this as an operational incident, not a reason to reprice the company. That is probably right in the short term, but the incident will be judged again when the post-incident reports arrive. If the reports show a testing gap or a change that went out without proper checks, the questions will get sharper. For now, the outage is closed, the backlog is cleared, and the clock is running on Microsoft's explanation.
Analyst's Take
Our call is Mixed. The resolution is the good news: services are fully recovered, the email backlog is processed, and the preliminary cause is an internal network fault, not a cyberattack or an AI failure — the two explanations that would have carried far worse consequences for Microsoft and for cloud trust generally. The bad news is the duration. Thirty-six hours is a long time for the world's most-used productivity suite to be degraded, and it spanned two working days. The market's reaction was muted — Microsoft shares closed up 0.17% on Friday — which suggests investors treated this as an operational stumble rather than a structural problem.
What to watch is the post-incident report. Microsoft has promised a preliminary report within two working days and a final one within five, and the interesting part will be what changed in the network and why a fault introduced during an earlier upgrade only surfaced after a later change. That is the kind of failure chain that tells you something about how carefully upgrades are tested before they reach production. For now, the outage is a reminder of concentration risk: when one company's cloud carries so much of the working world's email and documents, a single fault becomes a global event.
Reader poll: did the outage hit your work? Vote: Yes, hit hard, Briefly affected, or Not affected.
Are you bullish or bearish on this story?
By The Numbers
FAQ
How long was the outage?
About 36 hours from the first errors at 16:17 UTC on Thursday November 12 — the start time Microsoft gives for the Exchange incident EX1550543 — to the all-clear. Microsoft's own end time is 4:10 p.m. UTC on Friday November 13, and its final service-health update came at 04:17 UTC on Saturday November 14.
What caused it?
Microsoft's preliminary cause is a fault introduced during an earlier upgrade to network capacity, which surfaced after a more recent network change. Microsoft described it as a technical issue not related to cyber or AI.
What services were affected?
The Microsoft 365 business incident covered the productivity suite — email, documents and collaboration tools — and a separate consumer incident hit Outlook.com and Hotmail. The consumer incident was declared remediated at 03:51 UTC on November 14, and the business incident was cleared from the public status page at 05:42 UTC.
When will we know more?
Microsoft says it will publish a preliminary post-incident report within two working days and a final report within five. Those reports should give the fuller technical account and any changes Microsoft plans to make.
👁
Source: EpiFive