On Thursday, November 12, 2026, a software bug inside Microsoft’s network took down Outlook, Teams, SharePoint and Copilot together. Millions of users lost email first, and email stayed down the longest. In some regions the outage ran more than 12 hours.
The services look separate on a screen. Underneath, they ride the same gateways and the same sign-in. That shared base is the whole story for a Canadian office. When it blinks, the inbox, the files, the meetings and the AI assistant blink in the same minute.
What Microsoft says happened
Microsoft published its early incident report today, November 16. A software bug entered its Microsoft 365 networking gateway servers in an update back in July. The bug sat quiet for months. Traffic then shifted onto those gateways, and the fault spread.
At the worst point, more than 80% of the gateway servers were not answering. Safeguards meant to keep a problem inside one region did not contain it. Teams, OneDrive and SharePoint moved to other infrastructure and recovered sooner. Exchange Online could not move, which is why email took the hardest hit.
Microsoft is plain on one point. This was a technical failure inside its own network. It was not a cyberattack.
Service came back in stages through Friday, November 13. Microsoft marked the incident restored early on Saturday, November 14, after the backlog of queued email had been delivered.
One detail from the outage deserves its own line. Some users could not sign in to other services during those hours because their verification codes were sent to an Outlook inbox they could not open. The key to the second door was sitting inside the first one.
The AI assistant shares the same cord
Microsoft’s own advisory listed Microsoft 365 Copilot among the services that could be hit. Copilot Chat might not load or answer, and it could not reach email, calendar or files while the network was down.
That listing matters more than the outage itself. Firms across Canada are moving real work into Copilot and tools like it. Drafting, summaries, meeting notes and first passes at documents now start with the assistant.
On Thursday, the assistant had the same morning off as the inbox. An AI tool is only as separate as the network under it. A firm that counts Copilot as its backup for a busy day has a backup that shares a power cord with the thing it backs up.
The precaution is a map, drawn before the next blink
None of the checks below need new software. They need one quiet hour and a list.
First, list the tools your team opens before 9 in the morning. Mark every one that signs in with a Microsoft account. Most offices have never seen that list written down. The list is usually longer than anyone in the room expects.
Second, find the second doors. For each tool on the list, note whether it has a working web version, a phone app on a separate path, or an export your team can read without signing in. A tool with no second door is a single point of failure, whatever the contract says.
Third, move the codes. Sign-in codes and account recovery routes that land in the same inbox they protect form a loop. Thursday closed that loop for real users. A second channel for codes, held by a named person, breaks it.
Fourth, keep one contact path outside the suite. Your team needs one way to reach each other, and your customers, that does not start with the same login as everything else. A phone tree on paper in a drawer sounds old. On Thursday it would have been the fastest system in the building.
The quiet cost
No firm lost its files on Thursday. The data sat safe the whole time. What firms lost was the day itself, plus the trust that the floor under the office is solid.
That floor is rented now, from a small number of very large landlords. The rent is fair and the buildings are good. Thursday still showed what one bug in one wall can do to every tenant at once.
The firms that handled the day best were not the ones with the most tools. They were the ones that already knew which of their tools shared a wall.
Start with the map. The one hour it takes is the cheapest precaution in the building, and it pays out on the worst day of the year.
More on running AI inside a Canadian business sits on the Start Here page.