When Microsoft 365 Goes Down, Can Your Business Still Work?

Technology
17 Nov 2026 • 4:30 PM MYT
Amarjeet Singh Sran
Amarjeet Singh Sran

A Business Consultant in Malaysia with over 25 years of experience

Image from: When Microsoft 365 Goes Down, Can Your Business Still Work?
Picture from Google Gemini's Image Generation (Nano Banana)

By Dr. Amarjeet Singh @ AJ

It’s 9 am. Sales is waiting for a quotation to be approved. Finance needs an invoice from SharePoint. A customer has joined a Teams meeting, but your team can’t get in. You try to send an email explaining the delay. Outlook is affected too.

The Microsoft 365 disruption on 13 November 2026 affected services including Outlook, Teams and SharePoint Online. It raises a question for every business owner and department head. Are we using technology to our advantage, or have we put ourselves at its mercy? sdf.status.cloud.microsoft

From a business and crisis management perspective, my first question would be simple. Who is waiting on us right now, and how do we reach them?

The first 15 minutes

If you’re a user, save what you’re working on. If a document won’t sync, keep a clearly labelled copy in an approved work folder and tell your team which version you’re using. If an email seems stuck, check Outbox and Sent Items before resending.

Then look at what’s due in the next hour. A customer waiting for a decision deserves a call. A supplier holding a delivery needs to know whether to proceed. A meeting that can wait should be rescheduled, with participants told directly. A meeting that needs to happen can move to an approved backup platform or a phone call.

Give IT something it can act on. “Teams is down” gives them very little. “Three staff in two locations couldn’t join the 9 am supplier call” tells them who is affected, what failed and why it matters. Include the time and the error message if you have it.

If you’re the IT head, check Microsoft 365 Admin Center → Health → Service health. Confirm which services are affected for your organisation and record the incident ID if available. If the admin centre is inaccessible, use Microsoft’s public status page. learn.microsoft.com

Send one clear update through a channel staff can access. Tell them what’s affected, what to use and when they’ll hear from you again. If you promise an update at 10 am, send it at 10 am. Staff need a reliable time to plan around, even when you’re still waiting for Microsoft.

Give every critical job a backup

Start with the work. Which orders, payments, customer commitments and frontline services have to continue today? Once you know that, choose the simplest fallback your team can actually use.

If this is unavailableWhat you can do
OutlookCall or SMS for urgent updates. Use an approved alternative channel for follow-up. Keep key customer and supplier numbers in an approved location staff can reach during an outage.
Teams meetingsUse an approved alternative such as Zoom, Google Meet or a telephone conference. Make sure the host can sign in and participants can get the new link without Outlook or Teams.
SharePoint or OneDriveKeep controlled offline copies of essential SOPs, contact lists, checklists and forms. Give each document an owner, a version date and a review schedule.
Planner or shared task listsUse an approved offline tracker or a physical board. Record the task, person responsible and deadline. Nominate one person to enter updates when the system returns.
Digital approvalsUse a pre-approved manual process. Record who authorised the decision, when, and within what limits. Keep the normal authorisation rules in place.
Customer service toolsRoute enquiries to a published phone number or working support channel. Log each case and give customers a realistic callback time.
Copilot or automated workflowsUse standard templates, checklists and manual routing for time-sensitive work. Give staff an approved place to record anything the automation would normally capture.
Dashboards or live reportsUse the last verified report, clearly marked with its timestamp. Collect fresh figures from department leads when a decision depends on current information.

There’s a difference between having an alternative and being able to use it at 9 am. If your backup meeting platform uses the same work sign-in, test what happens when that sign-in is unavailable. If your emergency contacts are in SharePoint, try getting them with SharePoint out of reach. If the backup works only when the IT head is around, have a second person practise running it.

For a small business, a current contact list, a phone and a single manual log may be enough to get through the morning. A larger operation may need an emergency notification service, a separately accessible backup platform and clear instructions for every site. The right choice depends on how long you can afford to lose each workflow.

Let department heads make the operational decisions

IT can confirm that SharePoint is unavailable. Finance knows which payment is urgent. Sales knows which quotation expires at noon. Operations knows whether the next shift can open safely. Those decisions belong with the people responsible for the work.

Imagine a tour group arrives at an attraction while the team can’t access its booking list. If the site has an approved offline arrivals list, the supervisor can verify the group and record admission manually. If the list is unavailable, the duty manager needs a way to verify the booking and the authority to decide what happens next. The group is already at the gate. They need an answer while IT works on the outage.

The same principle applies to a warehouse waiting for a dispatch approval or a service team waiting for a work order. Who can authorise the next step, and where will that decision be recorded? Answer those questions before the outage. Agree in advance which activities must pause if your team can’t complete an essential safety, identity or payment check.

Use the tools you have, with some discipline

WhatsApp can be handy for telling staff where to join a replacement call or asking a supervisor to ring a customer. Use it for coordination where company policy allows. Keep sensitive files, customer records and financial information in approved systems. An outage is a poor time to start moving company documents into personal email accounts or unapproved storage.

Think about the dependencies too. A spare laptop helps when a device fails. A mobile hotspot helps when the office internet fails. A phone call helps when Teams fails. Each backup solves a different problem. Ask your team what it would do if the office lost internet, if the Microsoft service was disrupted, or if staff couldn’t sign in. Those three scenarios can require three different responses.

And before buying another subscription, ask the people who will use it to try it. Can the receptionist reach the contact list? Can the site supervisor send a staff alert? Can a manager approve urgent work while travelling? A quick drill will tell you where the money and training are needed.

Recovery includes the work done during the outage

When services return, ask affected staff to test the tasks they actually need. Send and receive email. Join a Teams call. Open, edit and save a shared document. Check whether the workflows that route approvals or notifications are running again.

Then account for what happened in the meantime. An email may have been sent twice. Two teams may have updated different copies of the same spreadsheet. A purchase may have been approved by phone while the system still shows it as pending. Give each department someone to reconcile those records and follow up with customers or suppliers where needed.

Before everyone moves on, ask where the delay really came from. Did we spend 30 minutes looking for a phone number? Did two managers think the other one had authority? Did the backup meeting link go out through the very service that had failed? Fix the specific thing that held people up.

Give your management team 15 minutes

At your next management meeting, put one question on the table.

If Outlook, Teams and SharePoint were unavailable until tomorrow morning, what would we do to serve customers and keep urgent work moving today?

Ask someone to open the emergency contact list. Get a department head to walk through an urgent approval. Have a team member start a backup call and get everyone onto it. Try it with the people who will be on duty on a Saturday, when several of your usual decision-makers may be away.

Technology gives us the ability to work faster and serve customers across locations. We get the full advantage when people also know how to operate through a disruption. Microsoft can restore Microsoft 365. Keeping your business moving while they do it is a management responsibility.

Dr. Amarjeet Singh @ AJ


Amarjeet Singh Sran (amarjeetsinghsran5@gmail.com) is a content creator under the Newswav Creator programme, where you get to express yourself, be a citizen journalist, and at the same time monetize your content & reach millions of users on Newswav. Log in to creator.newswav.com and become a Newswav Creator now!

The User Content (as defined on Newswav Terms of Use) above including the views expressed and media (pictures, videos, citations etc) were submitted & posted by the author. Newswav is solely an aggregation platform that hosts the User Content. If you have any questions about the content, copyright or other issues of the work, please contact creator@newswav.com.

Newswav Malaysia Best News App

Newswav is an online content aggregator and obtains its content from different online sources. The content in the app do not belong to Newswav nor do they reflect the opinions of Newswav and its staff. Your use of this app indicates your understanding and acceptance of this information.

Newswav Sdn. Bhd. (201701008480 (1222645-M)) 2026 All Rights Reserved