A cloud provider's restoration clock is not a business continuity plan. When a platform is unavailable, the operational question is what the business can decide, communicate and deliver before that clock stops.

The November 2026 Microsoft 365 disruption brought that distinction into focus. Microsoft reported services restored on November 14 after an incident affecting multiple regions. The detailed post-incident report was not publicly available in the research reviewed for this article, so the incident does not establish which specific corrective actions would have prevented it. It does provide a useful reason to examine how businesses prepare for a provider outage.

Our view is that an IT partner should be judged on its ability to help a business prepare for and manage disruption, not on a promise to restore a platform it does not control. That is a demanding standard: it requires clear ownership, credible alternatives and communication that works when familiar tools do not.

Business impact starts with a decision, not a system

A Microsoft 365 outage can interrupt email, collaboration and access to information. The operational effect depends on what people need those tools to do. A delayed internal update may be manageable; an unanswered urgent customer request or an inaccessible approval may have a more immediate consequence.

A useful continuity discussion therefore begins with the business activity. Which commitments cannot wait? Who can decide what takes priority? What information and people does that decision require? The answers should shape the technology response, rather than the other way around.

The Canadian Centre for Cyber Security's IT recovery planning guidance connects critical functions and disruption tolerance with recovery responsibilities. That framework matters in a provider outage because the order in which a business needs to resume work may not match the order in which individual services become available.

Consider a company that needs to respond to urgent customer calls while routine correspondence can wait. Its immediate requirement may be a reliable way to reach the people handling those calls and give them enough information to respond. That is a different priority from restoring every employee's normal workflow at once.

A provider restores the platform. A business still has to lead.

Microsoft is responsible for restoring its service. The business retains authority over its customers, staff and operating priorities. Between those responsibilities, an IT partner can provide valuable coordination, subject to the agreement and available access.

A partner may be able to distinguish a known provider incident from a separate local issue, interpret updates, explain the consequences for affected systems and help coordinate agreed alternatives. The business decides which work takes precedence, who can approve a temporary process and what stakeholders need to hear.

The difference is consequential. A provider update saying that service is recovering does not tell a manager whether a particular team can safely resume its work. Someone must assess the actual business process, communicate the decision and account for work handled through an alternative route.

Business continuity planning should make those responsibilities explicit before an incident. A support agreement can define what the partner will do, how it will communicate and which activities require the client's decision. It should also make clear where technical access, scope or response-time limits apply. Confidence comes from understanding those boundaries, not from assuming they disappear during an outage.

The communication plan must survive the channel it replaces

A team cannot coordinate through an unavailable channel. A separate messaging service, phone tree or other agreed route can provide a way to reach people, provided it does not depend on the same affected service and is appropriate for the information being shared.

The route needs an owner and a purpose. Staff should know who provides updates, where decisions are recorded and how to reach the people authorised to act. Contact information must remain accessible to authorised people and protected appropriately. Updates should distinguish confirmed information from uncertainty, including when no restoration time is known.

Microsoft directs authorised administrators to Service health for information relevant to their organisation, with its public status page serving as a backup when the admin centre or Service health is inaccessible. Those updates inform the response; the business still needs its own route for communicating what its people should do.

A workaround is an operating choice

An alternative should earn its place by supporting a specific priority. An offline document may let a team complete a limited task, but it can be outdated or create conflicting versions. A separate communications tool may reach staff while creating privacy or recordkeeping concerns. In some cases, waiting is the responsible choice.

This is where a partner's technical advice and a leader's business judgement need to meet. Together they can determine which alternatives are workable, who may activate them, what information is required and how the business will reconcile decisions and transactions once normal services return.

Test the agreed approach against a realistic interruption. Can the people responsible reach one another and obtain what they need? Can they record the work completed outside the usual system? A test that exposes a missing contact or an unusable document is useful precisely because there is still time to address it.

Choose a partner for the response it can substantiate

The strongest continuity conversation is specific. Ask an IT partner how it would follow provider updates, communicate with your team and help assess which business activities are affected. Ask which alternatives it can support under the actual agreement, how they are tested and how responsibilities change when the provider restores service.

A good answer should identify both capabilities and limits. It should connect technical information to business decisions and leave your team clear about its own role. It should also address the return to normal work, including how temporary records, missed requests and potential duplicates will be reconciled.

Cloud services bring significant operational value, but they also place essential dependencies outside the business's direct control. Leadership means making those dependencies visible and deciding how the organisation will respond when one of them fails. A capable IT partner helps make that response practical.

Talk through your continuity priorities

If a cloud outage would leave important work or communications uncertain, Talk with us about your business continuity priorities and the support your organisation needs.

Talk to us
ThinkSwift Technology Team