On Thursday 12 November, Microsoft 365 had two problems one after the other. First, Teams was disrupted for users in North and South America for about an hour. Microsoft fixed that. Then, 24 minutes later, people could no longer open their mailboxes in Outlook. That second problem spread to the whole world and to other Microsoft 365 services.
We are publishing this on Friday morning, 13 November. The second outage is not over yet. Email is starting to come back, but Microsoft has not confirmed a cause. This post is a summary of what is known so far. We will write a follow-up when there is more.
Timeline
All times are UTC. Central European time is one hour ahead.
| Time | What happened |
|---|---|
| Thursday 14:45 to 15:53 | Teams problem in North and South America. Messages were delayed or failed to send, and chats were slow to load. Microsoft said the cause was "resource contention" in its infrastructure and marked it as resolved. |
| Thursday 16:17 | People can't open their mailboxes in Outlook on the web, on desktop or on mobile. First reported in the Americas. |
| Thursday 18:19 | Microsoft says its servers are under "elevated load across multiple regions". |
| Thursday 18:26 | Microsoft opens a wider incident that covers the other Microsoft 365 services that depend on email. It says users in any region may be affected. |
| Thursday around 19:06 | Microsoft pauses all planned changes to its systems. |
| Thursday around 19:18 | Microsoft says the load is not caused by more traffic. A number of servers have become unavailable, and the rest are struggling. |
| Thursday 22:00 | Microsoft says what it has tried so far hasn't worked. |
| Friday around 00:00 | Servers that are restarted stop responding again once users reconnect. |
| Friday, early hours | Microsoft starts undoing a recent network change that was made around the time the problem began. It says there is no sign of malicious activity. |
| Friday 07:29 | Microsoft reports "positive results for server stability" after applying a patch. |
| Friday around 09:10 | Email starts to stabilise. Microsoft says delayed emails will be kept for 48 hours, so they should still arrive. |
Microsoft has not said whether the Teams problem and the email outage are connected. They were recorded as two separate incidents (TM1550488 for Teams, EX1550543 and MO1550821 for the rest).
How many people are affected
Nobody outside Microsoft knows, and Microsoft has not given a number.
There are some indications. Downdetector had about 130,000 reports about Outlook at the peak on Thursday. Those are only the people who took the time to report it, so the real number is much higher. Al Jazeera counted reports from 74 countries within the first hour. Government systems in Singapore, Japan and Australia were affected, as were the Supreme Court of the Philippines and email at the US House of Representatives.
What is and isn't working
Not working, or working badly:
- Email. Outlook on all devices. Emails are delayed, but Microsoft says they are not lost.
- Teams calendar and meeting scheduling. Chat and calls have mostly kept working.
- Copilot. It can't read email or calendars, and in some cases files.
- Automations and integrations that read email or calendars, including Power Platform flows and some third-party tools.
- Security and admin tools. Microsoft Defender, Microsoft Purview, Intune and some pages in the admin center.
Still working:
- Azure. Its status page shows no incident.
- SharePoint and OneDrive file storage, for the most part. People can still open and share files.
What Microsoft has said
Microsoft has posted updates about every half hour, including overnight. It has been open about things that didn't work, which is helpful.
Its explanation so far is this. Some of the servers that run Outlook's email service failed their automatic health checks and were taken out of service. The servers that were left had to handle everyone and couldn't keep up. When Microsoft restarted servers, every Outlook client tried to reconnect at the same time, and the servers went down again. That is why recovery has taken so long.
Charles Lamanna, a senior Microsoft executive, wrote on X on Thursday that "there is no indication this is the result of malicious or cyber activity". Microsoft's status updates have said the same.
Microsoft has not confirmed the root cause. It has promised a full report.
The rumours
When something this big breaks and there is no official cause, people fill the gap. These are the theories we have seen most:
It is a cyberattack. This spread quickly on social media. Microsoft says there is no sign of it. One thing supports that: an attack that floods a service would show up as a jump in traffic, and Microsoft says traffic did not go up.
It was caused by Patch Tuesday. Microsoft released its monthly security updates two days before, with nearly 1,100 fixes. The timing looks suspicious, but Microsoft has not connected the two, and nothing published so far does.
AI overloaded the service. Copilot stopped working, so some people assumed Copilot was the cause. More likely it is the other way round. Copilot depends on email and calendars, and those were down.
AWS and Google are down too. Reports for both went up on Downdetector on Thursday. Amazon says its services are working normally. When email stops, people often report whatever service they happened to be using.
We don't know the cause either. Based on what Microsoft has published, an internal technical fault fits the facts better than any of these theories. We will wait for the report.
What this means for your data
This is the part we want to add, because it is what we work on every day. 1Security shows companies who has access to what in Microsoft 365, and what people do with that access.
When email goes down, people still have work to finish. So they find another way:
- They share a file as a link instead of attaching it to an email. When they are in a hurry they often choose "anyone with the link", because it always works. We explained why that is risky in anyone with the link is a credential.
- They send documents from a private email account or through WhatsApp.
- They download files to their own computer so they can keep working.
- They use a personal laptop or phone.
That is normal, and nobody should be blamed for it. But it happened at a bad moment. Defender and Purview were also affected by the outage. Microsoft warned that rules for data loss prevention and sensitivity labels "may experience delays or failures". So some sharing that would normally be checked or blocked may not have been.
When things are back to normal, we would check the following for the period since Thursday 16:17 UTC:
- New sharing links, especially public ones and ones sent to outside companies you don't normally share with.
- Unusually large downloads by a single user.
- New email forwarding rules, for example to a private address.
- New apps that were given access to your tenant.
- Sign-ins from new devices or countries.
One warning for the coming days. Attackers will use the outage as an excuse for phishing. Expect emails that say your mailbox has been restored or will be blocked, and that you need to sign in again. Tell your users today that Microsoft will not ask them to sign in through a link in an email.
One honest note about our own product. 1Security reads Microsoft 365 through Microsoft's APIs, so when those are slow, our data for the last few hours is delayed too. What we already collected before the outage is stored outside Microsoft 365 and stayed available. That gives you something to compare against: what access and sharing looked like on Wednesday, and what changed since.
Common questions
Are emails lost? Microsoft says no. They are delayed, and Microsoft is keeping them for 48 hours. Please don't resend everything, or people will get each message twice.
Was our data exposed? Microsoft has reported no unauthorised access. The services were unavailable, but nothing suggests anyone broke in.
Where can we check the status if the admin center doesn't load? Go to status.cloud.microsoft. It is public and you don't need to sign in. Microsoft also posts updates on the @MSFT365Status account on X. It is worth bookmarking the status page now.
Should the helpdesk reset passwords or set up Outlook again? No. The problem is on Microsoft's side, so that won't help. It only costs the helpdesk time and frustrates users.
Where should people communicate while email is down? Ideally on a backup channel that does not depend on Microsoft 365 and that you agreed on in advance. If you didn't have one this time, people chose their own. It is worth finding out what they used, and agreeing on one for next time.
Should we turn off a security policy so people can work? We would not. Settings that are turned off in a hurry are often never turned back on. If you really need an exception, write down who approved it and when it ends.


