Five practical steps to keep your organization running if this happens again
For millions of organizations including our own, Microsoft 365 is the backbone of everyday operations. Email, meetings, calendars, file sharing, and collaboration all depend on it. So when Microsoft experienced a massive global outage last week, the disruption went far beyond a few missed emails. It brought our own small company nearly to a grinding halt. After waiting several hours with no fixes, urgent emails had to be sent from our personal accounts; our personal phone numbers and WhatsApp accounts had to be shared with customers.
For nonprofits, foundations, and smaller organizations with limited IT resources, the incident raised an uncomfortable question: What happens when the technology you depend on suddenly becomes unavailable—and there’s nothing your IT team can do to fix it? Do you have a plan?
What Happened Last Week?
On Thursday, November 12, a widespread Microsoft 365 outage disrupted Outlook, Exchange Online, Teams, Copilot, and other connected services. Users around the world struggled to access email, send messages, manage calendars, and use certain collaboration tools. The disruption lasted nearly 24 hours, with Microsoft confirming that the primary incident had ended on Friday, November 13.
Microsoft’s preliminary investigation identified a software defect introduced months earlier, combined with increased network traffic and reduced server capacity. The resulting chain reaction overwhelmed servers across its infrastructure.
Importantly, Microsoft said the outage was not caused by a cyberattack or AI-related activity. It was an internal technical failure—one that affected organizations regardless of how well they maintained their own systems.
Why Nonprofits and Foundations Are Especially Vulnerable
For a large corporation, a day without email is disruptive. For a small nonprofit operating with a staff of 15 or 20 people, it can bring essential work to a standstill.
Consider a foundation preparing to approve time-sensitive grants. Staff may be unable to communicate with applicants, access meeting invitations, or coordinate decisions. A nonprofit running a fundraising campaign could miss donor inquiries or struggle to coordinate with volunteers and community partners.
And unlike larger enterprises, smaller organizations rarely have dedicated business continuity teams or sophisticated backup communication systems.
When nearly everyone relies on the same platform, a single outage can affect the entire organization simultaneously. Even worse, staff may have no clear instructions about what to do while they wait for services to return.
The Hidden Risk of Putting Everything in One Basket
Microsoft 365’s biggest advantage is also a potential weakness: integration. Outlook connects with Teams. Teams connects with SharePoint and OneDrive. Copilot draws information from across the Microsoft environment. These connections make everyday work easier, but they also create dependencies.
Last week’s outage demonstrated how problems with one underlying service can ripple across multiple applications. Although some tools remained accessible, features dependent on Exchange Online were affected.
This doesn’t mean nonprofits should abandon Microsoft 365. Its affordability, nonprofit licensing benefits, security features, and productivity tools still make it an excellent choice for many organizations.
But it does mean organizations should recognize the risks of relying entirely on one provider—and prepare accordingly.
An Outage Can Create a Security Problem, Too
Unfortunately, service disruptions can also create opportunities for cybercriminals.
Following last week’s outage, Microsoft warned of phishing emails impersonating official Microsoft 365 service notifications. Some messages falsely claimed that delayed emails would be deleted unless users clicked a link to restore them. It’s an effective tactic because employees are already frustrated, confused, and eager to get back to work.
For nonprofits and other small companies with limited cybersecurity resources, these situations can be especially dangerous. A staff member who would normally recognize a suspicious email might be more inclined to click when it appears to offer an immediate solution.
The lesson? Outage preparedness and cybersecurity awareness go hand in hand. Staff should know where to find legitimate Microsoft service updates and understand that unexpected recovery links deserve extra scrutiny.
Five Steps Small Organizations Should Take Now
You can’t prevent Microsoft from experiencing another outage. But you can significantly reduce its impact on your organization.
- Create an alternative communication plan. Establish a way to reach staff when Outlook and Teams aren’t working, such as phone calls, text messages, or an independent messaging platform.
- Keep essential contact information accessible offline. Maintain secure, up-to-date contact lists for employees, board members, vendors, and critical partners.
- Identify your most critical operations. Determine which activities—grant approvals, donor communications, financial transactions, or service delivery—cannot wait until systems are restored.
- Review backup and recovery capabilities. Microsoft 365 backups help protect against data loss, but they don’t necessarily provide access to email or applications during a service outage. Know the difference.
- Practice your response. Even a brief tabletop exercise can reveal gaps in your organization’s ability to operate without its usual technology.
Your IT Provider Can’t Fix Microsoft, But They Can Help You Prepare
One frustrating aspect of last week’s outage was that even the most capable IT professionals couldn’t simply restore Microsoft’s services themselves. However, a good IT partner can make a significant difference before, during, and after an incident.
They can monitor service health, communicate reliable updates, help staff distinguish widespread outages from local problems, and establish alternative workflows. They can also review your organization’s dependencies and develop practical continuity plans that fit your budget.
For smaller nonprofits, this doesn’t necessarily require an expensive, enterprise-level disaster recovery program. Sometimes the most effective solutions are surprisingly simple.
The Bigger Lesson: Resilience Matters More Than Ever
Microsoft eventually restored its services, and organizations returned to business as usual. But the outage exposed something worth remembering: Even the world’s largest technology providers aren’t immune to failure.
For nonprofits and foundations, technology disruptions aren’t just an inconvenience. They can delay funding, interrupt programs, strain relationships, and interfere with the missions these organizations exist to serve.
The goal isn’t to eliminate every possible technology risk. That’s impossible. It’s to make sure your organization can continue functioning when something goes wrong.
At CGNET, we help nonprofits and foundations build practical, affordable IT strategies that include security, backup, and business continuity planning. If last week’s outage left your organization scrambling, now is a good time to talk about how to be better prepared for the next one.




0 Comments