On the morning of Friday 13 November (Sydney time), people across Australia opened their laptops and found Outlook wouldn't sign in, Teams calendars were blank and Copilot wouldn't load. The ABC reported that Downdetector logged a peak of nearly 140,000 problem reports for Outlook alone, and that Service NSW centres were among those affected. Microsoft said there was no indication of a cyber attack.
If you spent that morning restarting your computer and wondering what you'd broken, this guide is for you. Outages like this will happen again, with Microsoft or with someone else. Ten minutes of preparation makes the next one much less stressful.
Step 1: Check whether it's you or them
Before you change anything, spend two minutes finding out where the problem is.
Ask one colleague. If the person next to you, or someone on a different internet connection, has the same problem, it's almost certainly not your computer.
Check Microsoft's status page. On your phone, go to status.cloud.microsoft. It shows whether Microsoft has an open incident. During a large outage, Microsoft also posts updates from its Microsoft 365 Status account on X.
Check with IT, once. Your IT team can see more detail than you can. Look for a message from them before you send one. During an outage they're getting hundreds.
Step 2: Leave these alone
Most of the extra damage in an outage comes from people trying to fix it. If the status page shows an incident, don't do any of the following:
Don't reset your password. Your password isn't the problem, and a reset during an outage can leave you locked out after everyone else is back.
Don't reinstall Outlook or Teams. You'll lose time and possibly your settings, and it won't help.
Don't click links in "your account has been suspended" emails or texts. Scammers move quickly when an outage is in the news. Microsoft won't ask you to confirm your password by text.
Don't forward work files to your personal email so you can keep going. That creates a privacy problem that outlasts the outage.
Step 3: Keep working with what still runs
An outage rarely takes everything down at once. Try these before you give up on the morning:
Files you've already opened. Word, Excel and PowerPoint on your computer usually keep working on files that are saved locally or already open. Save a copy to your desktop and carry on.
The phone. If a meeting can't start, ring the organiser. A five-minute call often covers a thirty-minute meeting.
Thinking work. Planning, outlining and reviewing printed or downloaded documents don't need email.
What about using a different AI tool?
If Copilot is down, it's tempting to open ChatGPT, Claude or Gemini on a personal account. That's fine for work with nothing confidential in it, such as outlining a presentation or tidying your own notes. It isn't fine for client details, staff information, contracts or anything else your workplace wouldn't want leaving its systems. The outage doesn't change your privacy rules. Our guide AI at Work: What's Safe to Type Into ChatGPT and What Isn't has a simple list.
Write your one-page outage plan
The best time to plan is the week after an outage, while everyone remembers what went wrong. Ask any AI tool to draft a plan for you, then fix it with what you know about your own team.
Print the finished plan. A plan saved only in SharePoint is no use when SharePoint is down.
A list of mobile numbers for your team and your five most important outside contacts, kept somewhere other than Outlook. And a saved or printed copy of whatever you'd need in the first hour of a normal day: today's appointments, this week's payment run, the roster. Both take minutes to set up.
Try it this week
Bookmark status.cloud.microsoft on your phone today. Then run the prompt above, spend ten minutes correcting the draft, print it, and put your team's mobile numbers on the back.