Microsoft 365 Outage: How Prepared Is Your Business?

Microsoft is dealing with a major Microsoft 365 service disruption today. But the more useful question for a business owner is not simply when Microsoft will fix it.

It is this: what happens to your business when technology at the centre of it stops working?

At 11:11 am NZDT on 13 November 2026, Microsoft’s public status page continued to show a service degradation affecting Microsoft 365 Business and Enterprise users. Microsoft said users might be unable to connect to multiple services.

Potentially affected services included Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR. The incident was being tracked under EX1550543 and MO1550821.

Microsoft said a number of servers had unexpectedly become unavailable, placing more load on the remaining infrastructure. It had validated an alternative service health-check method on some affected servers and was applying that change more broadly. No confirmed restoration time had been published.

For affected businesses, that could mean staff being unable to access email, collaborate through Teams or retrieve information stored in SharePoint.

But the outage raises a bigger question.

Moving to the cloud changes the dependency

Most businesses have embraced cloud technology for good reasons.

Microsoft 365 brings email, documents, communication, identity, security and collaboration into one connected environment. It removes much of the work involved in managing infrastructure yourself.

But moving to the cloud does not remove your operational dependencies. It changes who manages them.

When one platform sits at the centre of communication, file storage, identity and access to other applications, a disruption can affect several parts of the business at once.

The problem is not necessarily the technology. It is the dependency.

Microsoft operates enormous, sophisticated infrastructure. That does not make it immune to failure. Switching providers is not necessarily the answer either. Every technology platform carries some risk.

The more useful question is whether your business understands those risks and has planned for them.

For example:

• Can employees access essential information if SharePoint is unavailable?
• Can customers still contact the business if email is disrupted?
• Which critical applications depend on Microsoft Entra ID for authentication?
• Is there another agreed way for management to communicate with staff?
• How long could the business operate before an outage caused serious financial or operational disruption?

These are not simply IT questions.

They are business continuity questions.

A cybersecurity warning while the outage is active

There is another risk that deserves immediate attention.

We are already seeing phishing emails use the Microsoft 365 disruption as cover. Some tell recipients that email or the usual communication channel is unavailable and ask them to continue the conversation another way. Then, while they have the recipient’s attention, they ask for bank account details to be updated or a payment to be redirected.

The timing makes the story sound plausible. The outage is real. The message may not be.

The pattern is straightforward: create urgency, move the conversation away from its normal checks, then change where the money goes.

Tell staff and anyone who approves payments:

• Do not accept new bank account instructions by email, chat or an unfamiliar communication channel.
• Verify any payment-detail change by calling a known contact on a number already held in your records.
• Do not use the phone number or contact details supplied in the suspicious message.
• Require a second person to approve changes to supplier or payroll bank details.
• Report suspicious messages immediately, even if no payment has been made.

A genuine service outage does not suspend your financial controls. It makes them more important.

Five things businesses should consider

1. Understand your technology dependencies

Identify the systems your business relies on and how they connect. A problem with one provider can affect several applications that appear unrelated.

Do not stop at a list of products. Record which business processes depend on them, who owns each system and what else stops if that system becomes unavailable.

2. Document your critical processes

Your team should understand how essential work gets done and what alternatives are available when the primary system cannot be accessed.

That does not require a 100-page continuity manual. Start with the work that cannot wait: customer communication, urgent approvals, payroll, dispatch, bookings or access to key operational information.

3. Agree on alternative communication methods

If email and Teams are unavailable, your business should already know how to reach staff, customers and suppliers.

The alternative might be a phone tree, text messaging or another approved channel. What matters is that people know what to use before the normal channel disappears.

An alternative channel should be agreed and communicated internally in advance—not introduced through an unexpected message during the outage.

4. Understand the difference between backups and availability

Backing up Microsoft 365 data is important, but a backup does not automatically keep the business operating during a Microsoft outage.

A backup protects data. A continuity arrangement explains how the business keeps working while the usual system is unavailable. You may need both.

5. Test the plan

A plan that has never been tested is largely an assumption.

Even a simple exercise asking, “What would we do if Microsoft 365 was unavailable for a full working day?” can reveal missing contact details, undocumented processes and applications that depend on the same identity platform.

Technology management needs to go beyond IT support

One challenge I regularly see is that technology decisions are made individually.

A new application is introduced. Another system is integrated. A process becomes automated. Each decision may be reasonable on its own.

Over time, the business develops a complex technology environment without a complete picture of how everything connects.

When something fails, those connections suddenly become very important.

This is also why it helps to understand the business problem before choosing more technology. Resilience is not created by adding another platform without understanding the dependencies you already have.

Effective technology management means knowing what the business uses, how it supports operations, where the risks sit and what happens when a critical part is unavailable.

Use the disruption as a practical test

The objective is not to eliminate every possible failure. That is unrealistic.

It is to understand your dependencies, reduce unnecessary exposure and give your team a workable response when technology does not behave as expected.

If Microsoft 365 were unavailable for an entire working day, how would your business cope?

If the answer is unclear, today’s disruption has already given you a useful place to start.