Cybersecurity protects your systems. Cybersecurity risk management protects your business.®

The Information Highway

The Information Highway

Font size: + –
5 minutes reading time (993 words)

Cybersecurity Threat Advisory: Fake Microsoft 365 Outage Emails Are Stealing Logins

Threat update

Microsoft 365 had a real service disruption that began on November 12, 2026, and attackers wasted no time turning it into bait. On November 14, Microsoft Threat Intelligence reported a high-volume phishing campaign sending fake outage and "message recovery" notices designed to steal Microsoft 365 passwords. Microsoft says it found no evidence the outage itself was caused by an attack, but that doesn't matter to the criminals. Your users just lived through a real outage, so an email saying "your held messages will be deleted unless you act now" sounds believable. If your organization uses Microsoft 365, now is the time to warn your team and check your mailboxes.

Technical Detail and Additional Info

What is the threat?

The phishing emails pose as official Microsoft 365 service health notifications. They're convincing because they borrow details from the real incident. Here's what to look for:

  • A real incident number: The emails reference the genuine Exchange Online incident ID EX1550543, which makes them look legitimate at a glance.
  • A predictable subject line: Subjects follow the pattern Outage – followed by a six-character code.
  • Look-alike senders: Display names imitate official Microsoft notices and often include your organization's name or a prefix to look internal.
  • A deadline and a button: The message claims emails held during the outage will be deleted within 24 hours unless you click Restore Messages. That button leads to a fake sign-in page that captures your username and password.

The fake email isn't the only trick. Attackers are also using the outage as cover for:

  • Fake password reset requests
  • Bogus "your account will be deactivated" notices
  • Text messages asking to change where payments are sent
  • Phone calls from fake "IT support" asking users to share information or allow remote access to their computer

Why is it noteworthy?

Attackers love a real event. When something is actually broken, people expect to get notices about it, they're frustrated, and they want their email back. That's the perfect moment to slip in a fake "fix." Using a genuine Microsoft incident number removes one of the easiest red flags your users have been taught to look for.

The stakes are also bigger than one stolen password. Microsoft 365 is usually the key to everything else: email, Teams, OneDrive, SharePoint, and often the single sign-on for your other business apps. Once an attacker is in one mailbox, they can send phishing emails to your coworkers, clients, and vendors from an address everyone already trusts. 

What is the exposure or risk?

Organizations face the most risk when:

  • Users were affected by the Microsoft 365 outage and are expecting follow-up notices
  • Accounts are protected only by a password, or by MFA that can be phished (text codes, phone calls, or push approvals)
  • No Conditional Access policies limit where and how users can sign in
  • Anyone outside the company can message employees in Teams
  • Staff can approve payment or banking changes without a call-back check
  • Remote support tools can be installed without IT knowing

If an attacker gets a user's credentials, they could:

  • Take over the mailbox and read, send, or delete email
  • Launch business email compromise (BEC) scams, such as fake invoices or payment redirection
  • Send phishing emails internally and to clients from a trusted account
  • Steal sensitive files from OneDrive, SharePoint, and email
  • Stay hidden and keep access by creating inbox rules, auto-forwarding mail outside the company, approving malicious app permissions (OAuth consent), or registering their own MFA method

That last point is important: changing the password alone may not lock an attacker out. Those hidden changes have to be found and removed too.

What are the recommendations?

 LBT Technology Group recommends the following actions:

  • Tell your users now. Send a short heads-up: Microsoft will never ask you to click a link to "restore" messages. To check whether Microsoft 365 is having a problem, admins should use the Service health page in the Microsoft 365 admin center, and users should ask IT. Never follow a link in an unexpected email.
  • Find and remove the emails. Use Defender for Office 365 Threat Explorer, Defender XDR advanced hunting, or message trace to search for subject lines starting with Outage – and emails mentioning EX1550543. Purge them from mailboxes and block the sending addresses, domains, and URLs.
  • Check your email protection settings. Make sure Safe Links, Safe Attachments, and anti-phishing and impersonation protection are turned on and applied to all users, not just a pilot group.
  • Look for signs of compromise. Review Entra ID sign-in logs and Purview audit logs for unusual sign-ins. Check for new inbox rules, external mail forwarding, unexpected app consents, and newly added MFA methods. Remove anything unauthorized, then reset the affected passwords and revoke all active sessions and tokens.
  • Upgrade your MFA. Move to phishing-resistant MFA (such as passkeys, FIDO2 security keys, or Windows Hello for Business) and use Conditional Access policies so a stolen password or MFA code alone isn't enough to get in.
  • Close the side doors. Restrict external access in Teams, require a call-back to a known number before any payment or banking change, and lock down who can install remote support tools.
  • Keep training going. Short, regular phishing awareness training and simulated phishing tests help users recognize "urgent" messages like this one, especially when they arrive during a real outage.

Not sure whether anyone in your organization clicked, or whether your Microsoft 365 security settings would stop an attack like this? Contact LBT Technology Group for a no-pressure review of your Microsoft 365 and email security. 

References

 For more in-depth information about the recommendations, please visit the following links:

The Payment That Never Arrived: Tax Season, AI Phi...

Top Breaches Cost ($) of 2024

HEALTHCARE
FINANCIAL
INDUSTRIAL
TECHNOLOGY
ENERGY
Source: IBM Cost of a Data Breach Report 2024