FSO NEWS: Microsoft 365 Outage Stretches Into a Second Day, and It Shows the Cost of a Single Provider

Key takeaways

A global Microsoft 365 outage began Thursday, November 12, 2026, around 1 p.m. Eastern, affecting Outlook, Teams, Copilot, OneDrive and other services that depend on email. As of about 8 a.m. ET Friday, Microsoft's public status page still listed a service degradation, while the company reported encouraging recovery in Europe and improvement in North America.
Microsoft has not said how many people were cut off. More than 430 million people use Microsoft 365 apps, according to Microsoft. Downdetector recorded about 140,000 Outlook reports from 74 countries on Thursday evening, the BBC reported, a figure the BBC said is likely a large undercount.
Microsoft blamed servers that became "unexpectedly unavailable," which overloaded the systems still running, and said there was no evidence of malicious activity.
The disruption delayed company results, including Richemont's half-year numbers and Workhorse Group's third-quarter report, and knocked out email for schools, health services and other public bodies.
Microsoft shares were about 2% lower in premarket trading on Friday, according to CNBC and a Dow Jones report. Those figures can change once regular trading is finished. This article is not investment advice.

Times are Eastern (ET) unless noted. This article was refreshed about 8 a.m. ET Friday, November 13, 2026, while Microsoft was still reporting recovery in progress and its public status page still listed a service degradation.

For a second day, a lot of the working world has been staring at Outlook and waiting.

A Microsoft 365 outage that started on Thursday afternoon, November 12, 2026, was still not over as of about 8 a.m. Eastern on Friday. Email was the most visible failure. Teams, Copilot, OneDrive and other tools that sit on the same platform were also hit. Microsoft said recovery was improving in some regions, but it had not declared the incident over. Its public service health page, checked around that time, still listed a service degradation on Microsoft 365 for business, enterprise and consumer products, and said users may be unable to connect to multiple Microsoft 365 services. It also warned that some users could still see intermittent problems.

The company has not published a headcount of affected customers. It does not have to for the scale to be obvious. Microsoft 365 is how countless companies, governments and schools send mail, book meetings and store files. When that layer fails, the damage shows up in delayed house purchases, late results announcements, and public services asking people to call instead of emailing.

What went down, and when

Reports began rolling in shortly before 1 p.m. ET on Thursday, CNBC and The Verge reported. Microsoft later confirmed that Microsoft 365 features which interact with Exchange Online and email were affected, including Outlook (on the web and on the desktop), SharePoint Online, Teams, Copilot and other business services.

The outage was uneven. Microsoft and several newsrooms said core Teams messaging and meetings were working for some people even while mailbox access and email delivery were not. Calendar details and files were among the things users could not always see. BBC News, which followed the incident through Friday, listed Teams, Outlook, Copilot and OneDrive among the affected services.

Administrators were pointed to incident MO1550821 in the Microsoft 365 admin center, and to Microsoft's public status page at status.cloud.microsoft if that center was itself hard to reach. Official updates also appeared on the @MSFT365Status account, which Windows Central and The Verge quoted throughout the night and into Friday.

How big was it?

Microsoft has not said how many tenants or mailboxes were actually offline. Two other numbers are being used to describe the blast radius, and they measure different things.

The first is the size of the product. The BBC reported that more than 430 million people use Microsoft 365 apps, according to Microsoft's website. That figure also appears in a Microsoft 365 blog post, which cites the company's fiscal 2025 third-quarter earnings call in April 2025 and says "over 430 million people" use Microsoft 365 apps. It is a user-base number, not a count of people who lost service on Thursday.

The second is what people reported. A BBC article on the outage said reports of issues with Outlook peaked globally at nearly 140,000 around 18:00 GMT (1 p.m. ET) on Thursday, according to the monitoring site Downdetector. In a later explainer, the BBC said Downdetector had 140,000 people from 74 countries report Outlook problems on Thursday evening, and that the real number affected is likely much higher because the site depends on people choosing to report. The BBC's live page put it in similar terms: tens of thousands of reports across more than 70 countries, and "likely to be a vast underestimate."

Other outlets captured different snapshots at different times. A Reuters dispatch earlier on Thursday, republished by Investing.com, counted more than 97,000 Outlook reports at 2:07 p.m. ET, plus more than 38,000 for Microsoft 365 and about 4,500 for Teams. The Guardian later cited nearly 130,000 reports in 74 countries at about 6 p.m. GMT. Those figures are not contradictions so much as different looks at a moving tracker. The BBC's peak and country counts are the ones used in this piece.

What Microsoft says caused it

Microsoft has ruled out a cyber attack. Charles Lamanna, executive vice president of Copilot, Agents and Platform, said there was "no indication this is the result of malicious or cyber activity," Windows Central reported. The BBC, CNBC, The Verge and The Guardian all carried the same basic assurance from the company: no evidence of malicious activity.

The explanation Microsoft has given is an infrastructure failure, not a flood of incoming mail. In its early updates it said a portion of its infrastructure was experiencing "elevated load across multiple regions." It later said that load was caused by a number of servers "being unexpectedly unavailable," which strained the remaining systems. CNBC reported that some servers were failing automated health checks. The BBC summarized the same sequence: servers dropped out, traffic landed on what was left, and those remaining servers were overwhelmed.

Fixes did not take hold quickly. Microsoft at one point said changes were "not taking as expected," the BBC and CNBC reported, and it warned that servers brought back into service could become unresponsive again once traffic returned. Engineers took systems offline, brought them back in stages, and, according to status updates quoted by The Verge and Windows Central, extended the email timeout to 48 hours so delayed messages would keep trying to send while queues were cleared.

By Friday morning, the tone of the updates had improved, without a claim of a full restore. Around 6 a.m. ET, Microsoft said recovery actions had been completed across portions of the affected infrastructure in the Asia Pacific region, with traffic being gradually restored and improvements in mailbox access and delayed email processing, the BBC and NBC News reported. Shortly after 7 a.m. ET, CNBC, the BBC and NBC News reported, Microsoft said it was seeing "encouraging recovery progress in Europe," with service availability and email delivery improving across a growing portion of the affected infrastructure; that North America was "improving"; and that Japan remained "comparatively more stable," though some users might still see intermittent issues. Microsoft said it was focused on the remaining areas of disruption and on reducing email queues and backlogs. Windows Central, quoting a Microsoft 365 Status update around 7:33 a.m. ET, said the extended 48-hour email timeout window remained in place. The Verge noted there was still no time given for a full restoration. As of about 8 a.m. ET, the official status page still showed the degradation.

A full post-incident report has not been published. The Guardian quoted Microsoft as saying that once the problem is mitigated, the company will provide "full details of the root cause, defence-in-depth repair items, and more within a post-incident report." NBC News, at 7:48 a.m. ET Friday, reported that Microsoft said on its public service health page that it will share that report, including the root cause, after recovery is complete.

The business and public-service impact

Because so much of daily work still passes through email, the outage showed up in places that have nothing to do with software journalism.

Two companies delayed financial results. The Swiss luxury group Richemont, owner of brands including Cartier and Chloé, said its half-year numbers would be delayed because of the Microsoft disruption, the BBC reported; CNBC later described those earnings as slightly delayed on Friday. U.S. electric-truck maker Workhorse Group, which had been due to report third-quarter results on November 12, moved the release to November 16, citing the outage, according to the BBC and CNBC.

In the United Kingdom, the BBC reported disruption at GP surgeries, pharmacies, schools, police forces and parts of the NHS, with some organizations telling the public to telephone rather than email. NHS England said the global issue was "inevitably" disruptive for staff and that local services were using long-standing measures, including other IT systems or paper records, so that critical care and appointments could continue. Patients were told to attend appointments unless they heard otherwise, and to keep using 999 in an emergency. Some court hearings in Scotland were delayed, and a first-time house purchase in Staffordshire was pushed back because a solicitor could not reach other parties, the BBC's live coverage said. Friday is a common completion day for UK property sales.

The disruption was not only a UK story. The BBC said CBC reported that a Toronto-area hospital network had email problems but that patient care was not affected, and that Japan's government said a shared IT platform had been disrupted. OpenAI and Anthropic, which connect some tools to Microsoft's systems, both reported issues with those connections, according to the BBC, Reuters and The Guardian. Air India said it had temporarily rerouted emails so it could keep receiving customer messages, and that flight operations were not affected, CNBC reported.

What it means for Microsoft (MSFT)

For Microsoft, the immediate market question is whether investors treat this as a short operational mess or as another reminder that the company's most important software franchise can still fail in public, for many hours, on a weekday.

CNBC, in an article updated Friday morning, reported that Microsoft shares were around 2% lower in premarket trade. A Dow Jones report carried by MarketWatch and Morningstar also said the stock dropped 2% in Friday premarket trading, putting it on track for its lowest close since November 2 and its worst week since the week ending July 24. As of this refresh, about 8 a.m. ET Friday, the regular U.S. session had not yet opened, and neither CNBC, Reuters nor Dow Jones had published a newer figure that superseded those readings. They are premarket numbers, not a regular-session close, and they can move as the day goes on. This article does not use later, conflicting percentages from other outlets.

The outage also landed on a product Microsoft has been pushing hard. Copilot, its AI assistant, was among the tools affected. The same Microsoft blog post that cites the 430 million Microsoft 365 users also says more than 90% of Fortune 500 companies trust Microsoft 365 Copilot, a figure The Guardian repeated. An outage that includes Copilot is awkward for a company that has made that assistant central to its pitch, but it does not, by itself, tell you how the stock will trade next week.

This is news and analysis, not a recommendation to buy or sell Microsoft or any other security. Past outages, including a Microsoft Azure disruption last month that news reports said affected productivity tools, are useful context. They are not a prediction.

The single-provider problem

The more durable point may be the one several people made while they were still waiting for mail to move. If your business, school or clinic uses one company for email, files, chat and calendars, a failure at that company is not an inconvenience. It is a stoppage.

The BBC quoted cyber-security adviser Jake Moore describing the scale as "absolutely massive" because Microsoft "sits at the heart of many businesses," and saying organizations should have backups in place, such as another messaging platform, for when things go wrong. Software engineer Gergely Orosz told the BBC he "cannot recall" a business-email outage taking this long to return to normal, and that the incident could be the "most disruptive" business email outage "of all time." That is an expert's judgment, not a measured ranking, but the length of the failure is what prompted it. Microsoft said earlier attempted fixes were not taking as expected, and more than 16 hours after the start it was still talking about incremental improvement and capacity that had not fully returned to normal, the BBC reported.

None of that requires a company to abandon Microsoft 365. It does argue for a second path that does not live on the same infrastructure: a backup mailbox at an independent provider, a current export of contacts, and a plan to reach customers by phone or another channel when Outlook is dark. Changing mail-routing records in a panic, mid-outage, is usually a poor substitute for having that path ready in advance.

Microsoft will eventually publish a technical review, and the queues it is clearing should drain. The lesson for everyone who could not send a message on a Thursday afternoon is simpler than the engineering: if one vendor holds all of your communications, you will wait when that vendor does.

Sources

This article is news and information only, not investment advice. It was refreshed about 8 a.m. ET Friday, November 13, 2026, while Microsoft was still reporting recovery in progress and its public status page still listed a service degradation.

This article is for general information only and is not financial, tax, legal or insurance advice. Check the official sources linked in the article and speak with a qualified professional about your own situation.

Microsoft 365 Outage Stretches Into a Second Day, and It Shows the Cost of a Single Provider