The Day Outlook Took a Long Lunch: What the Microsoft 365 Outage Teaches Us About Running on One Platform

On Thursday 12 November, a little before 8 in the evening Athens time, millions of people clicked "Send" and watched their email sit in the Outbox like it was waiting for a bus. Outlook was down. So were Teams, SharePoint, Copilot, Planner, To Do and a handful of Microsoft's security tools. For many offices in Europe the evening was already over, so the full experience arrived on Friday morning, right on schedule, the 13th.

We use Microsoft 365 too, so this is not a story about other people. Here is what happened, what it looked like from inside an agency that runs on it, and the short list of things we think every business should have ready before the next one.

What happened in the Microsoft 365 outage?

Problems started shortly before 1 p.m. US Eastern time on Thursday 12 November 2026 (around 20:00 in Greece). Within minutes, close to 130,000 people had reported Outlook problems on Downdetector.

Microsoft's status page listed Exchange Online (Outlook email), Microsoft Teams, SharePoint Online, Microsoft 365 Copilot, Planner, To Do, Intune, Defender XDR and Defender for Office 365 as affected.

Microsoft's explanation, in its own words: "a process on the affected servers responsible for establishing secure connections becomes overwhelmed," "causing the servers to stop processing requests." It said it was reverting a recent network configuration change that lined up with the start of the problem, and that it had put temporary traffic limits in place in some locations. It also said it found no sign of malicious activity, so nobody hacked anything. A setting changed, a busy process got busier, and the dominoes did the rest.

Recovery came in stages. Overnight Microsoft reported "partial recovery across regions", and by Friday it described "encouraging recovery progress" with email queues heading back to normal. Some users were fine by breakfast. Others spent the morning refreshing.

What it looked like from our side

We run a set of automations on top of Microsoft 365: inbox sorting, a morning briefing, calendar checks before meetings. From around 2 a.m. Athens time they started getting the digital equivalent of a shrug. Mail requests returned server errors. A mailbox check failed, waited, tried again, and failed again, every fifteen minutes, all night, with the patience of someone on hold with their bank.

The morning briefing couldn't read the calendar, so it didn't prepare meeting notes. One inbox search failed so many times that the assistant gave up on it and read the mail by date instead, which is roughly what a person does when the search bar stops working.

Nothing was lost. Everything that failed tried again and caught up once Microsoft came back. That only worked because we had built for failure from the start: retries, logs, and a rule that a failed check gets reported rather than quietly skipped. The lesson isn't really about Microsoft. Every cloud service goes down sometimes. What you control is what your business does in those hours.

Why a 365 outage hurts more than it used to

Five years ago, "email is down" meant you couldn't send email. Today the same login runs your email, your calls, your shared files, your calendar, your task lists and, more and more, your AI assistant. When one secure-connection process gets overwhelmed, a whole company can lose its voice at once.

For any company that runs everything on one platform, the cost shows up quickly:

• Quotes and invoices that don't arrive, or arrive a day late.
• Client meetings on Teams that turn into a scramble for a phone number.
• Staff who can't open the shared file they need, so they wait.
• Website contact forms that send their leads to an inbox nobody can open.

That last one is the quiet one. Your website keeps working and keeps collecting enquiries, but if those enquiries only go to a Microsoft 365 mailbox, they pile up where no one can see them until the service returns.

A plain checklist for the next outage

None of this is expensive, and most of it takes an afternoon.

1. Know where to check

Bookmark Microsoft's official status page (status.cloud.microsoft) and the Microsoft 365 Status account on X. When something feels off, check there first before restarting every router in the building.

2. Have a second way to reach your team

A WhatsApp or Signal group for the whole team, with a simple rule: if Teams is down, we talk here. Write it down now, while everything works.

3. Keep client phone numbers outside the inbox

If the only copy of a client's phone number sits in an email signature inside Outlook, you can't call them when Outlook is down. A CRM, a shared sheet stored somewhere else, or even your phone's contacts will do.

4. Make your website forms send to two places

Have your contact forms store every submission on the website itself as well as emailing it. That way a lead that arrives during an outage is saved and visible, and nobody has to hope the email turns up later. If you're not sure how your forms work today, that's worth a check, and so is the rest of the site, since old plugins and forgotten forms are also where security problems tend to start.

5. Give automations a retry and a report

If you use automations or AI tools that depend on Microsoft 365, make sure they retry failed requests and tell a human when something stays broken. An automation that fails silently is worse than no automation, because everyone assumes the work got done.

6. Prepare a short customer message

Two sentences you can post on your website or social channels: "Our email is affected by the current Microsoft outage. Please call us on [number] or message us on WhatsApp." It saves you writing one under pressure.

Should you leave Microsoft 365 because of this?

No, for most businesses. Google Workspace, Zoho and every other provider have outages too, and moving a company's email, files and calendars has a real cost. A better plan is to accept that one day per year or so your main platform will have a bad afternoon, and to make sure your business can keep talking to clients when it does.

Frequently asked questions

When did the Microsoft 365 outage start?

It began shortly before 1 p.m. US Eastern time on Thursday 12 November 2026, around 20:00 in Greece, and carried on into Friday 13 November, with services coming back in stages across regions.

What caused the Microsoft outage?

Microsoft said a process on its servers that sets up secure connections became overwhelmed, so the servers stopped processing requests. It linked the timing to a recent network configuration change, which it reverted, and said there was no sign of malicious activity.

Were emails lost during the outage?

Microsoft's updates talked about delayed email delivery and queues returning to normal rather than lost mail. In practice most messages arrived late. If something important is still missing, ask the sender to resend it.

How can a business prepare for the next one?

Set up a backup channel for your team, keep client phone numbers outside your inbox, make your website forms save submissions on the site as well as emailing them, and have a two-line customer message ready. That covers most of the damage.

How we can help

At Ruler we set up websites, forms and AI automations that keep working when one service has a bad day: retries, logs, and a person told when something breaks. If you want us to check how your site and inbox would cope with the next outage, get in touch. We'll answer, even if Outlook doesn't.