Microsoft 365 outage aftermath: what Aussie small businesses should take from 13 November
2026-11-13
The Microsoft 365 outage hit Australians from early Friday 13 November 2026, and we could not find a final explanation from Microsoft in today's reporting. For Aussie small businesses and SMEs the useful work starts now: a short debrief of what stopped in your business, while you still remember it.
This post is the aftermath. For the live-day advice, see what the outage means for small business and working through a Microsoft 365 outage. We won't repeat them here.
What happened, and what Microsoft has and hasn't explained
The HRD (hcamag.com) report on the outage (13 November 2026) puts the start on Thursday 12 November US time, which was early Friday 13 November in Australia. ABC News (13 November 2026) says the problems began affecting Australians just after 3am AEDT. iTnews (13 November 2026) says Microsoft first acknowledged the issue at 4.54am AEDT, and iTnews described it as a major outage lasting more than 12 hours. Sources differ on the exact start, so treat the times as approximate.
The list of affected services was long. ABC News (13 November 2026) reported Microsoft confirming users may be unable to connect to Exchange Online, Teams, SharePoint Online, Copilot 365, Defender, Planner, To Do, Intune, Purview and Power BI.
Here is what has been reported about the cause so far:
- Global News (13 November 2026) quotes Microsoft saying it was not a rise in traffic, but a number of servers unexpectedly becoming unavailable and straining the rest.
- ABC7 San Francisco (13 November 2026) carries a Microsoft status update saying a process on the affected servers that establishes secure connections became overwhelmed.
- ABC News (13 November 2026) reports there was "no indication" of a cyber attack.
- SmartCompany (13 November 2026) reports Microsoft saying its restart attempts were "not taking as expected".
The explanation also moved during the day. BleepingComputer (12 November 2026, US time) reported Microsoft looking at reverting a small number of recent configuration updates. Another Microsoft update, carried by ABC7 San Francisco (13 November 2026), described reverting a recent network configuration change that correlates with the start of impact. SecurityWeek (13 November 2026) said Microsoft had yet to confirm a root cause.
Our read: the cause is not settled, and anyone who tells you it is, is ahead of the evidence. SecurityWeek (13 November 2026) listed the incidents in the Microsoft admin centre as EX1550543 and MO1550821. If you or your IT provider have admin access, check those entries over the coming days for a final write-up.
How it landed on Aussie small businesses and tradies
The big names made the headlines. ACS Information Age (13 November 2026) reported the Australian Federal Police, ASIO and the ABC among those affected, with local businesses also hit. The HRD (hcamag.com) report (13 November 2026) said Service NSW closed centres in parts of regional New South Wales, according to local councils.
Small-medium enterprises felt the same thing at a smaller scale, usually with no IT team to call. iTnews (13 November 2026) described Australian users waking to email that would not load. ITWire (13 November 2026) said Downdetector Australia logged more than 4,400 Outlook reports by 8.20am AEDT.
Tradies will know this feeling. Here is an example of a typical business, not a client. A five-person Sydney plumbing outfit runs quotes, booking confirmations and job photos through Outlook, Teams and SharePoint. On Friday the first crew starts at 7am. Nobody can open the day's job sheet. The office person is on the phone trying to remember who has which job. Nothing is broken at the business itself. One supplier's servers are down.
For sole traders and contractors the pattern is the same, and the pain is more personal. If your invoicing, your client email and your login codes all sit behind one Microsoft account, one fault stops all three.
Three things the headlines mostly missed
Login codes can lock you out of other tools. ABC News (13 November 2026) reported that some users could not use two-factor codes to log in elsewhere because the Outlook problems were blocking those codes. If your codes arrive by email, an email outage is also a login outage.
Some separately hosted email kept working. SBS News (13 November 2026) reported that businesses whose email was hosted by a company other than Exchange Online could still use Outlook during the disruption. That is one expert's framing of one design choice, not a rule. It does show that where your email lives is a decision, not a given.
AI tools were caught up too. The Conversation (13 November 2026) reported OpenAI and Anthropic had problems with the tools that connect their AI services to Microsoft 365. If you have wired ChatGPT or Claude into your mailbox or files, check whether those automations stalled on Friday too. We cover this in how AI can help your business ride out outages.
One more point for the nervous. Cypro, in a bulletin on the 12 November outage, advised that, on the evidence available, the outage should not itself be treated as a sign your own Microsoft 365 setup was compromised. That is a reasonable default, not a guarantee.
The Friday debrief: five questions to run this week
Small-medium enterprises rarely have an IT team, so give this 30 minutes with whoever runs your admin. Write the answers down. Do it before the memory fades.
- What stopped? List every job that stalled or was done differently. Quotes? Bookings? Payroll approvals? Patient reminders? Be specific.
- For how long? Note when you noticed and when each task was back. This is your real downtime, which may differ from the headlines.
- What did we improvise, and did it work? Phone calls, personal phones, texts, paper. Keep what worked. Write down what was awkward or risky, such as client details sent over personal channels.
- What was the single point of failure? Look for the one thing that, when it failed, took several others with it. Login codes by email and shared calendars are common ones.
- What would have kept the work moving? Pick one task from question 1 and ask what the smallest fix would be. A printed job sheet, a second contact method, a copy of the schedule somewhere else.
Then finish with one written line: "By [date], [name] will [fix] for [job]." That line is your output. A fix with no name and no date is a wish.
Pick one fix, not five. In our view, trying to fix everything after an outage tends to mean fixing nothing.
If question 5 turns up fixes that need more than a printout, build resilience into business workflows covers the design side.
There is a context point too. The Conversation (13 November 2026) noted earlier Microsoft disruptions this year, including January and a code update in August that took several days to fix. Our opinion: for Australian small businesses, a day of Microsoft downtime is something to plan for, not a once-off. You don't have to leave Microsoft 365. You do have to know what your business does when it is gone.
Bring your debrief to a first chat
The debrief is the raw material for a sensible fix. If your answers show a few manual jobs that stalled, workflow automation is where MILabs would start, by working out which steps can keep moving or recover on their own when one system drops. Bring your list from question 1, the jobs that stalled on Friday, and we will go through it together. Discovery is free, no obligation from the first chat. Every enquiry gets a reply within 24 hours.
Sources
- Microsoft outage drags on for hours, disrupting Outlook, Teams for thousands
- Access to Microsoft Outlook and other services being restored as cyber security chief investigates - ABC News
- Microsoft users caught up in global M365 outage - iTnews
- Microsoft Outlook outage disrupts workplaces and raises cyber risks
- Major Microsoft outage hits Outlook, Teams, more
- Global Microsoft outage continues as tech giant seeks "alternate workstreams"
- Microsoft 365 outage continues globally as company says no fix yet - National
- Microsoft outage live updates: What to know as Outlook, 365 and other apps remain down - ABC7 San Francisco
- Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide
- Microsoft 365 Outage Disrupts Outlook, Exchange Online and Teams - SecurityWeek
- Microsoft's Friday the 13th outage shows the cost of running the whole office on one cloud
- The Microsoft outage is part of a growing trend. This is how to prepare for further disruption
- Microsoft has suffered a global outage. A tech expert explains what went wrong
- Microsoft 365 Outage: What Happened on 12 November
Frequently asked questions
- Has Microsoft published a final explanation for the 13 November 2026 outage?
- Not in the reporting we found on 13 November 2026. Microsoft described servers becoming unavailable and a process being overwhelmed, but had not confirmed a root cause. Updates are posted in the admin centre entries EX1550543 and MO1550821.
- Was the Microsoft 365 outage a cyber attack?
- ABC News reported on 13 November 2026 that there was no indication of a cyber attack. The cause itself was still under investigation.
- Do sole traders need an outage plan?
- Yes, a light one. List the jobs that depend on one Microsoft account, including login codes, and pick one fix, such as a printed job sheet or a second contact method.
