Tokyo Weekender collected some of those posts. Some were grim: one user called the Outlook outage "an absolute disaster," and another said they were "screwed without Outlook." Others treated it more lightly. People asked whether they could go back to sleep or go home, and one suggested that everyone "stop working and start drinking this afternoon."
These are anecdotes from social media, and they don't show that employers in Japan gave anyone the day off. The technical problems behind them were real, though, and they reached Japan's government.
How a Thursday problem became a Friday problem in Tokyo
The outage started on Thursday, November 12. Around noon Eastern time, Microsoft's support account said it was looking into "issues accessing Exchange Online mailboxes through multiple connection methods in the Americas," and tracked the problem under incident EX1550543 in the Microsoft 365 admin center. The company added: "While we're working to mitigate impact, we've confirmed the issue may affect Microsoft 365 service connectivity for users in any region."
Noon Eastern on Thursday is about 2 a.m. Friday in Tokyo. Tokyo Weekender says Downdetector reports peaked at nearly 140,000 around 3 a.m. Japan time, which lines up with ABC7's report that nearly 130,000 users on outage tracker Downdetector reported problems accessing Outlook just after 1 p.m. Eastern. The two outlets give different totals, and either way these are user-submitted reports, not a confirmed count of affected people. Tokyo Weekender adds that the disruption was still spreading across Asia-Pacific, including India and Australia, when Tokyo offices opened.
So Japanese offices didn't catch the start of the outage. They caught the part where the fixes were still failing.
The government got hit, too
Tokyo Weekender reports that Deputy Chief Cabinet Secretary Masanao Ozaki said the outage had affected the Japanese government's IT infrastructure and that officials were watching the situation closely. The Associated Press separately reported that the government had arranged alternative ways to communicate, including telephones.
Japan wasn't the only government affected. CBS News, running AP's reporting, said that from Asia to the U.S., the outage involving services like Outlook and Teams dragged on for hours and impacted many users, companies and some government operations. AP also reported problems for Singapore's government email and for the Philippines' Supreme Court.
There were concrete examples in Japan as well. The Tokyo Foundation, a think tank, posted a notice on November 13 saying it could not reliably receive or review messages sent by email or through its website's contact form. That's an easy point to overlook: if a website contact form delivers into an Exchange Online mailbox, it fails along with email.
Section summary: The outage was not limited to individual inboxes. It affected government communications and public-facing contact channels, and organizations fell back on phones and public notices.
What actually broke
Exchange Online was the source of the problem. Microsoft's broader incident notice, MO1550821, said that features of many Microsoft 365 services that interact with Exchange Online and email services are impacted, while elements of those services that do not depend on interaction with Exchange Online remain functional.
The affected list grew beyond Outlook. ABC7 listed Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365, Microsoft Defender XDR, Microsoft Planner, Microsoft To Do, Microsoft Intune and Microsoft Defender for Office 365 as potentially affected. An admin-focused write-up on Azureblog mentioned a security detail worth knowing: Safe Links "may be unable to verify URLs", which may affect people clicking links in Outlook and Teams. In other words, the outage could also interfere with Microsoft's protection against malicious links.
Here's how the causes developed, according to Microsoft's status updates as summarized by Tokyo Weekender:
- Servers dropped out. Several servers unexpectedly became unavailable, and the remaining ones had to carry more load.
- A core process got overwhelmed. A process that sets up secure connections on the affected servers became overloaded, and those servers stopped responding to requests.
- A configuration change coincided with the start. Microsoft found a recent network configuration change that began around the same time as the disruption and started rolling it back.
- Recovery kept failing. By Friday afternoon in Japan, Microsoft was still restoring servers and sending traffic through other routes, but some restored servers stopped responding again once traffic reached them.
That last step matches what U.S. outlets reported overnight. Deadline said Microsoft had reported "positive results" restarting infrastructure, and then quoted the company saying "these actions aren't resulting in sustained recovery." Microsoft also told users it was taking "a measured approach to identify and repair affected infrastructure."
Note that Microsoft said a configuration change coincided with the start of the outage. It did not say that change caused it, and a final root-cause report had not been published when this was written.
Was it a cyberattack?
According to Tokyo Weekender, Microsoft executive Charles Lamanna said on X that the outage was not the result of a cyberattack. Microsoft also said it didn't have any indication that the outage was caused by malicious activity and would treat the incident "with urgency and priority until full resolution."
The timing has raised questions. SecurityWeek noted that the disruption came two days after Microsoft released its November Patch Tuesday updates, which included CVE-2026-124194, an Outlook spoofing flaw Microsoft says attackers have exploited. However, Microsoft's service advisories have not linked the vulnerability to the Exchange Online outage. Treat that as a coincidence of dates, not as evidence that the two are connected. Still, if your organization hasn't installed the November updates, the exploited Outlook flaw is a separate reason to do it.
The reliability question
Tokyo Weekender calls this the second major Microsoft 365 disruption of 2026, but that count misses the August 31-September 3 outage (tracked as EX1464935/MO1465074), which also disrupted Outlook, Teams and other services worldwide for days, making this the third major disruption of the year. The first was on January 22 and also took down Outlook and Teams. The outlet says the outages are prompting corporate customers to question the reliability of a platform with more than 430 million users. Nothing published so far shows a technical link between the January and November incidents, so it would be wrong to call this a recurring fault. Two major email outages in one year will still come up when IT leaders review continuity plans.
Microsoft 365 is reliable most of the time, and a mailbox Microsoft runs is still usually more resilient than one many organizations could run themselves. The problem with putting so much on one platform is that when Exchange Online fails, email, meetings, Copilot features and parts of the security stack can all be affected together.
What Windows admins and users should take from this
The outage shows where to focus during an incident and what to set up afterward.
During the outage:
- Check service health before troubleshooting PCs. If Microsoft has an active incident such as EX1550543 or MO1550821, reinstalling Outlook, resetting profiles or power-cycling routers won't fix the problem, because it's on Microsoft's side. Microsoft also gave admins an alternative status page in case they couldn't reach the admin center. It directed administrators to these incident records for further information and provided an alternative status link for those unable to access the admin centre.
- Tell staff which backup channel to use. Japan's government switched to telephones. Choose your fallback in advance and make sure it doesn't depend on Exchange Online.
- Be careful with links. If Safe Links can't check URLs, users should be more cautious than usual about clicking links in email and Teams.
- Don't work around security controls. Sending sensitive files through personal email or unapproved apps can create a bigger problem than the outage.
After the outage:
- List what depends on Exchange. Web contact forms, automated alerts, approval workflows and connectors from third-party AI tools can all route through it. AP reported that OpenAI and Anthropic both had trouble connecting to Microsoft 365 tools, which suggests integrations like these were affected too, not those companies' main services.
- Prepare a public notice in advance. The Tokyo Foundation's short notice is a good example. If you can't receive email, tell customers how else to reach you.
- Read Microsoft's post-incident report when it comes out. It should say whether the configuration change was the cause or just happened at the same time.
The bottom line
The jokes from Japanese workers are funny, but they point to how much ordinary office work now depends on one cloud service. When Exchange Online stopped responding, Outlook, Teams, Copilot, SharePoint and some security tools were affected across several continents, along with government offices in Tokyo and elsewhere. As of Friday, Microsoft was still trying to get a lasting recovery, and it said there was no sign of malicious activity. Choosing your backup communication channel now is easier than doing it in the middle of the next outage.
Correction (November 13, 2026): An earlier version of this article described the November 12 outage as the second major Microsoft 365 disruption of 2026. It is the third: a second major outage ran August 31-September 3, 2026 (EX1464935/MO1465074).