---
title: "Microsoft 365 Down: Outlook, Teams and Copilot Outage (Nov 12–13, 2026)"
description: "Microsoft 365 outage Nov 12–13, 2026: Outlook, Teams, SharePoint and Copilot down. Incident MO1550821, the July gateway bug, and times in JST."
canonical: https://itsupportintokyo.com/en/blog/microsoft-365-outage-nov-12-2026-outlook-teams-down
language: en-US
published: 2026-11-18T01:40:00.000Z
modified: 2026-11-18T01:40:00.000Z
author: "IT Support in Tokyo Team"
keywords: "Microsoft 365 down, Outlook down, Teams down, Microsoft outage, Microsoft 365 outage November 2026, Copilot down, Exchange Online outage, SharePoint down, is Microsoft down, MO1550821"
image: https://itsupportintokyo.com/article-assets/microsoft-365-outage-2026-11-12/photo-office.webp
translations: ["https://itsupportintokyo.com/ja/blog/microsoft-365-outage-nov-12-2026-outlook-teams-down"]
---

# Microsoft 365 Down: Outlook, Teams and Copilot Outage (Nov 12–13, 2026)

> Microsoft 365 outage Nov 12–13, 2026: Outlook, Teams, SharePoint and Copilot down. Incident MO1550821, the July gateway bug, and times in JST.

**Microsoft 365 went down for roughly a day on Thursday, Nov 12, 2026 (US time), taking Outlook email, Teams, SharePoint, Copilot and Defender XDR with it. In Japan the outage ran through the working day on Friday, Nov 13.** Microsoft tracked it as incident MO1550821, said it was not an attack, and later blamed a software bug that had been sitting in its network gateway servers since July. This report separates what Microsoft said from what users reported, with every time converted to Japan Standard Time.

**Key facts**
- **When:** Nov 12, 2026 from about 11:20 a.m.–1:26 p.m. ET (01:20–03:26 JST, Nov 13; see below on the two start times) until customer impact ended at 11:10 a.m. ET on Nov 13 (01:10 JST, Nov 14).
- **What:** Exchange Online (Outlook email), Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR, per Microsoft's advisory MO1550821.
- **Cause:** a previously undetected software bug introduced in a July update to Microsoft 365 networking gateway servers, per Microsoft's preliminary post-incident report. Not a cyberattack, per Microsoft.
- **Status now:** resolved. Microsoft said it was still clearing a backlog of delayed email on the following weekend.

![A Japanese office worker leans back from her laptop in frustration in a Tokyo office at dawn, the screen showing a blank grey warning dialog, while two colleagues check their phones and Tokyo Tower glows in the window](/article-assets/microsoft-365-outage-2026-11-12/photo-office.webp)

Friday morning in Tokyo, Thursday afternoon in New York: the outage straddled both. AI-generated image (ChatGPT), not a photo of the event.

## What went down

Microsoft's own advisory in the Microsoft 365 admin center, MO1550821, said customers "may be unable to connect" to Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR, according to [BleepingComputer](https://www.bleepingcomputer.com/news/microsoft/massive-microsoft-365-outage-disrupts-outlook-teams-copilot-worldwide/), which reported the incident as it developed. Because Outlook reads mail from Exchange Online, Outlook users saw the failure as "Outlook down". Complaints on the outage tracker Downdetector also mentioned OneDrive, Azure and the Microsoft Store, but those names did not appear in Microsoft's advisory, so we list them separately.

![Nine product tiles: Exchange Online, Outlook, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR marked in red as named in Microsoft's advisory, and OneDrive, Azure and Microsoft Store in blue as user reports only](/article-assets/microsoft-365-outage-2026-11-12/services-en.webp)

Red: named in Microsoft's advisory MO1550821. Blue: user complaints on Downdetector, as reported by BleepingComputer, not confirmed by Microsoft. Product names only; we do not reproduce Microsoft's logos.

## Timeline, in Japan time

US Eastern Time is 14 hours behind Japan in November, so a Thursday afternoon outage in New York is a Friday outage in Tokyo. Two start times appear in the coverage: BleepingComputer's live report gave 1:26 p.m. ET (03:26 JST), while its later article on Microsoft's post-incident report gave 11:20 a.m. ET (01:20 JST). Neither source explains the gap, so we show both.

![Three clocks showing the same moment: 03:26 on Friday Nov 13 in Tokyo, 13:26 on Thursday Nov 12 in New York, and 18:26 on Thursday Nov 12 in London](/article-assets/microsoft-365-outage-2026-11-12/timezones.webp)

The same moment in Tokyo, New York and London. This is why the outage carries two dates.

![Timeline of five events from 23:45 JST on Nov 12 to 01:10 JST on Nov 14: the Teams incident TM1550488, Exchange Online mailbox errors, incident MO1550821, Microsoft's servers-unavailable update, and customer impact ending](/article-assets/microsoft-365-outage-2026-11-12/timeline-en.webp)

Times from Microsoft's updates and BleepingComputer's reporting, converted from US Eastern Time to JST. Spacing is not to scale.

- **23:45–00:53 JST, Nov 12–13 (9:45–10:53 a.m. ET, Nov 12):** a separate Teams incident, TM1550488. According to Microsoft's later report, Teams automatically failed over onto Exchange Online's networking infrastructure about 15 hours before the main outage, which raised the load on the gateway servers.
- **01:20–03:26 JST, Nov 13:** Exchange Online mailbox errors begin in the Americas and spread. Microsoft opens MO1550821.
- **08:57 JST, Nov 13 (6:57 p.m. ET, Nov 12):** Microsoft 365 Status posts on X that the problem is "a number of servers being unexpectedly unavailable" ([post](https://x.com/MSFT365Status/status/2121016338181161457)).
- **01:10 JST, Nov 14 (11:10 a.m. ET, Nov 13):** Microsoft says active customer impact has ended. At 12:15 p.m. ET it reports "broad recovery and stability".
- **Weekend of Nov 14–15:** services largely recovered, with a backlog of delayed email still being delivered, per [ABC News](https://abcnews.com/US/outlook-down-microsoft-outage-reported-mail/story?id=138088203).

## What Microsoft said caused it

Microsoft's explanation changed as it learned more, and both versions are on the record. On Nov 13 it told BleepingComputer the outage was "a technical issue not related to cyber or AI / agents" and pointed to an issue during an earlier network capacity upgrade. On Nov 16, BleepingComputer [reported](https://www.bleepingcomputer.com/news/microsoft/microsoft-says-months-old-bug-caused-global-microsoft-365-outage/) Microsoft's preliminary post-incident report, shared with administrators in the admin center. That report describes a chain of four things:

- A software bug introduced in July in an update to Microsoft 365 networking gateway servers, which had not been detected.
- Extra traffic on those gateways after Teams failed over to Exchange Online's network about 15 hours earlier.
- Reduced headroom: roughly 14% of gateway capacity was already offline because of an unrelated issue.
- A cascade: more than 80% of the gateway servers became unresponsive in under two hours. Failover to other servers spread the problem, and cross-region safeguards did not contain it. Exchange Online could not fail over the way Teams, OneDrive and SharePoint could, which is why email was hit hardest.
**Not a hack**Microsoft said on X on Nov 13 that it "found no indication that the outage was caused by malicious or cyber activity." ABC News reported the same message and an apology from Microsoft. We have seen no evidence from any source that contradicts this.

## What it meant in Japan

Microsoft has not published a country breakdown, and we have no count of affected users in Japan. What we can say is about timing: the outage began in the small hours of Friday, Nov 13 JST and was still ongoing when Tokyo offices opened, which means a full Japanese working day without reliable Outlook, Teams or SharePoint for affected tenants. Companies whose tenants sit in Japan data centres may or may not have been affected; Microsoft's advisory did not list regions.

## If your company runs on Microsoft 365

![Checklist of five steps for a Microsoft 365 outage: check the service health page, don't reinstall or reset, switch to the backup channel, expect delayed email rather than lost email, and write a post-mortem for your own team](/article-assets/microsoft-365-outage-2026-11-12/checklist-en.webp)

A five-step routine for any Microsoft 365 outage.

- **Check Microsoft's service health first.** Administrators can open [Health in the Microsoft 365 admin center](https://admin.microsoft.com/Adminportal/Home#/servicehealth); everyone else can read [status.cloud.microsoft](https://status.cloud.microsoft/) or the @MSFT365Status account on X. Look before you change anything.
- **Do not reinstall Outlook or reset passwords.** During a service outage, a failed sign-in is not your password's fault. Resetting it can lock you out when the service returns.
- **Switch to the channel you agreed on in advance.** Phone, SMS, Slack or LINE. The time to decide the backup is before the outage, not during it.
- **Expect delayed email, not lost email.** Microsoft queued messages during recovery and said it was still clearing the backlog days later. Ask senders to resend only if something is still missing after a day.
- **Write your own short post-mortem.** What stopped, who noticed first, what you could not do, and what to pre-arrange. Ten lines is enough.
**Want a Microsoft 365 outage plan for your Tokyo team?**

We set up backup communication channels, admin recovery access and a one-page outage checklist for small companies, in English or Japanese. Book a free consultation.

[Book a free consultation](/en/contact)

## Sources

Microsoft 365 Status on X ([Nov 12 update](https://x.com/MSFT365Status/status/2120962673911181437), [Nov 12, 6:57 p.m. ET update](https://x.com/MSFT365Status/status/2121016338181161457)); BleepingComputer, ["Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide"](https://www.bleepingcomputer.com/news/microsoft/massive-microsoft-365-outage-disrupts-outlook-teams-copilot-worldwide/) (Nov 12–13, 2026) and ["Microsoft says months-old bug caused global Microsoft 365 outage"](https://www.bleepingcomputer.com/news/microsoft/microsoft-says-months-old-bug-caused-global-microsoft-365-outage/) (Nov 16, 2026); ABC News, [Outlook outage updates](https://abcnews.com/US/outlook-down-microsoft-outage-reported-mail/story?id=138088203). Microsoft's preliminary post-incident report was shared with administrators in the admin center and is quoted via BleepingComputer; we have not read it directly. Graphics are our own and show product names only. The photo-style image was generated with ChatGPT and is not a photograph of the event. IT Support in Tokyo is not affiliated with Microsoft. Microsoft, Microsoft 365, Outlook, Teams, SharePoint, Copilot and Defender are trademarks of Microsoft Corporation.

Related: [More tech news](/en/news) · [Apple outage, Nov 17](/en/blog/apple-outage-nov-17-2026-icloud-applecare-apple-business) · [IT support in Tokyo](/en/it-support)

## Source

Canonical HTML: https://itsupportintokyo.com/en/blog/microsoft-365-outage-nov-12-2026-outlook-teams-down
Other language: https://itsupportintokyo.com/ja/blog/microsoft-365-outage-nov-12-2026-outlook-teams-down