When Outlook will not open, the day gets small and strange. You cannot get the school message, the bill, the reset link, the thread that explains what was supposed to happen next. That is what a lot of people ran into when Microsoft 365 had a major disruption in mid-November 2026.
Microsoft’s own status updates, under incident MO1550821, said users may be unable to connect to multiple Microsoft 365 services. Those updates record a start time of 18:26 UTC on 12 November 2026 — late morning in the U.S. Pacific time zone. In an update at 17:57 UTC on 13 November 2026, Microsoft apologized and said it was seeing broad recovery and stability. It described the event as a technical issue, said an issue from an earlier network capacity upgrade had surfaced after a recent network change, and said it had addressed that underlying issue while it continued to restore remaining customers and regions. A full post-incident report, Microsoft said, would come after its review. As of that update, the incident was still listed as service degradation. Those are Microsoft’s words, as collected in a public extract of its admin-center incident reports.
Microsoft listed a clear, practical impact on email: people may have been unable to open a mailbox in Outlook on the web, in Outlook on a computer, or on a phone, and mail may have been delayed. It also said that most core Microsoft Teams features — joining calls, meetings, group chats, and channel messages — were not impacted, while features that depend on Exchange, such as some calendar tasks, were. Files sitting directly in SharePoint, Microsoft said, remained reachable; features that depend on Exchange may not have been.
This is not a story that Microsoft “got hacked” last week. Microsoft described a technical issue. It is a story about what happens to ordinary life when so much of it runs through one company’s mail system — and about a simple plan for the logins that should still be openable if that system, or you, cannot.
This was not the first time the same door stuck.
Microsoft has already published a detailed review of a wider incident on 29–30 October 2025. In that Post Incident Review (tracking ID YKYN-BWZ), Microsoft says Azure Front Door and its content delivery network — the edge layer that many Microsoft services and customer sites use — had connection timeouts and DNS problems from 15:41 UTC on 29 October until 00:05 UTC on 30 October 2025. Microsoft’s stated cause was a sequence of ordinary, valid configuration changes that, across two software versions, produced incompatible settings, uncovered a hidden bug, and spread globally because the warning system still thought the system was healthy. Microsoft 365 was among the services Microsoft listed as affected, along with the Azure Portal.
You do not need the engineering detail to see the pattern. One platform, used by many products, had a bad hour — in that case, more than eight hours — and a lot of doors closed together.
A separate official report, about keys rather than downtime.
In 2023, a different kind of problem made official news. A threat actor Microsoft calls Storm-0558 used forged sign-in tokens to read some people’s Exchange Online email. Microsoft’s public analysis in July 2023 said this began on 15 May 2023 and reached email at approximately 25 organizations, including government agencies, and related personal accounts. In March 2024, the U.S. Cyber Safety Review Board published an independent report. Citing Microsoft, the Board wrote that the actor accessed mailboxes at 22 organizations and 503 related personal accounts worldwide, including senior U.S. government officials named in the report.
The Board found that the intrusion was preventable and should never have happened, and that it succeeded because of a cascade of security failures at Microsoft. In plain words, a signing key — the Board called signing keys the “cryptographic equivalent of crown jewels” — was used in a way it should not have been, and a check that should have rejected the wrong kind of key for work email was not in place. Microsoft published its own investigation and later updated it, including to correct earlier technical detail. The Board noted that Microsoft cooperated fully with the review.
This is not a claim that your Outlook account was in that incident. The Board’s figures are about the accounts Microsoft reported as accessed. It is a reminder that the same company that holds a great deal of the world’s mail also holds the keys that say who is allowed to read it. Official reviewers thought that concentration, and the failures around it, deserved a public report.
A different place a vault can live.
Qerron is not a new Outlook. It will not send your mail. It is a private vault you open with a passkey — Face, fingerprint, or a security key — with no master password to invent or forget. The notes and logins you put in are encrypted so we cannot read them. It runs on the Internet Computer, a public network described in official documentation at internetcomputer.org.
In that documentation, the network is made of groups of independent machines called subnets, run by different node providers, that agree on what the software did through a consensus process. Programs, called canisters, are copied across the machines in a subnet, and no single machine is supposed to be able to change that state by itself. A technique called chain-key cryptography splits a subnet’s secret key so no one machine holds it. That is the idea, in ordinary language: the vault is not sitting on one company’s private servers, and one operator does not hold the only copy of the lock.
That is not a promise that nothing can ever go wrong, and it is not a promise that a product is unhackable. It is a different place to keep the things you would need if mail is down, or if you yourself cannot open a device.
A plan for the person who should be able to open it if you cannot.
You can share a vault now with a partner or a family member, using a one-time invite link and their own passkey. You can also set a check-in: you name a person, choose which vaults, and choose how often you will check in. If you stop, and the waiting period you set has passed, they can be given access to what you picked. If you check in late, access is taken back.
Qerron is a secure storage and access tool. It is not a will, not legal advice, and not a custodian of your assets. For families thinking about that question at more length, there is what happens to your passwords when you die.
You can try the full product for fourteen days. No credit card is required. Personal is $48 a year. Household is $72 a year for up to six people. If you want the business reading of the same week, see what official reviews say for operators. If you want the protocol in more detail, see how the Internet Computer is built. The shorter earlier note is When Microsoft goes down, half the internet goes with it.
Sources
- Microsoft service health updates for incident MO1550821, as recorded in the University of Pennsylvania’s public extract of Microsoft 365 admin-center incident reports: mailservices.isc.upenn.edu/computing/email/penno365/alerts/ms-incidents.html
- Microsoft Azure Post Incident Review, tracking ID YKYN-BWZ, 29–30 October 2025: azure.status.microsoft/en-us/status/history/?trackingId=YKYN-BWZ
- Microsoft Threat Intelligence, “Analysis of Storm-0558 techniques for unauthorized email access,” 14 July 2023: microsoft.com/en-us/security/blog/2023/07/14/analysis-of-storm-0558-techniques-for-unauthorized-email-access/
- Microsoft Security Response Center investigation of Storm-0558 key acquisition, 6 September 2023, updated 12 March 2024: microsoft.com/en-us/msrc/blog/2023/09/results-of-major-technical-investigations-for-storm-0558-key-acquisition
- Cyber Safety Review Board, “Review of the Summer 2023 Microsoft Exchange Online Intrusion,” 20 March 2024: cisa.gov/resources-tools/resources/CSRB-Review-Summer-2023-MEO-Intrusion
- ICP developer documentation, Network overview and Chain-key cryptography
Try it free for 14 days, no credit card needed.