Free trial The cheapest email marketing platform: try Moosend free for 30 days, no credit card. Don't miss your seat. The cheapest email marketing platform Start free trial →

Fake Microsoft 365 Outage Notices Push Credential Phishing, Microsoft Warns

Microsoft Threat Intelligence says attackers are sending fake Microsoft 365 service health notices that cite the real outage incident EX1550543 and route clicks through SendGrid tracking links.

Alaa Touil
Email infrastructure specialist, 8+ years in SMTP and deliverability
Event Nov 13, 2026 4 min read Nov 16, 2026 0 views
Independent email news, no paywall.Add as preferred sourceBuy us a coffeeRSS
Fake Microsoft 365 Outage Notices Push Credential Phishing, Microsoft Warns (SMTPedia News)

Attackers moved fast after the 12 November Microsoft 365 outage. Microsoft Threat Intelligence says it detected a credential phishing campaign on 13 November that impersonates Microsoft 365 service health notices and cites the real Exchange Online incident number, EX1550543. Some of the messages tell recipients that mail held during the outage will be deleted within 24 hours unless they click a link to restore it.

The same weekend, Microsoft stated publicly that the outage itself was not an attack. In a statement posted on X, the company said: "This was a technical issue not related to cyber or AI / agents." For email teams, the two facts go together: the outage was an accident, and the phishing that followed is deliberate and built to look like routine admin mail.

Key facts

  • Detected: 13 November 2026, by Microsoft Threat Intelligence
  • Lure: fake Microsoft 365 service health notices citing incident EX1550543
  • Pressure tactic: "held" emails supposedly deleted within 24 hours unless the recipient clicks
  • Delivery: recipient-specific SendGrid tracking links that redirect to an attacker-controlled site
  • Targets: organizations across several US sectors
  • Status: Microsoft says its security products are blocking the campaign

What Microsoft found

According to Microsoft Threat Intelligence, the emails pose as service health notifications from Microsoft 365. Subject lines start with "Outage -" followed by a six-character code. The display name combines organization-specific wording with "Outage Notification" or "Service Health", so the message looks like it comes from the recipient's own IT team or tenant.

The links in the messages are recipient-specific SendGrid tracking links. They redirect through SendGrid's click tracking to a separate domain controlled by the attackers. Microsoft lists three sending domains in its post: moments-notice[.]com, planetmaison[.]com and newbooker[.]com, with the redirect landing on reallifeaccounting[.]com.

Microsoft describes the activity as consistent with credential phishing. It has not confirmed that credentials were stolen or that malware was delivered. In a follow-up post, it said Microsoft security products were blocking the campaign.

Why this lure works

The outage gave attackers a believable story. Exchange Online deferred and queued mail for many hours, so users had real reasons to wonder whether messages were missing. A notice that names the genuine incident code and offers to "restore" held mail matches what people expected to hear.

The delivery path matters too. A tracking link from a well-known email service provider points to a domain with a good reputation, and the real destination only appears after the redirect. Filters and users who only look at the first hostname in a link see a familiar sending platform, not the phishing site behind it. Our guide on detecting phishing emails that pass every check covers this pattern in more detail.

Microsoft's own position is simple: service incidents are published in the Microsoft 365 admin center (Service health), and that is where administrators should confirm any incident, not through a link in an email.

What it means for senders

What changes

Attackers are sending fake Microsoft 365 outage notices that cite the real incident EX1550543 and push users to click before "held" mail is deleted. Any message about the outage that asks for a click or a sign-in should be treated as suspect.

Who is affected

Organizations on Microsoft 365, their IT and security teams, and any company that sent its own outage notices to customers or staff, since its real messages now look similar to the phishing. ESPs are affected too: their click tracking was used to hide the final destination.

When

The campaign was detected on 13 November 2026, the day Exchange Online incident EX1550543 was marked resolved. Expect copycat lures for as long as the outage stays in the news.

Action checklist

  • Search your mail logs for subjects starting with "Outage -" and for the three sending domains Microsoft listed, then quarantine matches.
  • Investigate any clicks on those messages, reset the passwords of affected users and review their recent sign-ins and session tokens.
  • Review your Safe Links policies in Microsoft Defender for Office 365 so links are checked at click time, after redirects.
  • Tell users where incidents live: Microsoft 365 service health is in the admin center, and no genuine notice asks users to click to "restore" mail.
  • Make your own notices recognizable if you email customers about an outage: no sign-in links, a consistent From address, aligned SPF, DKIM and DMARC.
  • Enforce DMARC on your domains so attackers cannot send outage notices under your exact name. See our guide to email spoofing.

Sources

  1. Microsoft Threat Intelligence on X: phishing campaign exploiting the Microsoft 365 outage (primary source)
  2. Microsoft Threat Intelligence on X: campaign blocked by Microsoft security products
  3. Microsoft on X: statement that the outage was not a cyberattack
  4. Microsoft 365 Service health status

Get SMTPedia news first on Google

Add us as a preferred source to see our stories in Top Stories and Discover.

Add as preferred source

Useful story?

SMTPedia news is free and independent. A coffee helps us keep covering what changes for senders.

Buy SMTPedia a coffee

Newsletter

Get the next rule change before it bounces your mail