Blog

Oran Moyal
|
|
Reading Time:
6
min

On November 12, 2026, a Microsoft 365 outage cut organizations off from their Exchange Online mailboxes, and delayed mail was still arriving the next day. Service is back, and Microsoft says it was not a cyberattack. The security risk outlasts the outage: outages hand attackers a believable pretext, and the backlog pushes employees to move fast and miss warning signs.
What happened during the Microsoft 365 outage?
Starting late morning Eastern time on November 12, users could not reach Exchange Online mailboxes from Outlook on the web, desktop or mobile, and mail delivery was delayed. Microsoft tracked the incident as EX1550543 and MO1550821, and the impact later spread to Teams, SharePoint Online, Defender XDR and other Microsoft 365 services, according to SecurityWeek. Downdetector logged more than 131,000 Outlook reports at the peak, per TechRadar.
Microsoft said it had "no evidence of malicious activity." On November 13, it attributed the incident to an issue introduced during an earlier network capacity upgrade. Microsoft extended its email timeout window to 48 hours so delayed messages would still arrive, and on the afternoon of November 13 it was "still draining queued messages." Service has since been restored. A full post-incident report is pending.
Productivity Moves at the Speed of Communication
Business runs at the speed of communication, and email is where most of that communication happens. Invoices, approvals, contracts, vendor coordination and customer commitments all move through the inbox.
Email also connects a company to everyone outside it. Customers, suppliers, partners, lawyers, auditors and banks all reach the business through the same channel, and most of them share no chat workspace to fall back on. Email is the record of what was agreed, too. When a deal, a payment or a contract is disputed, the thread is the evidence.
That makes email the dependency under every revenue, finance and customer process. When it slows down, deals stall, payments wait, support queues grow and decisions get pushed to tomorrow. Few companies track that cost as an email problem, but every team feels it.
On Wednesday, many teams could still open their CRM and their file shares, but they could not confirm a payment, answer a customer or approve a vendor. So people improvised. They forwarded work to personal accounts, moved threads to WhatsApp and texted links to files. Each workaround kept the business moving, and each one moved sensitive work outside the channels security teams protect and monitor.
Outages are the visible version of a problem that happens quietly every day. When employees second-guess every invoice, wait on IT to release quarantined mail or call a vendor to confirm a bank change, communication slows down the same way it does in an outage. Lost trust in email costs the business time, just like downtime does.
That is why availability and security belong in the same conversation. Communication has to keep flowing, and every message in it has to be trustworthy. At Ocean, our mission is to secure the most vital driver of business, communication, so it can flow freely and people can work fast, without fear.
Why are outages perfect timing for attackers?
Outages create two attack windows: the confusion during the disruption and the rush after it. Attackers watch status pages as closely as administrators do, and they plan for both.
During the outage, impersonation gets easier. Employees expect to hear from Microsoft or internal IT, so a message or call asking them to "restore access," "re-verify" their mailbox or approve an MFA prompt sounds routine. To an attacker, a real outage is a ready-made pretext with global credibility. Users who would normally spot a fake login page assume the request is part of the recovery. Outage-themed lures need no technical skill. They only need good timing.
After the outage, the backlog trap opens. The backlog trap is the period after an email outage when queued messages arrive all at once and employees, rushing to catch up, overlook warning signs they would normally catch. Deadlines have already slipped. Vendors are asking about payment status, and customers want to know why a deliverable is late. In that rush, a spoofed vendor invoice, an altered wire routing number or a lookalike domain gets through because someone was trying to clear their inbox. A delay also stops looking strange. On a normal day, a "time-sensitive" invoice that arrives hours late might raise a question. After an outage, every message is late, so a fraudulent payment request blends into a pile of real ones.
Example of a related phishing attempt we caught just this week here:

What should organizations do after an email outage?
Organizations should treat the days after an email outage as a period of elevated risk and act on five things:
Give people one place to look. During a disruption, employees are trying to keep work moving and want answers fast. Tell them exactly where to expect IT updates, and remind them that Microsoft will not ask them to log in from a link in an email. One clear source of truth means fewer guesses under pressure.
Make it easy to verify IT contact. When people are stressed and waiting for access to come back, a call from "IT" or a surprise MFA prompt can feel like help arriving. Give employees a known number or ticketing path to confirm the request, and make clear that checking first is always the right call.
Give people permission to slow down. The backlog puts real pressure on people to catch up, and urgency is when warning signs get missed. Tell teams that taking a few extra minutes to double-check is expected. Payment changes, new bank details and login requests get a second check through a separate channel, such as a callback to a number already on file, even when the sender says it cannot wait.
Bring work back from shadow channels. Find out which approvals, files and conversations moved to personal email or messaging apps, and bring them back into managed systems.
Add email outages to your continuity plan. Decide in advance how teams will communicate, approve payments and reach customers when email is unavailable.
Recovery is the riskiest part of an outage
Most continuity planning ends when mail starts flowing again. Recovery is complete only when communication is flowing safely, and the hours in between are where exposure peaks. A person cannot carefully verify 400 messages that arrive in the same hour. That volume is exactly what investigation at scale is built for.
Ocean investigates every email before a compromise happens. Its AI agents validate the sender, read the intent of the request and follow the links and attachments the way an analyst would, at machine speed. When the backlog lands, that work happens on every message, so employees can catch up without carrying the burden of verification.
Outages will happen again, to every provider. The organizations that come through them cleanly will be the ones that treat email as the business infrastructure it is.
As always, if there's anything we can do to support your team, we're here to help.
Frequently asked questions
Was the November 12, 2026 Microsoft 365 outage a cyberattack?
No. Microsoft said it had no evidence of malicious activity and later described the November 12, 2026 Microsoft 365 outage as a technical issue. On November 13, Microsoft attributed it to an issue introduced during an earlier network capacity upgrade. A full post-incident report was still pending at the time of writing.
Were emails lost during the Microsoft 365 outage?
Microsoft reported that mail was delayed and queued during the Microsoft 365 outage. It extended its email timeout window to 48 hours so that delayed messages would still be delivered, and queued messages were delivered as service recovered. Mail that arrived late from the outage window deserves extra care.
How do attackers exploit email outages?
Attackers exploit email outages in two ways. During the disruption, they impersonate Microsoft or internal IT with calls or messages asking users to restore access, re-verify a mailbox or approve an MFA prompt. After recovery, they hide fraudulent invoices and credential requests in the backlog, when employees are rushing and delays look normal.
What should employees do after an email outage?
After an email outage, employees should slow down on anything urgent, financial or credential-related, even when the backlog is large. They should confirm unexpected requests from IT or vendors through a known phone number or internal channel, and never log in from a link that claims to restore their mailbox.
About Ocean: Ocean is the agentic email security platform. Where traditional tools scan the surface, Ocean goes deep, deploying purpose-built AI agents to investigate every email and stop today's AI-powered targeted attacks at machine speed. With Ocean, organizations automate SOC triage and guide employees in real time, so they can work fast, without fear.