Email stopped being “just email” a long time ago. It carries invoices, password resets, approvals, and the sign-in checks that open other services. So when Microsoft 365 service was disrupted for roughly 24 hours, organizations felt the impact right away.
During this downtime, the 90,000+ customers who rely on Check Point WorkSpace email security to protect their mailboxes turned to us for support. Here is what we saw, what we did to keep their email safe and flowing, and what we’re improving.
What our customers needed
When messages couldn’t be delivered to mailboxes, we held them safely until delivery could resume. Our team worked around the clock, across every time zone, to ensure that no email would be lost and that no email would be delivered unless it had been cleared as safe by our security layers. As a result, not a single email was lost, and every email was scanned for threats before reaching end users
Adversity is where resilience proves itself
A disruption of this scale puts every part of the cloud ecosystem under pressure. Our protections continued to operate as designed, while the event reinforced two important learnings about continuing to build resilience in an increasingly interconnected world.
- First, outages can have effects far beyond the affected platform. Delays extended into the broader email ecosystem, including mail destined for Gmail users, as queues increased and delivery slowed. The takeaway is simple: organizations cannot assume that a disruption affecting one cloud provider will remain isolated to that environment.
- Second, resilience requires the ability to absorb unexpected demand. As queues grew, our platform continued protecting messages while our DevOps team proactively scaled capacity to accommodate the exceptional volume. We’re building on that resilience with additional automation and dynamic capacity management, further reducing the operational intervention required during extreme events.
Attackers follow outages
Disruption creates confusion, and criminals use it. After outages like this, we expect fake support messages, bogus “recovery” links, help-desk impersonation, and payment fraud. Under pressure to keep people working, teams may also be tempted to loosen security controls. That is exactly the moment attackers hope for.
What to do now
- Keep multi-factor authentication and other controls on. Log any emergency changes, and reverse them once service returns
- Verify every password reset, access request, or payment-change request through a second channel
- Give staff an approved backup way to communicate, so they don’t turn to personal email or apps
- Tell staff never to sign in through a link in a “recovery” message
- Once service is back, review sign-ins and admin changes made during the outage
The bigger picture
This is not the first outtage this year. Undersea cable cuts, the PHP2Shell vulnerability, and a major AWS outage all showed the same thing: too many organizations depend on the same few providers, for email and for the identity checks that open everything else.
Resilience is an ongoing engineering journey of adding redundancy to critical components and analyzing each component’s behavior when other parts of the system fail. This Microsoft 365 outage gave us a rare opportunity to test the system in such rare circumstances.
Join us tomorrow for a live webinar on the recent outage. We’ll walk through what happened, what we learned, and what we’re changing to prevent it from happening again. Register now












