Strategy
When the Cloud Goes Dark: Practical Lessons from the November Outages.
When a service like Microsoft 365 goes down, the pressure reaches people quickly. Customers still need answers. Employees need direction. Leaders have to make decisions with incomplete information, often while their own communication tools are unavailable.
The Microsoft 365 outage that began on November 12 and the FAA’s nationwide ground stop on November 13 brought that pressure into focus. Different systems, different circumstances, but a familiar challenge for the organizations affected: how do you keep essential work moving while someone else works to restore the service?
Most teams already have full workloads. Finding time to document a workaround or practice operating without email can be difficult to prioritize. During an outage, though, those preparations can give people something valuable: a clear next step.
What These Incidents Remind Us
Microsoft’s preliminary incident report identifies Exchange Online as the most significantly affected service, with users unable to access mailboxes and email delivery delayed. Features in other services, including Teams, SharePoint, and Copilot, were also affected where they depended on Exchange Online; the impact varied, and those platforms were not uniformly unavailable.
The preliminary findings describe a combination of a latent software defect, a shift in traffic, and reduced available server capacity. That explanation may develop as Microsoft completes its review. Microsoft preliminary incident report, hosted by 365Fanatic
The FAA, meanwhile, reported network instability affecting 17 of its 22 Air Route Traffic Control Centers, spreading to additional facilities and prompting a nationwide ground stop. Its account describes routine work that included installing a new router, followed by excessive network connection attempts that destabilized legacy equipment. FAA incident questions and answers
For business leaders, the practical lesson is that routine changes and familiar infrastructure deserve a place in continuity planning. A disruption does not have to begin with a sophisticated attack to create a difficult operating day.
There are also useful examples of organizations putting alternatives into practice. During the Microsoft outage, NHS Essex established a temporary telephone number for urgent referrals from health and care providers. It gave people a specific way to continue an essential activity while email was disrupted. NHS Essex service update
That is what a useful continuity plan should provide: a workable next step.
Start with the Work That Must Continue
Business continuity planning focuses on keeping essential business activities operating through a disruption. Disaster recovery focuses on restoring the systems and data that support them. Both matter, and they need to work together.
Start by identifying the activities your organization cannot leave unattended for long. Depending on the business, those might include:
- Receiving urgent customer requests and assigning someone to respond.
- Accepting orders and confirming delivery commitments.
- Dispatching technicians or coordinating field employees.
- Approving time-sensitive payments.
- Communicating with employees, customers, and suppliers.
For each activity, decide how long it can reasonably wait, who is responsible, and what temporary process is acceptable.
Operating at reduced capacity can be a successful outcome. A team that can handle urgent requests by phone while routine work waits has a useful capability. Define that expectation in advance so employees can focus their effort where it matters most.
Include the people who perform the work every day. They can identify the approval email, shared spreadsheet, or individual contact that a process quietly depends on.
Give People Usable Options
A continuity plan earns its value when people can find it, understand it, and act on it under pressure.
If the only copy lives in SharePoint, consider how employees will reach it when SharePoint or their usual sign-in process is unavailable. Keep current copies of essential instructions and contact information in accessible locations, with appropriate protection for sensitive information.
Be equally specific about communication. Identify how the response team will connect, how employees will receive instructions, and where customers can find updates. Make sure people know these arrangements before they need them.
The same scrutiny should apply to technical alternatives. Ask your technology team or provider to explain which failure each option is designed to address:
- A backup internet connection may help when the primary connection fails. What is the plan when the application itself is unavailable?
- A secondary email environment needs a clear purpose. Does it depend on the same infrastructure or sign-in service?
- Emergency access procedures need to account for what happens when the usual identity service is unavailable.
- Data recovery arrangements should establish what can be restored, where it can be used, and how long that will take.
Match the investment to the activities you need to protect and the interruption your organization can tolerate. Some workflows may justify additional technology. Others may need an approved phone process, an offline record, or clearer instructions.
Make Decision Authority Clear
Even a capable team can lose time when everyone is waiting for someone else to act.
Decide who can activate the continuity plan, authorize a temporary process, and communicate changes. Name an alternate for each key role. Establish when the team should move to a workaround and when it should reassess.
Employees also need boundaries. What information can they share through an alternate channel? Which approvals still apply? Where should they record work completed outside the usual system?
Making those decisions ahead of time gives people room to respond while protecting the business from avoidable confusion.
Practice One Realistic Scenario
An untested plan is a document, not a capability.
A useful exercise can begin with a straightforward scenario: Microsoft 365 becomes unavailable at 9 a.m., and your team is planning to operate without it through the following business day.
Bring together the people who handle customer requests, coordinate operations, approve decisions, and support technology. Walk through the work:
- How does an urgent request reach the right person?
- How do employees receive assignments and report progress?
- Where are contact lists and essential instructions?
- Who approves an exception?
- How are customers updated?
- Where is completed work recorded?
Pay attention to the points where someone says, “I would just email…” or “That information is in Teams.” Those moments reveal dependencies worth addressing.
Keep the exercise constructive. Gaps are useful findings, and employees need to feel comfortable identifying them. Assign someone to address each significant gap, set a completion date, and try the affected process again.
Alongside these discussions, ask the technology team to demonstrate that relevant access, failover, and restore procedures work under the conditions the plan assumes.
Plan for the Work After Service Returns
Restoring a service begins another phase of recovery.
Your team may still have delayed messages, unprocessed orders, missed approvals, and work recorded outside the normal system. Decide how that backlog will be reviewed and prioritized.
Confirm that urgent requests reached the right people. Reconcile manual records. Check for duplicate entries or payments. Tell employees when to return to normal processes, and let customers know where delays remain.
Give the team time to work through this stage. Expecting everyone to resume normal output immediately can overlook the effort required to make the business current again.
Give Your Team a Clearer Next Step
You cannot control when a major provider experiences a failure. You can decide which activities take priority, give employees workable alternatives, and practice the decisions they may need to make.
Start with one scenario and the operations you are most concerned about keeping available. Record where the process breaks down, assign responsibility for closing those gaps, and revisit the plan as your business changes.
Your team may still face a difficult day when the next outage happens. Preparation gives them clearer choices, fewer avoidable obstacles, and more confidence in how to respond.
If it would help to work through that conversation with your team, reach out. We can start with the activities your organization needs to keep moving and build from there.