In the same week, Microsoft 365 went down for nearly a full day, and Microsoft’s November Windows updates turned out to break some printing. None of this argues for leaving the cloud or skipping patches. It does argue for a plan B, which most businesses discover they need about an hour into an outage.
What happened
The Microsoft 365 outage. On Thursday, November 12, Exchange Online started failing around 11:20 a.m. Eastern. Outlook and email were hit hardest, and problems spread to Teams calendars and meeting scheduling, Copilot, SharePoint, Intune and other services. Microsoft reported customer impact ended late Friday morning, November 13, nearly 24 hours later. In its preliminary report, Microsoft traced the outage to a latent software bug in a July update to the gateway servers that carry Microsoft 365 traffic. It says this was not a cyberattack. A final report is expected around November 20.
The November Windows updates. Microsoft’s November 10 security updates came with two acknowledged problems:
- Printing failures. Some print jobs can fail when a document contains an image that renders at zero height or width, with Word the most commonly affected app. It spans Windows 10 and 11 and Windows Server 2016 through 2025. At the time of writing, Microsoft is still investigating and has not published a fix.
- Activation errors. The updates also broke SLMGR, the built-in tool admins use to manage Windows licensing and activation (error 0x80041008). Microsoft released an optional out-of-band (off-schedule) fix on November 13 and says devices that were already activated stay activated.
What it means for you
A day without email is no longer a minor inconvenience. Orders, approvals, password resets and customer requests all run through it. If your continuity plan assumes Microsoft 365 is always up, last Thursday was a free stress test, and the grading was not on a curve.
The printing bug makes the same point from the other direction. Update problems are normal; what hurts is pushing them to every device at once. When a Word document fails to print, most help desks look at the printer first. This time, the printer is innocent.
The activation fix also needs attention. For Windows Server and Windows 10 LTSC (long-term servicing) editions, it is available only through the Microsoft Update Catalog, so it won’t show up by itself.
Your options
- Plan for cloud downtime. Decide in advance how staff will reach customers, vendors and each other if email or Teams is down: a phone tree, a texting group, or a secondary channel that does not depend on the same provider.
- Stage your updates. Send monthly patches to a pilot group first, including a few heavy printers and a server or two, then roll out more widely after a few days.
- Know your options under your agreement. Read your Microsoft 365 service terms so you know what an outage entitles you to, and how to claim it, before you need to.
What we recommend
- Write a one-page “Microsoft 365 is down” plan covering who decides, how people communicate, and where critical contacts live offline.
- Keep key phone numbers and procedures somewhere other than Outlook and SharePoint.
- Deploy updates in rings (pilot first, then everyone) rather than all at once.
- Apply the November 13 out-of-band update wherever you manage activation with SLMGR.
- Brief your help desk on the printing issue, and watch Microsoft’s release health page for a fix.
How DTM can help
We help IT teams with Microsoft licensing, collaboration tools, servers, endpoints and printers, plus nationwide on-site print repair, maintenance and supplies. Whether you’re reviewing your Microsoft 365 setup, adding a backup communication option or sorting out a printer that suddenly won’t cooperate, your dedicated DTM contact can help you weigh the options across vendors.
Want help building your plan B? Contact us.
Details on both issues may change as Microsoft publishes its final outage report (expected around November 20) and a printing fix; check Microsoft’s service health and release health pages for the latest.
Sources
- Office Watch: Microsoft 365 outage, what went wrong (reproduces Microsoft’s preliminary post-incident report)
- MacRumors: Microsoft 365 outage resolving after nearly 24 hours (Nov 13, 2026)
- Digital Trends: Microsoft’s longest outage in years is finally over
- BleepingComputer: Microsoft says November security updates cause printing issues
- The Register: Microsoft has an image problem with November’s Windows security update
- Microsoft: Windows message center (out-of-band update, Nov 13, 2026)
- Cyber Security News: out-of-band update for Windows licensing and activation errors
- BleepingComputer: Microsoft says months-old bug caused global Microsoft 365 outage
- 365Fanatic: Microsoft 365 outage, 12 November 2026 post-incident report summary
