Marketing · 18 November 2026
Microsoft 365 outage used as cover for credential phishing campaign
Attackers used a prolonged Microsoft 365 outage as cover for phishing emails posing as service-health notices. Microsoft says credential phishing is most likely; capture is unconfirmed.
What happened
Cybercriminals used a genuine Microsoft 365 service disruption as cover for a credential phishing campaign. Within a day of a prolonged outage that affected Outlook, Exchange Online, Teams and Copilot, Microsoft Threat Intelligence identified a coordinated, high-volume campaign targeting organisations across several industry sectors, as reported by Computerworld.
The emails imitated Microsoft 365 service-health notifications. They told recipients that messages held during the outage would be permanently deleted within 24 hours unless they were restored, a deadline designed to prompt quick action. Recipients who clicked the embedded links could have exposed their login credentials.
Microsoft's assessment is that the activity was most likely credential phishing. The available evidence, however, does not confirm credential capture, malware delivery or any post-compromise activity, and the reporting notes that multiple threat actors may continue to exploit the disruption.
Why it matters
For organisations that run on cloud productivity platforms, this episode shows that a service incident creates two problems at once. The first is the technical fault itself. The second is the communications vacuum that follows, which attackers can fill with convincing messages that look like official updates. Once people are waiting for news about their email, service-health notifications become a trusted channel that can be imitated.
The campaign also shows how a deadline-based message can override careful checking. Attackers only needed a plausible reason to act and a short window in which to do it. For leaders in digital transformation, the lesson is that cloud resilience now depends on how clearly and verifiably an organisation communicates during disruption, not only on how quickly systems recover.
The Renascence take
Most coverage of this story will focus on the security failure. The more useful question is why a deadline-driven notice about lost email was believable at all. Urgency and loss aversion are well-documented drivers of rushed decisions, and an outage gives attackers both in the same moment. Service teams should treat their incident communications as part of the security perimeter: publish a single, clearly marked status source, tell customers and staff in advance that official notices will never ask them to click through to restore data, and rehearse those messages before the next incident. The operators who handle this best will be the ones who made the legitimate channel so predictable that a fake one stands out.
Sources
This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.
FAQ
Questions we get on this topic
More in Marketing
Stay ahead of CX
Get the signal, not the noise.
The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.


