The outage began on 12 November 2026, at around 18:15 to 18:26 UTC. It affected Exchange Online mailboxes first, then other Microsoft 365 services that depend on it, including Teams, SharePoint Online, Copilot, and Microsoft Defender XDR. Microsoft's incident IDs are EX1550543 for Exchange Online and MO1550821 for dependent services.
Downdetector recorded Outlook reports peaking above 130,000 in the United States and close to 140,000 globally. These figures count reports, not confirmed affected users, so they should not be read as a precise number of victims. The company's executive Charles Lamanna said on X that a security breach was not the cause.
Microsoft has not published a full root cause yet. Accounts of the early cause differ, and this article does not repeat any of them as established.
Are you affected?
Two groups should act now.
Anyone who received an email about "held" messages during the outage. Do not click any links in it, even if it claims to be from Microsoft or your IT department.
Anyone who clicked a link or entered a password after 12 November. Assume the account may be compromised until proven otherwise.
If you did not receive such an email and your mail is working normally, you are not affected by this specific lure.
How the phishing works
According to Microsoft Threat Intelligence, phishing messages detected on 13 November falsely claimed that some emails had been held during the outage. The observed patterns include:
Element | What to look for |
|---|---|
Subject line | "Outage" followed by a six-character code, for example "Outage – [code]" |
Sender display name | An organisation-style prefix followed by "Outage Notification" or "Service Health" |
Sender domains | moments-notice.com, planetmaison.com and newbooker.com, as identified by Microsoft |
Call to action | A button or link to "restore messages" or verify an account before messages are deleted |
Microsoft assessed the activity as consistent with credential phishing. The company has not confirmed that credentials were collected or that malware was delivered.
Microsoft's own advice is clear: outage updates appear only on the Microsoft 365 admin center's Service health page. Microsoft does not ask users to restore held messages through an email link, and it does not need users to reset passwords to recover from an outage.
What to do
Verify the outage in one place only. Check the Service health page in the Microsoft 365 admin center, not the email, the link, or a phone number in the message.
Do not click links in outage-themed emails. Report them using your organisation's phishing reporting process or Outlook's report button.
If you entered credentials on a suspicious page, change your password immediately from a known-good device, then check for new inbox rules, forwarding addresses, and unfamiliar sign-ins in your account activity log.
Revoke active sessions for any affected account, and enable or re-check multi-factor authentication.
Administrators should review Safe Links policies in Microsoft Defender for Office 365, confirm that links in these emails are blocked or rewritten, and use Threat Explorer and Defender XDR advanced hunting to find users who interacted with the messages. Microsoft recommends this specific investigation path.
Warn users before the next outage. A short message explaining that Microsoft does not ask for password resets to restore mail will reduce the chance that a lure works.
Why the timing matters
Attackers do not need a real breach to exploit a real outage. When people are worried about missing messages, they are more likely to click a link that promises a quick fix. The outage gave the lure its credibility, because many users had just experienced the disruption.
Organisations should treat any major service disruption as a predictable phishing opportunity, and plan communication before the next one. Teams that rely on email to share outage updates should provide a backup channel, such as a phone tree or a messaging tool, so that staff do not have to trust unknown messages to find out what is happening.
The lesson
The outage was a technical event, but the phishing wave is a human one. Most users do not need to understand how Exchange Online works to protect themselves. They need to know where Microsoft posts official updates, and that a message asking them to click to restore mail is not one of them.