If you sat down at your desk on Friday morning and Outlook just spun, Teams wouldn’t connect and your files wouldn’t sync, it wasn’t you. It wasn’t your Wi-Fi either. Microsoft 365 had fallen over, and it was taking a good chunk of the working world with it.
As I write this on Friday afternoon, Microsoft is slowly bringing servers back a few at a time, but it hasn’t declared the problem fixed or said exactly what caused it. Here’s what we know, the security risks that come with a day like this, and what I’d suggest doing about it.
What happened
The issue started around 18:00 UTC on Thursday, which was early Friday morning here in Australia. Microsoft first flagged problems with Exchange Online mailboxes in the Americas, then admitted users in any region could be affected. By 7:30am Sydney time, Downdetector had more than 2,500 Outlook reports from Australia alone, and well over 120,000 worldwide.
It wasn’t just email. Teams, SharePoint, OneDrive, Copilot, Planner and Power BI were all hit. So were some of the tools IT teams use to manage and protect devices, including Intune, Defender and Purview. In Australia, Service NSW, Queensland Health, several state and territory governments and local councils reported disruption.
Microsoft’s explanation has shifted as the day went on. It started with “heavy load”, then said traffic hadn’t actually increased. The latest version is that some servers unexpectedly stopped responding, which piled the work onto the rest, and a core process on those servers got overwhelmed. Servers that were brought back online froze again as soon as traffic hit them. Microsoft is now looking at rolling back some recent configuration changes.
Importantly, Microsoft says there is no indication this is a cyber attack, and the National Cyber Security Coordinator is keeping an eye on it.
So why is a security company writing about an outage?
Because outages are when people make security mistakes. Everyone is stressed, things are broken, and the usual rules feel like they’re getting in the way. Attackers know this, and they love it.
Here’s what I’d be watching for.
- Fake “fix your account” emails. Expect messages dressed up as Microsoft, telling you to sign in again, verify your mailbox or “restore access”. They link to convincing fake login pages built to steal passwords. Microsoft will not email you a link to fix an outage.
- Payment scams using the outage as cover. “Our email is down, please pay this invoice to the new account, I’ll confirm by text.” When email is unreliable, people accept odd requests through other channels. That’s exactly what business email compromise thrives on.
- Fake IT support calls. Someone rings claiming to be from Microsoft or your IT provider and offers to get you back online if you install a remote access tool. Hang up.
- Panic changes by admins. When nothing works, it’s tempting to switch off MFA, loosen conditional access or open up mail rules “just to test”. The problem is on Microsoft’s side. Those changes won’t help, and they’re easy to forget to undo.
- Work drifting to personal apps. Staff who can’t use Teams or OneDrive will grab WhatsApp, personal Gmail or a free file-sharing site to get the job done. Then client data lives somewhere you don’t control.
- Reduced visibility. With some Defender and Intune portals disrupted, your security team may not see alerts as quickly. Protection on devices generally keeps running in the background, but the people watching are partly blindfolded for a while.
What I’d do today
- Send your team a short, calm message through a channel that works, like SMS. Tell them it’s a Microsoft problem, not a hack, and that nobody should click any “re-authenticate” or “restore your mailbox” links.
- Verify any payment change by phone, using a number you already have, not one in the message. Today of all days.
- Check status from the source. Use the Service health page in the Microsoft 365 admin centre, or Microsoft’s public status page if the admin centre won’t load. Downdetector is handy, but it’s just user reports.
- Don’t make emergency security changes. Leave MFA, conditional access and mail flow rules alone unless Microsoft specifically tells you to.
- Once things are back, do a quick tidy-up. Look for odd sign-ins, new mail forwarding rules and any temporary workarounds people set up, and remove them.
The bigger lesson
This is the third major Microsoft 365 disruption this year, after January and August. That’s not a reason to abandon Microsoft. Every big cloud provider has bad days. But it is a reminder that when one platform runs your email, chat, files, device management and security tools, one bad day hits all of them at once.
A few questions worth asking before the next one:
- How would your team talk to each other, and to customers, if email and Teams were down for a full day?
- Do you have offline access to the documents you can’t work without, like contracts, rosters and client details?
- Is there a written plan, even a one-pager, that says who decides what during an outage?
- Does your backup sit somewhere other than the platform it’s backing up?
None of this needs to be expensive. A shared phone list, an agreed backup channel and a page of “what we do when Microsoft is down” will put you ahead of most businesses. Outages are annoying. Being caught out by a scam during one is far worse.
Sources
- Forbes Australia: Microsoft servers crash in global outage (forbes.com.au)
- The Register: Microsoft struggling to fix massive cloud outage that’s taken down email and Intune (theregister.com)
- Cybersecurity News: Massive Microsoft 365 outage impacts Exchange Online, Teams, SharePoint, Copilot and Defender XDR users (cybersecuritynews.com)
- Microsoft 365 Status: incident updates EX1550543 and MO1550821
- McAfee: Why outages trigger a scam playbook (mcafee.com)
This article reflects public information as of Friday 13 November 2026. The outage was still being resolved at the time of writing, and Microsoft has not yet published its root-cause report.
