Microsoft 365 Outage Phishing: Fake Notices Cite Real Incident EX1550543, What Is Confirmed and What to Tell Staff This Week
Phishing emails posing as Microsoft 365 outage notices cite the real Exchange Online incident EX1550543. Here is what is confirmed, what is not, and what businesses should tell staff this week.
Where Worldwide
On this page 8 sections
Attackers are sending phishing emails dressed up as Microsoft 365 outage notices. The emails name a real Exchange Online incident, EX1550543, so they look genuine. If your staff spent part of November 12 waiting for their email to come back, a message offering to restore their held mail is exactly the kind of thing they are ready to click.
This post covers what is confirmed about the campaign, what is still unknown, and what a business on Microsoft 365 (many people still call it Office 365 or M365) should do this week.
What happened with the Microsoft 365 outage
Field Effect's write-up says: "On November 12, 2026, Microsoft reported a suite-wide Microsoft 365 service degradation that began at 18:26 UTC." Field Effect describes the cause as an unexpected failure that left several servers unavailable and put extra strain on the rest of the infrastructure.
On its own, that is ordinary. Large cloud services have bad days. It became a security story because of what came next.
The Microsoft 365 phishing campaign that followed
Cyberpress reports that "Microsoft Threat Intelligence has observed an active phishing campaign exploiting the Microsoft 365 service disruption". The emails refer to the legitimate Exchange Online incident EX1550543.
Khaleej Times describes the lure. The emails claim that held messages "will be deleted within 24 hours unless recipients click to restore them".
Together, those pieces make a convincing email. It arrives around the time of a real outage. It cites a real incident number that an IT person may already have seen. And it sets a deadline so nobody stops to check.
What is confirmed and what is not
Our sources are Field Effect's write-up and news reports of Microsoft's findings. We could not cite a Microsoft write-up of the campaign directly, so treat the details below as reported, not as Microsoft's own wording.
| Question | What the sources say |
|---|---|
| Was there a real outage? | Yes. Microsoft reported a suite-wide degradation that began November 12, 2026, at 18:26 UTC |
| Is the phishing campaign real? | Microsoft Threat Intelligence observed it, per Cyberpress |
| Does it use a real incident number? | Yes, it refers to the legitimate Exchange Online incident EX1550543 |
| What does the email say? | That held messages will be deleted within 24 hours unless the recipient clicks to restore them |
| Were passwords stolen? | Not confirmed. The activity is consistent with credential phishing, but neither credential collection nor malware delivery has been confirmed |
| Who is behind it? | Not known. The sources do not name anyone |
| How many businesses were targeted? | Not known |
| Where does the link go? | Not known from our sources |
The short version: a real outage, a real incident number, and a fake email built around both. Nobody has confirmed whether anyone lost a password to it.
Why outage phishing works on businesses
Most phishing has to invent a reason for you to click. Outage phishing does not. The reason is real, and your staff already know about it.
- People are frustrated and want their email back, so a restore button feels helpful rather than suspicious.
- A real incident number makes the email look credible to anyone who recognizes it.
- The 24-hour deadline pushes people to act before they ask anyone.
- The people most likely to fall for it are often the ones trying hardest to help: office managers and IT staff working to get everyone back online.
For a company, one Microsoft 365 password typed into the wrong page can give a stranger the same email and files that person can reach. Nobody has confirmed credential theft in this campaign, but this type of email is built for exactly that.
How to check Microsoft 365 service health the right way
Field Effect puts it plainly: "Microsoft posts outage updates only on the Microsoft 365 admin center Service health page."
That gives you a simple rule for staff. Outage news comes from the Service health page in the admin center. Your admin gets there by signing in the way they always do, not by clicking a link in an email. If an email says your messages are held, about to be deleted or waiting to be restored, that is not how Microsoft tells you about an outage.
If nobody watches that page for you during an outage, fix that too.
What to do this week
| Step | Who | How to check it is done |
|---|---|---|
| Tell staff that Microsoft posts outage updates only on the Service health page in the admin center | Owner or IT lead | A short message sent to everyone that names this campaign and EX1550543 |
| Tell staff that any email offering to restore or release held messages after the outage is suspect | IT lead | Staff know to forward it to IT, not click it |
| Ask who received an email like this and whether anyone clicked | IT lead | A list of names, even if the answer is nobody |
| If anyone clicked and entered a password, change that password now | IT lead | The password is changed and the account's recent sign-in activity is reviewed |
| Make sure whoever checks Service health during an outage signs in directly | Admin | They use a saved bookmark or type the address, never an emailed link |
None of these steps needs a patch or a new product. They are about who your people trust when something breaks.
Microsoft 365 outage phishing questions people are asking
Is the Microsoft 365 outage email real?
The outage was real, and EX1550543 is a real Exchange Online incident. Emails that use it to get you to click and restore held messages are part of a phishing campaign that Microsoft Threat Intelligence observed.
What is Exchange Online incident EX1550543?
The sources call it a legitimate Exchange Online incident. The phishing emails borrow it to look believable.
Did the phishing emails steal passwords?
That has not been confirmed. Reports describe the activity as consistent with credential phishing, but neither credential collection nor malware delivery has been confirmed.
Where does Microsoft post outage updates?
Only on the Service health page in the Microsoft 365 admin center, according to Field Effect. Not through links in emails.
What should I do if someone clicked?
Treat it as a possible password leak. Change that account's password and have whoever runs your IT review its recent sign-in activity.
Who is behind the campaign?
That is not known. None of our sources says who sent the emails or how many organizations received them.
What caused the Microsoft 365 outage?
Field Effect describes an unexpected failure that left several servers unavailable and put extra strain on the rest of the infrastructure.
The bigger lesson
Attackers do not need a new flaw when a real event hands them a reason. The next outage, at Microsoft or any other service your business relies on, will bring its own fake notices. Decide now where your team gets status updates, write it down and make it the only place they look.
Want a second look at how your accounts and email are protected? See security hardening or get a quote.
Get security alerts like this by email, with our free checklist, at /security-alerts.
Sources: Cyberpress; Field Effect; Khaleej Times.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Microsoft 365 Outage Phishing: Fake Held-Mail Emails Used the November 12 Disruption as Bait, What Is Confirmed and How to Check Who Clicked
Phishing emails used the November 12 Microsoft 365 outage as cover, falsely claiming messages held during the...
Fireworks AI Data Breach: Uber Notifies 149,346 People After Hackers Stole Driver License Data From Its AI Vendor, What Is Confirmed and What Businesses Should Check
Uber says hackers stole drivers' names, addresses, dates of birth and license numbers in a breach at vendor Fi...
PostgreSQL Vulnerability CVE-2026-6460: Object Creators Can Run Code on the Database Server, 52 Flaws Fixed, and Why Updating Without Rebuilding Extensions Is Not Enough
PostgreSQL fixed 52 security flaws, including CVE-2026-6460, which lets an account that can create objects run...