Back to Newsroom

Threat intel5 min read

Fake Microsoft 365 outage alerts used real incident ID to phish staff

A day after the 12 November Exchange Online outage, phishing emails posing as Microsoft 365 service-health notices quoted incident EX1550543 and threatened to delete held mail within 24 hours.

4Tify Team

Phishing emails dressed up as Microsoft 365 service-health notices started landing in corporate inboxes on 13 November 2026, one day after a real outage knocked Exchange Online offline for close to a full day. The messages quoted the genuine incident number, EX1550543, and told recipients that held mail would be deleted within 24 hours unless they clicked to restore it.

What happened

Exchange Online began failing on the afternoon of 12 November 2026 (UTC). Microsoft tracked the mail problem as EX1550543 and opened a second incident, MO1550821, for the knock-on effects in Teams, SharePoint, Outlook and Copilot. Its preliminary review points to a failure in the networking gateway that fronts many Microsoft 365 services, and the company said there was no sign of malicious activity behind the outage.

The next day, Microsoft's threat intelligence team spotted a coordinated, high-volume phishing run aimed at organisations in several sectors worldwide. Microsoft published its analysis on 16 November.

What the emails looked like

  • Subject lines followed the pattern Outage - <random token>, for example Outage - aF7vG6. Other variants used "Strengthen - Security" or "Restore - 4 messages" followed by a random string.
  • Display names paired a three-letter, company-style prefix with "Outage Notification" or "Service Health", such as "MSF Outage Notification" or "AMZ Service Health".
  • The body described an Exchange Online incident on 12 November, claimed four messages were held, and offered a bright "RESTORE MESSAGES" button. A second version warned of "1 security issue" with a "TAKE ACTION" button.
  • Hidden text: the emails carried a fake conversation thread that the reader never sees, which Microsoft reads as an attempt to slip past mail filters.

Mail went out from three sender domains: moments-notice[.]com, planetmaison[.]com and newbooker[.]com. Every link was a recipient-specific click-tracking URL from a commercial email-delivery service (SendGrid), so no two victims got the same link. The clicks ended up at reallifeaccounting[.]com/themelist0.html, and in some samples at outagefixed[.]sbs or outagerestored[.]sbs. A tracking pixel served from 162[.]120[.]17[.]69 on port 8080 recorded who opened the message.

How bad is it

Microsoft assesses the campaign as likely credential phishing. It found no attachments, QR codes or malware. It also says its evidence does not show credentials being captured or any account being taken over, and it has not tied the activity to a named group. Defender blocks the domains involved, and Defender for Office 365 quarantines the emails.

The lure works because the timing is right. Staff who had just lived through a day of missing mail had every reason to believe some messages were stuck, and a 24-hour deadline leaves little room to stop and ask IT.

What to do now

  1. Search and purge. Hunt mail logs for the three sender domains, the Outage - subject pattern, the "messages held after the outage" wording and the destination domains above. Remove delivered copies.
  2. Find who clicked. Check click telemetry and proxy logs for reallifeaccounting[.]com and the two .sbs domains. A click alone does not mean a compromise, but it tells you where to look.
  3. Treat any entered password as stolen. Reset it, revoke active sessions and refresh tokens, and check MFA registrations, new inbox or forwarding rules, OAuth consents and delegate permissions.
  4. Block with care. Block the destination domains, but don't block the whole email-delivery service; legitimate mail uses it too.
  5. Teach one rule. Real Microsoft 365 notices never send users to an outside site to recover mail. Service status lives in the admin center, as described in Microsoft's service health guide.
  6. Harden sign-in. Move to phishing-resistant MFA such as passkeys or security keys where you can. CISA's fact sheet explains why one-time codes and push prompts can still be phished.

The full indicator list and Defender hunting queries are in Microsoft's analysis of the campaign.

Credentials taken this way tend to resurface later in criminal markets and combo lists. Our Deep/Dark Web monitoring watches those places for your company's domains and accounts, so a password typed into a fake page can be caught and reset before someone tries it.

NEWSLETTER

The week’s news,
every Friday.

A short email with what we published that week. You can unsubscribe from any of them.

FRIDAY DIGEST · SAMPLE4TIFY NEWSROOM

This week in security

  • 01Attackers exploit critical Cisco Expressway flaw to gain root on clustered nodes
  • 02SonicWall ends Gen 6 firewall patches, even for critical flaws
  • 03WhatsApp fixes three flaws, one possibly used to back up scam messages

+ 6 MORE IN THIS ISSUE · UNSUBSCRIBE IN ONE CLICK

ONE OFFER

More than one product?
Get one offer.

Tell us what you need to protect and your budget, monthly or yearly. We combine the products into one offer and one contract, sized to that budget, and we stay with you after it is signed.

Ask for an offer Just tell us how many assets you have and what you want to spend.
Fake Microsoft 365 outage alerts phish with EX1550543 | 4Tify