The outage that started the soul-searching
How-To Geek senior author Tony Phillips says he has used Outlook in some form for decades. He stayed mostly out of habit, partly because his Hotmail account worked with it. The recent outages made him ask whether Outlook was still the right client for him.
The outage was real and large. On Thursday, November 12, 2026, Microsoft opened Exchange Online incident EX1550543 and Microsoft 365 suite advisory MO1550821. Users could not connect to Exchange Online mailboxes through Outlook on the web, MAPI, Exchange ActiveSync and the REST API. Microsoft 365 features that depend on Exchange Online were also affected.
Here is how the timeline looks from the reporting:
- Microsoft's status account said it was investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas.
- Android Authority reported that Teams, SharePoint Online, Copilot 365 and Defender XDR were also degraded. In fact, that detail comes from its own coverage of Microsoft's status page, not from SOCRadar.
- SOCRadar counted nearly 140,000 Outlook reports on Downdetector globally at the peak.
- Microsoft's preliminary Post-Incident Report, as described by Office 365 IT Pros, confirmed that EX1550543 lasted 23 hours and 50 minutes.
- Microsoft's status account said on November 14 that it had restored service to the remaining impacted customers and regions. Android Authority carried that update.
The sources give slightly different start times and report counts. This is normal for outages, because external monitors and Microsoft's own service history measure different things. The Phillips article describes an event that was already resolved when it was published.
What Phillips actually did
The article is a first-person account, not a benchmark. Phillips is clear about that. He says the outage would have happened whichever client he used.
Setup. He added his personal Hotmail account first. He says Thunderbird detected the settings, opened Microsoft's sign-in page, and had the account working in under a minute. His folders and messages appeared without any manual server configuration. He then added a business Gmail account, which he says went just as smoothly.
That "under a minute" figure is his own experience. Your timing will vary with your account type, any multi-factor prompts, and your tenant's policies.
Threads. He found long, multi-participant conversations easier to follow in Thunderbird than in the new Outlook for Windows. He describes a clean chronological display with controls to jump between replies. By his account, the new Outlook means more expanding and collapsing, even with conversation view on.
Interface. He likes the traditional layout, with familiar menus, right-click options and easy-to-find settings. He says it felt consistently responsive. He also says he did not benchmark anything and is not claiming it is objectively faster.
Multiple accounts. He used Unified Folders to merge inboxes, sent items and archives. Mixed-account lists made it unclear where a message came from. So he switched to Table View and added an Account column.
Where Outlook still wins
Phillips is candid about the trade-offs:
- Calendars and contacts. Email worked almost immediately. Microsoft calendars and contacts felt less straightforward. Thunderbird offered to sync his Google calendars during setup. He did not dig deeper because he schedules through Google Calendar on his phone.
- Microsoft ecosystem. He says Outlook remains stronger for workflows built around Teams, Microsoft 365 services and enterprise features.
This is one person's experience, not proof that Thunderbird can't handle Microsoft calendars. For an enterprise user, though, those gaps decide whether switching is practical.
Client versus service
Phillips' key observation is that Thunderbird was "simply a different way of accessing the same account." That is the practical point readers should take from the piece. It also cuts the other way.
If your mailbox is on Exchange Online or Outlook.com, Thunderbird is still talking to Microsoft's servers. The November 12 incident was a server-side failure. It affected several connection methods. Microsoft's own status updates said returned servers could become unresponsive again under load, so it was limiting which traffic types could reach affected infrastructure. A different desktop client would not have made that mailbox reachable.
This is my analysis, not something Phillips or Microsoft claims. The evidence available supports the following points:
- Switching clients can improve your reading experience, your account consolidation and your day-to-day comfort.
- It does not make a Microsoft-hosted mailbox independent of Microsoft.
- Already-downloaded mail may still be readable in a client that keeps a local copy. That depends on your sync settings and account type, and none of the sources tested it.
- Real outage resilience comes from other measures: a second mail account for critical contacts, alternative channels, and for admins, a documented continuity plan.
Setting up Thunderbird with a Microsoft account
I couldn't retrieve Mozilla's documentation in this session, so treat the following as the general flow described in Thunderbird's setup process. It matches Phillips' experience, but check the current wording in your version.
- Open Thunderbird's account setup.
- Enter your name, email address and, where required, a password.
- Let Thunderbird look up the provider's settings, then confirm them.
- Sign in through the provider's own OAuth sign-in page. Complete multi-factor authentication if it asks.
- Choose whether to add address books and calendars if the provider offers them.
- If the settings can't be found automatically, you may need to configure the servers manually.
For business Microsoft 365 accounts, an administrator's tenant policies may restrict third-party clients or OAuth app consent. Check with your IT team before assuming a personal-account experience will carry over.
Should Windows users switch?
It depends on your workflow, and Phillips doesn't claim otherwise.
| Your situation | Likely fit |
|---|---|
| Personal Hotmail or Gmail, mostly email, many long threads | Thunderbird is worth a trial |
| Several accounts you want in one inbox | Unified Folders and Table View, as Phillips used |
| Heavy Teams, shared calendars and Microsoft 365 integration | Outlook is likely the better fit, per Phillips |
| Managed enterprise tenant | Check admin policy first |
The sensible approach is the one Phillips took: add your existing account to a second client and see what you think. You don't have to migrate or change your address to try it. A bad week at Microsoft won't be solved by a new inbox app, but it is a reasonable moment to ask why you use the one you do.
References
- Outlook's latest outages convinced me to finally try Thunderbird, and I liked it far more than I expected How-To Geek · 2026-11-17T18:30:15+00:00
- Microsoft Outlook Outage: What You Need to Know socradar.io
- Outlook Down Nov 12: EX1550543 Health-Check Fix explainx.ai