The Microsoft Outage Was A Fire Drill For CIOs
Last week’s Microsoft outage took down Outlook, Teams, Copilot and SharePoint for much of the world. Todd Mazza argues CIOs should treat it as a rehearsal for the next one. He covers testing out-of-band communication channels, backing up M365 data in

“Your employees and leadership team think this event came to an end last week but for you as CIO it is just getting started.”
On Thursday afternoon, Microsoft Outlook stopped working for a large part of the planet, and it stayed broken into Friday morning. It is being reported as the worst outage of the year by far. Other Microsoft products like Teams, Copilot and SharePoint had significant impacts as well. For most of us, the first sign was a help desk queue that tripled in 10 minutes. For some, it may have been a CEO sending a text message, asking, “Why is my e-mail down?”
Your employees and leadership team think this event came to an end last week, but for you as CIO, it is just getting started. Here are five things I think CIO’s need to do right now to get ahead of the next major outage:
Did your out-of-band communication work as planned?
Do you have text messaging, or established-and-trusted locations to provide information when e-mail is not available? Maybe a voice recording as part of your service desk IVR system? One thing we learned last week is the importance of a critical communications plan that can use a diverse set of channels. Organizations that only used Teams and Outlook were unable to coordinate incident response. Maintain out-of-band communication methods like enterprise-grade secondary messaging platforms or SMS notifications systems that have a separate identity provider or cloud dependency from the primary channels. If your organization doesn’t diversify its critical communications plan, people will make up their own information and go to untrusted sources.
Understand that “coming back online” might be rough
On Friday we saw that "coming back online" was not an instant flip of a switch. Restarting servers triggered a massive stampede of queued traffic and reconnecting clients that repeatedly knocked services back offline. Design local retry-logic, backoff strategies, and load-shedding policies in your own internal applications so you don’t accidentally DDoS your own downstream services or vendor APIs when they recover.
Assess your backups of M365 data
Microsoft's native retention protects against deletion, but you may not get access in the event of an extended outage. Consider an independent backup tool for data that may be in your Outlook and OneDrive repositories. Build this in as part of your disaster recovery procedures and make sure you test it.
Secondary email platforms
Now is the time to evaluate secondary e-mail platforms. The cost and complexity rarely justify these types of investments. But for some real-time business lines or companies, the investment may be worth it. If nothing else, present some high-level options and discuss interests, pros and cons with the leadership team before you spend too much time and energy.
Revisit “single point of failure” assumptions
Many enterprises assumed that choosing a tier-1 hyperscaler like Microsoft meant high availability equaled invulnerability, ignoring how interconnected Exchange, Azure gateways, and authentication layers actually are. Audit your dependencies for hidden cascading failures. (For example, check what happens if your identity provider, DNS, or primary email relay has a regional or global degradation).
Moving forward
At a hyperscaler like Microsoft, a single small mistake or technical issue can lead to significant interruption for millions of people around the globe. This will happen again sometime in the next few months. Things are moving at such significant paces that downtime is bound to happen. Microsoft has since restored services to all customers. But this outage was a rehearsal and opportunity to prepare for future outages. You should take advantage of this as an opportunity, instead of waiting for the next one, when it will take advantage of you.
Todd Mazza is the former CTO of Factory Mutual Insurance Company. He’s also held leadership roles at Rockwell Automation, Workday, AECOM, Levi Strauss & Co., MGM Mirage, and NBCUniversal. Contact Todd: LinkedIn | @ToddMazzaCIO on X
If this caught your attention, that’s not accidental.
The best editorial systems don’t happen by accident. Outlever builds them.









