

On November 14, 2026, Microsoft Threat Intelligence reported a high-volume phishing campaign exploiting the Microsoft 365 service disruption that began on November 12. Although Microsoft found no evidence that the Exchange Online and Microsoft 365 outage was caused by malicious activity, threat actors quickly leveraged the incident, sending fake outage and recovery notifications designed to harvest credentials.
What is the threat?
The phishing emails impersonate Microsoft 365 service health notifications and cite the genuine Exchange Online incident ID EX1550543. Subject lines follow the pattern “Outage – [six-character code],” while sender display names mimic official notifications, often using organization-specific prefixes. The messages claim that emails held during the outage will be deleted within 24 hours unless recipients click a “Restore Messages” button, directing them to a suspicious site in an apparent credential-phishing attempt.
Related outage-themed social engineering can also take forms such as fake password resets, account-deactivation notices, SMS payment-redirection scams, and fake IT support calls designed to convince users to disclose information or provide remote access.
Why is it noteworthy?
This campaign uses a real incident and authentic details to create a convincing outage-themed lure. The 24-hour deletion warning adds urgency, increasing the likelihood that recipients will act without properly verifying the message. More broadly, the campaign demonstrates how attackers can exploit legitimate service disruptions as cover for social engineering.
What is the exposure or risk?
Organizations using Microsoft 365 may be exposed, particularly those whose users were affected by the outage. A successful credential compromise can lead to account takeover, business email compromise, internal phishing from trusted accounts, payment redirection, and data exfiltration.
Compromised accounts can also be modified to maintain access through malicious inbox rules, mail forwarding, unauthorized OAuth application consent, or newly registered authentication methods. Organizations without phishing-resistant MFA or with insufficient controls around external communications and remote support tools may face increased risk.
What are the recommendations?
Barracuda recommends the following steps to reduce exploitation risk:
- Verify through official channels only. Instruct users to confirm service status through the Microsoft 365 admin center Service health page rather than links in unsolicited emails.
- Hunt and purge malicious messages. Use Defender for Office 365 Threat Explorer, Defender XDR advanced hunting, and message trace to identify outage-themed emails, including “Outage –” subject lines and references to EX1550543. Purge malicious messages and block associated senders, domains, and URLs.
- Review email protection policies. Verify that Safe Links, Safe Attachments, and anti-phishing and impersonation policies are enabled and appropriately applied.
- Investigate and remediate affected accounts. Review Entra ID sign-in and Purview audit logs for suspicious activity. Remove unauthorized inbox rules, forwarding, OAuth consents, or authentication methods, then reset affected passwords and revoke active sessions and tokens.
- Strengthen authentication. Use phishing-resistant MFA and Conditional Access to prevent credential and MFA-code theft.
- Reduce social engineering opportunities and educate users. Restrict external Teams access, verify sensitive changes, and train users to spot phishing.
References
For more information, review the following resources:
- Microsoft finds active phishing campaign exploiting service disruption – Khaleej Times (Nov 14, 2026)
- Phishers quick to exploit extended M365 outage – iTnews
- Microsoft 365 outage theme drives credential phishing and support scams – Field Effect (Nov 13, 2026)
- Microsoft Warns of High-Volume Phishing Attack Exploiting Microsoft 365 Service Disruption
If you have any questions about this Cybersecurity Threat Advisory, don’t hesitate to get in touch with Barracuda Managed XDR’s Security Operations Center.
This post originally appeared on Smarter MSP.

