Microsoft has published its first detailed explanation of last week’s Microsoft 365 outage. Microsoft’s preliminary incident report, republished in full by Office Watch, says three separate problems lined up to stop most users reaching their email for almost a full day.
If you’re on Google Workspace, iCloud or another provider, your own email kept working, but anyone you deal with on Microsoft 365 may have been out of reach.
What happened
According to the report, the outage ran from 4.20 pm UTC on Thursday 12 November to 4.10 pm UTC on Friday 13 November. Most users couldn’t open their mailbox in any mail client, and many saw delayed email. Parts of Teams, SharePoint, OneDrive and Copilot that rely on Exchange Online were hit too, though Microsoft says those services largely stayed online.
It starts with a fix Microsoft made in July for the gateway servers in front of Exchange Online. It ran for more than three months without trouble, but carried a latent defect that made servers seize up under certain heavy loads, especially newer machines with more processor cores. Microsoft says its load testing used weaker hardware, so the bug went unnoticed, and that neither the defect nor the fix applies to wider Windows deployments.
On Thursday, two other things coincided. About 15 hours earlier, Teams traffic had failed over onto the gateway Exchange uses, a routine move. And nearly 14% of the gateway’s capacity was already out of service after an unrelated issue the day before.
Microsoft says that extra load and reduced capacity set off the July bug at peak US traffic. Automatic systems moved traffic to healthy servers, which then failed in turn, and within two hours more than 80% of servers were unresponsive. The barriers that normally contain a failure to one region didn’t hold, because of what Microsoft calls a separate issue it hasn’t yet explained.
Recovery was slow because returning servers were swamped by waiting traffic, and the usual rollback tools couldn’t quickly reverse a months-old change. Engineers built an update restoring the earlier code and brought servers back in batches.
The BBC reported that the affected products have more than 430 million users and that problems were reported in more than 70 countries. In the UK, cyber minister Liz Lloyd told the BBC that the impact on frontline services such as 999 calls had been limited.
What Microsoft and others have said
A Microsoft spokesperson told the BBC the company was “deeply sorry” and that the cause was a technical issue unrelated to cyber activity or AI agents. Microsoft executive Charles Lamanna said its teams were reviewing how to prevent similar problems.
Since then, Microsoft Threat Intelligence has warned of phishing emails exploiting the outage. As ITNews reported, the messages impersonated Microsoft 365 service health notices and quoted the real incident number, EX1550543. Some claimed that mail held during the outage would be deleted within 24 hours unless the recipient clicked a link.
Adaptavist’s Matt Saunders told the BBC that running a second service is close to impossible for most businesses, so the realistic answer is a plan for working without these tools.
What it means for you
Plenty of Mac-first SMEs run email on Google Workspace or iCloud. If that’s you, you’ll still have felt Thursday through any client or supplier on Microsoft 365. Either way, your Macs, iPhones and Apple Business setup weren’t affected, because the fault sat entirely in Microsoft’s own servers.
Any cloud email provider can have a bad day, so this applies whoever hosts yours. In Dr Logic’s experience, the businesses that cope best have already agreed who tells clients what’s going on and how. We wouldn’t rush to add a second email provider: for most SMEs the cost and admin rarely pays off, and a one-page plan does more. If you don’t have that plan written down, we’re happy to help you put one together.
We’d act on the phishing campaign this week. An inbox full of genuine outage updates is exactly where a fake one gets clicked.
What we’d do now
- Check that anything important sent on Thursday or Friday arrived. Microsoft extended its delivery window so mail to its users wasn’t bounced. If you’re on Microsoft 365, Office Watch notes that mobile apps may have failed to send, so check Outboxes too.
- Tell staff about the fake outage emails, which can land in any inbox. Anything about held or deleted messages goes to IT, and real service status lives in your provider’s own admin console or status page.
- Write down your fallback: which approved channel you’ll use when email is down, so client files don’t drift onto personal WhatsApp, and who calls key clients from a contact list that doesn’t live in your email.
- Read Microsoft’s final report when it lands around 20 November. We will, and we’ll update this piece.





















