How to Keep Working Through a Microsoft 365 Outage
2026-11-13
When Microsoft 365 goes down, the fastest way to keep working is to confirm the outage, move the team to an agreed backup channel, and switch urgent customer work to the phone. The global outage on 13 November 2026 began at about 5:15am AEDT and was still not fixed late in the morning, according to the ABC, so a plan for a few hours is the plan to have.
In the first fifteen minutes
Confirm it is Microsoft. Check the service health page in the Microsoft 365 admin centre, Microsoft's status channels and Downdetector before anyone spends an hour restarting routers. On 13 November, Microsoft's service health page listed Outlook, Exchange Online, Teams, OneDrive, SharePoint Online and Copilot among the affected services (SBS).
Tell the team where to talk. If Teams is down, nobody can announce that on Teams. Send one SMS or group message saying the business is working around an outage, which channel to use and who is coordinating.
Warn staff about scams. Outages attract fake support calls. On the day, ING warned customers about scammers offering to fix the problem (ABC). Nobody legitimate needs a password to fix Microsoft's servers.
Keep the work moving
- Use what is already on your device. The Outlook desktop app in cached mode still shows recent mail and calendar entries. OneDrive files marked "Always keep on this device" open without a connection.
- Pick up the phone. Call customers with orders or appointments today. A phone call confirms an order as well as an email does, and customers remember who called.
- Write things down in one place. Keep a shared list, on paper or in a tool outside Microsoft, of every order, enquiry and promise made while systems are down. That list is how you catch up afterwards.
- Post a short notice. A line on your website or social channels saying email is delayed stops customers worrying that you have ignored them.
- Do the work that needs no connection. Planning, quoting from local files, site visits and phone calls can all carry on.
When services come back
Recovery can be patchy. On 13 November, Microsoft warned that servers it had restored could become unresponsive again once traffic returned (ABC). Give it an hour of stable service before moving everyone back.
Then work the catch-up list. Enter the orders taken by phone, reply to anything that arrived during the gap, and ask key customers to resend anything urgent in case it was delayed.
Set up for next time
Three changes take less than an hour and make the next outage much easier:
- Agree a backup team channel and put everyone's mobile number in it.
- Keep key customer and supplier phone numbers somewhere outside Outlook.
- Mark the files you need every day to stay on each device.
Lead capture, queued automations and a written plan take a little longer. They are covered in how to build resilience into your business workflows.
Want it built before the next one?
Discovery is free, no obligation from the first chat. Want website enquiries saved to a sheet while email is down, and an SMS to your team the moment Microsoft reports a problem? MILabs, a Sydney agency serving businesses across Australia, builds both as part of workflow automation. Tell us what stopped for you on 13 November, and every enquiry gets a reply within 24 hours.
Frequently asked questions
- How do I know whether Microsoft 365 is down or it is just us?
- Check the service health page in the Microsoft 365 admin centre if you can reach it, Microsoft's official status channels, and Downdetector. If several unrelated people report the same problem, it is the platform and not your network.
- Can we still read email during an outage?
- Often yes, in part. The Outlook desktop app keeps a local copy of recent mail in cached mode, so you can read and search what had already arrived, even while it cannot send or receive.
- Should we switch to personal email accounts during an outage?
- Only for short, low-risk messages, and only if your business has agreed it in advance. Customer data and anything sensitive should stay in business systems, so a phone call is usually the safer fallback.
