Attackers exploited a real Microsoft 365 outage by sending fake service-health emails that appeared to be Microsoft notifications. The messages warned recipients that emails delayed during the outage would be deleted within 24 hours unless they clicked a link, likely to steal credentials.
How the Attack Worked
On November 12, Microsoft experienced a real Microsoft 365 outage affecting Exchange Online, tracked under incident ID EX1550543. Attackers moved quickly to exploit the disruption, sending phishing emails that impersonated Microsoft 365 service-health notifications. The messages warned recipients that emails held during the outage would be deleted within 24 hours unless they clicked a link to restore them, creating urgency around a problem many users were already experiencing firsthand.
Subject lines began with "Outage -" followed by a six-character code, and sender display names combined organization-specific wording with phrases like "Outage Notification" or "Service Health." Microsoft traced the sending infrastructure to three domains: moments-notice[.]com, planetmaison[.]com, and newbooker[.]com, with SendGrid tracking links redirecting recipients to reallifeaccounting[.]com. Microsoft assessed the activity as consistent with credential phishing, though credential collection and malware delivery were not confirmed.
Why It Succeeded
The campaign's strength came from timing and authenticity cues rather than technical sophistication. By referencing the genuine incident ID and mirroring the format of legitimate outage communications, the emails exploited the confusion and anxiety of a real service disruption. Recipients already expecting service updates were more likely to lower their guard, especially when messages appeared tailored to their organization through the display name wording.
What to Watch For
- Urgent deadlines claiming emails or files will be deleted unless a link is clicked immediately.
- Subject lines starting with "Outage -" followed by a short code.
- Sender display names mixing organizational language with terms like "Outage Notification" or "Service Health."
- Messages that reference a real, verifiable incident but arrive from unfamiliar external domains.
How to Build Resistance
Organizations and individuals can reduce exposure to this type of campaign by building habits that do not depend on recognizing any single email:
- Verify outage or service-health claims directly through the Microsoft 365 admin center or another known internal channel instead of clicking links in unsolicited emails.
- Treat any message demanding immediate action to prevent deletion of emails or files as a warning sign, regardless of how legitimate the surrounding details appear.
- Check both the sender domain and the actual destination of embedded links, even when the message cites a real, widely reported incident.
- Encourage employees to report suspicious service notifications so security teams can investigate clicks and review Safe Links policies.
This technique aligns with spearphishing via link (T1566.002) and malicious link execution through user interaction (T1204.001), both of which rely on recipients trusting a seemingly authoritative message during a moment of genuine disruption.
Key findings
- The phishing campaign exploited the November 12 Microsoft 365 outage and used the real Exchange Online incident ID, EX1550543.
- Fake messages impersonated Microsoft 365 service-health notifications and used sender display names containing organization-specific wording plus “Outage Notification” or “Service Health.”
- The emails claimed held messages would be deleted within 24 hours unless recipients used a restoration link.
- Subjects began with “Outage -” followed by a six-character code.
- Microsoft identified moments-notice[.]com, planetmaison[.]com, and newbooker[.]com as sending domains; SendGrid tracking links redirected recipients to reallifeaccounting[.]com.
- Microsoft assessed the activity as consistent with credential phishing, although credential collection and malware delivery were not confirmed.
Who’s being targeted
- Commonly targeted roles: All Microsoft 365 users, Employees who rely on Outlook and Exchange Online, IT help desk, Microsoft 365 administrators, Security operations teams.
- Affected industries: Organizations across several United States sectors, Government agencies, Information technology and cloud-service users.
- Attack channels: email, website.
- Impersonated: Microsoft 365 Service Health / organization-specific IT service notification.
Red flags to watch for
- An urgent 24-hour deletion deadline pressures the recipient to act immediately.
- The notification arrives from an unrelated external domain rather than a verified Microsoft or internal service channel.
- The email asks the recipient to follow a link instead of verifying the incident in the Microsoft 365 admin center.
Frequently asked questions
What made this phishing campaign convincing?
The emails referenced the real Exchange Online incident ID, EX1550543, and the actual November 12 outage, which made fake restoration notices appear legitimate.
What did the phishing emails ask recipients to do?
They claimed emails held during the outage would be deleted within 24 hours unless the recipient clicked a link to restore them.
How can employees verify a real Microsoft 365 outage notice?
Microsoft recommended verifying service incidents directly through the Microsoft 365 admin center rather than clicking links in an unexpected email.
What domains were used to send these phishing emails?
Microsoft identified moments-notice[.]com, planetmaison[.]com, and newbooker[.]com as sending domains, with SendGrid tracking links redirecting to reallifeaccounting[.]com.
Read the video transcript
The Microsoft 365 outage was real. This email about it wasn’t. It cites the real Exchange Online incident, EX1550543. The subject starts ‘Outage -’ plus six characters. Then comes the trap: restore held emails within 24 hours or lose them. A real incident number doesn’t make the link real. The sender could be moments-notice dot com; a SendGrid tracking link could redirect to reallifeaccounting dot com. Don’t use that restoration link. Open the Microsoft 365 admin center yourself and check Service health there.