The agreement also had a clause ready for a day like this. Tony Burke said the government activated a provision of the June 2026 agreement. It required Microsoft to prioritise recovery for Australia. A government and Microsoft resilience exercise ran in the week before the outage. In August 2026, Home Affairs national security head Hamish Hansford warned of a disproportionate impact from a Microsoft outage. Home Affairs renewed that warning on 2 November 2026, eleven days before the failure.
| Item | Figure or status | Date |
|---|
| Federal contracts won by Microsoft | More than A$1 billion, plus a new five-year whole-of-government deal | 2026 |
| Defence contract | A$720 million | June and July 2026 |
| Services Australia contract | A$163.4 million | June and July 2026 |
| Australian Tax Office contract | A$151 million | June and July 2026 |
| Digital Transformation Agency review | Overall risk rated medium | February 2026 |
| Priority restoration clause | Activated for Australian recovery | 13 November 2026 |
Checked November 2026 on ABC News and Microsoft News.
What Australian organisations should change before the next outage
The warnings were on the record before the failure. The Digital Transformation Agency rated the risk as medium in February 2026. The Australian Computer Society has since called for a national review of sovereign IT risk. For private organisations the lesson is concentration. Australia depends heavily on a few global providers, and backup systems are not readily available. Switzerland drops Microsoft 365 covers what one government decided to do about that.
Two changes usually help first. Keep a communication channel that does not run through your mail provider, so urgent calls still reach people. Keep local copies of the documents your team cannot work without.
Identity is the other pressure point, and Okta vs Entra ID vs CyberArk explains the choices for managing sign-in. Treat unexpected credential prompts as hostile too, because phishing often follows a high-profile outage. Microsoft 365 phishing and MFA bypass covers a campaign that hit 258 organisations.
Is Microsoft still down in Australia?
No. The final incident end was recorded at 3:10am AEDT on Saturday 14 November. Microsoft marked the service restored at 3:15pm AEDT that afternoon. What remained was a mail backlog, because Microsoft extended its email timeout to 48 hours. Restoration was uneven, so check sign-in and mail flow inside your own tenant. Live status sits in the Service Health Dashboard.
Microsoft 365 business continuity plan for Australian businesses
A plan for Australian businesses has four parts.
- Alternate channel - a phone tree and a chat channel outside your mail provider
- Offline documents - local copies of the files your team needs daily
- Recovery checks - verify mailbox sign-in and mail flow after any incident
- Mail expectations - treat delayed mail as delayed, because the timeout ran to 48 hours
Next steps
Three things you can do this week.
- Look up EX1550543 and MO1550821 in your Service Health Dashboard, and record what you find
- Test a non-Microsoft way to reach your team, then fix whatever fails
- Save offline copies of the documents your team cannot work without
Photo: Coolcaesar, CC BY-SA 4.0, via Wikimedia Commons (https://commons.wikimedia.org/wiki/File:Building92microsoft.jpg)