The emails claimed messages held during the outage would be deleted within 24 hours unless recipients clicked to recover them.
What happened
Microsoft Threat Intelligence observed a coordinated, high-volume phishing campaign on November 13, 2026, that used fake Microsoft 365 service-health notifications to target organizations across multiple sectors worldwide, according to Microsoft. The emails followed a real Microsoft 365 service disruption on November 12. They claimed that emails had been held during the outage and would be deleted within 24 hours unless the recipient clicked to restore them. Microsoft assessed the campaign was likely aimed at stealing login credentials, but said it has not confirmed that any credentials were captured. Healthcare staff who depend on email for referrals, lab results, and scheduling are a natural target for a message warning that their mail is about to disappear.
Going deeper
The emails used subject lines following the pattern "Outage – [random code]" and sender display names combining a three-character prefix with "Outage Notification" or "Service Health," such as "MSF Outage Notification," according to Microsoft. One referenced a purported Exchange Online incident on November 12 and claimed four messages had been held, with a "RESTORE MESSAGES" button. The messages mentioned Exchange Online, Outlook, Teams, SharePoint, and Copilot, and contained a hidden fake email conversation that Microsoft said appeared to be an attempt to evade mail filters. Each recipient got a personalized tracking link that redirected to a website outside Microsoft's domains. Microsoft found no attachments, QR codes, or malware, and has not attributed the campaign to a named group.
What was said
Microsoft said the campaign "is consistent with historical attacker campaigns which continuously look for notable global events to exploit in their social engineering lures," in its write-up. It reminded users that legitimate Microsoft 365 service-health messages do not send people to non-Microsoft websites to recover held mail, and that service issues should be checked in the Microsoft 365 admin center rather than through email links. For anyone who may have entered credentials, Microsoft recommended resetting the password, revoking active sessions, and checking for new inbox or forwarding rules and unusual sign-ins.
In the know
Microsoft first warned about the campaign publicly on November 14, noting that the messages referenced the real Exchange Online incident number from the outage, Cyber Security News reported. Microsoft's outage updates said there was no indication that malicious activity had caused the underlying service failure. Using a real incident number gave the fake notices a detail recipients could match against what they had already heard about the disruption.
The big picture
Lures tied to real events work because staff have already seen genuine news about them, so defenses can't depend on spotting a false story. The only widely available phishing-resistant authentication is FIDO/WebAuthn, and when a user is tricked into logging in to a fake website, the FIDO protocol blocks the attempt, according to CISA. That protects the account even if a convincing outage notice gets a click. Healthcare organizations can also tell staff ahead of time how real outage updates will reach them, such as through IT or an internal status page, so a "restore your messages" email stands out as wrong whenever it arrives.
FAQs
What did the phishing emails claim?
That messages were held during the Microsoft 365 outage and would be deleted within 24 hours unless the recipient clicked to restore them.
Were credentials stolen?
Microsoft assessed the campaign was likely credential phishing but hasn't confirmed any credentials were captured.
How can staff spot these emails?
Real Microsoft 365 service-health messages don't send users to non-Microsoft websites to recover mail. Subject lines like "Outage – [random code]" were common.
What should someone do if they clicked and entered a password?
Reset the password, revoke active sessions, and have IT check for new forwarding rules and unusual sign-ins.
Why do attackers use real events?
People have already heard about them, so a related message seems plausible and urgent.
