Microsoft 365 has suffered a major service disruption, with Outlook email users unable to reach their mailboxes and problems reported across Teams, Copilot and other cloud services. The incident escalated on Thursday, 12 November 2026 in the United States — early Friday morning, 13 November, in eastern Australia. Microsoft has linked the disruption to servers unexpectedly becoming unavailable and placing extra load on the remaining infrastructure. It is restoring capacity and testing changes, but the complete scope and recovery time were not confirmed in the updates available for this report. Associated Press; Microsoft incident messages reproduced by the University of Pennsylvania.
Developing story | Published 13 November 2026 (AEDT). Incident status can change rapidly. Our source review covers Microsoft’s Exchange Online incident EX1550543 and wider Microsoft 365 incident MO1550821, independent reporting and Microsoft’s service-health guidance. Featured photograph is a licensed illustrative image of a person using a laptop, not a real outage screenshot or victim. A separate original AI-generated outage illustration has been saved to NextNews’s Canva media library.
On this page
Is Microsoft Outlook down — and how widespread is the outage?
Microsoft acknowledged connectivity errors involving Exchange Online, the hosted mailbox platform used by many Microsoft 365 business and education customers. Its initial public messages focused on customers in the Americas, while subsequent updates and reporting discussed infrastructure pressure spanning multiple regions. The Guardian and The Verge reported an international disruption, but Microsoft had not published a definitive country-by-country count of affected customers.
Outage-monitoring service Downdetector recorded almost 130,000 reports of Outlook trouble shortly after 1pm US Eastern Time on 12 November, according to the Associated Press. These are individual reports submitted to an outage tracker, not 130,000 verified unique users or organisations. Multiple reports can come from the same person, and the actual number of affected accounts may be much higher or lower.
For businesses in Australia, the incident’s global reach creates understandable concern, but it would be misleading to say every Australian Microsoft 365 tenant has lost access. The user impact depends on regional infrastructure, authentication and which services a company uses.
Which Microsoft 365 services are affected?
Microsoft’s service-health messages confirmed Exchange Online access problems and identified Teams, SharePoint Online, Microsoft 365 Copilot, Defender XDR, Planner and To Do as potentially affected by the wider incident. There were also reports involving OneDrive and Office web applications. A service being named in a potential-impact list does not mean every user of that service is affected. See the Microsoft 365 incident updates.
| Product or service | Evidence and incident status | What users may experience |
|---|---|---|
| Outlook for Microsoft 365 / Exchange Online | Confirmed Exchange Online incident EX1550543 | Mailbox access via Outlook on the web, desktop/mobile and connected applications may fail |
| Microsoft Teams | Separately reported; earlier North American issue was restored; also listed as potentially affected in MO1550821 | Chats, meeting access or other collaboration features could be degraded |
| SharePoint Online | Potentially affected under MO1550821 | Sites, shared documents and collaboration may be harder to access |
| Microsoft 365 Copilot | Potentially affected under MO1550821 | AI assistance and connected workspace tasks may fail or respond slowly |
| Defender XDR, Planner and To Do | Potentially affected under MO1550821 | Some security consoles and task-management features may be inaccessible |
| OneDrive, Word, Excel and PowerPoint | Various user reports; not every feature is independently confirmed down | Some cloud-dependent activities may fail; locally installed apps and offline files may still work |
An earlier, separately identified Teams disruption affecting North American customers was reported as restored, while the broader Microsoft 365 incident could still cause new or intermittent problems with Teams access. The distinction matters: recovering one Teams issue is not evidence that all Microsoft 365 problems have ended. Associated Press coverage; incident history.
What caused the Microsoft 365 outage?
Microsoft’s investigation indicates that numerous servers became unexpectedly unavailable after problems with automated health checks — processes used to assess whether infrastructure is healthy enough to keep serving customers. That removal reduced the available capacity and shifted more work onto the remaining servers, creating elevated load and connectivity errors. Microsoft said this was not simply a surge in normal user traffic. WIRED reporting on Microsoft’s technical updates; Guardian outage coverage.
Engineers began redistributing traffic, restarting affected servers and testing an alternative health-check process. Microsoft also paused some deployments and configuration changes while examining whether any recent changes contributed to the incident. This describes its mitigation work, not a final post-incident root-cause report. As the investigation continues, it is possible that a later technical explanation will be more specific.
There is currently no substantiated evidence in the statements reviewed that a cyberattack caused this particular outage or that the disruption exposed customer emails. Service downtime and a data breach are different events; one must not be described as the other without evidence.
When did the problems start?
The Exchange Online incident EX1550543 lists a start time of approximately 16:17 UTC on Thursday 12 November (about 3:17am AEDT on Friday 13 November). The broader Microsoft 365 incident MO1550821 lists a start around 18:26 UTC (about 5:26am AEDT). The incident messages were still marked as service degradation in the updates reviewed, while Microsoft was actively applying mitigations. Incident log and timestamps.
Downdetector reports spiked around early afternoon in the United States. Some users later saw improvements, but falling reports do not establish that every mailbox, meeting, calendar or security service is fully restored.
How to check whether Outlook or Microsoft 365 is working again
- For workplace Microsoft 365 administrators: sign in to Microsoft 365 admin centre, choose Health → Service health and check incident IDs EX1550543 and MO1550821. Your tenant’s status can be more useful than general social-media posts.
- For everyone else: check Microsoft’s public service-health page and updates from Microsoft’s official status channels; ask your organisation’s IT team whether your tenant is affected.
- Check the relevant product: Outlook for business, personal Outlook.com, Teams, OneDrive and Microsoft 365 apps do not always share the same incident or recovery path.
- Interpret green status indicators carefully: the public page may show consumer products operational while business or enterprise incidents remain visible in tenant-specific admin dashboards.
Microsoft’s official service-health instructions explain how to view active incidents and historical events. Status information can change within minutes, so the status in this article should not be treated as a continuously updated live feed.
What can you do while Outlook is not connecting?
If your email is needed for urgent work, first ask whether other colleagues are experiencing the same problem and check the service-health notices. A widespread backend incident may not be fixable by restarting your computer, repeatedly resetting your password or reinstalling Outlook.
- Use approved alternative communications: for urgent matters, telephone, SMS or another employer-approved service may work. Do not transfer confidential client or company information to an unapproved personal account simply because Outlook is unavailable.
- Try a different Microsoft access method cautiously: if the problem affects only one client, testing Outlook on the web or the desktop app can help identify the scope. If Exchange Online itself is affected, switching clients may not solve it.
- Use already synced offline files: locally cached Outlook content or previously downloaded Office documents may remain viewable, but new messages and edits might not synchronise until the service recovers.
- Keep records of urgent failed communications: note when important messages, meetings or customer requests could not be processed so they can be followed up once access returns.
- Leave account and security settings intact: do not disable multi-factor authentication, install unofficial “outage repair” tools or follow unfamiliar recovery links.
- Do not rely on automatic message delivery: once access is restored, confirm that time-sensitive emails were actually sent and received; inspect drafts, outbox items and bounce notifications.
Why the outage matters to Australian businesses
Australian organisations rely on Microsoft 365 for business email, virtual meetings, collaboration and document access. A disruption can affect appointment confirmations, customer enquiries, schools, government work, healthcare administration and suppliers. The impact on any individual organisation will depend on its Microsoft 365 configuration, existing offline access and fallback communications.
For small businesses, a useful short-term measure is an incident contact list containing authorised staff telephone numbers and alternative communication arrangements, stored securely outside the affected platform. For sensitive sectors, fallback systems must still meet applicable privacy, record-keeping and security obligations.
The longer-term lesson is that a cloud service can be highly reliable but still suffer widespread interruption. Businesses should periodically test how they would operate when their usual email, file storage and meeting service is unavailable. The best fallback is one that has been approved, documented and tested before a disruption occurs.
Watch out for fake Microsoft outage alerts and phishing
Major disruptions are opportunities for scammers to circulate fake service-restoration notices, urgent password-reset prompts and phoney support numbers. Treat a message claiming you must re-enter your Microsoft password, submit a security code or install a new recovery tool with caution. Always open Microsoft’s official support or status site independently rather than through an unexpected email or message. Australian Cyber Security Centre scam guidance.
NextNews has also explained how convincing fake websites and suspicious payment links work in its Black Friday shopping scam guide. The same basic principle applies here: an urgent-looking warning is not proof that the sender is trustworthy.
What happens next — and when will Microsoft 365 be restored?
Microsoft has been returning servers to service and testing mitigations, including an alternative method of assessing server health. Those steps could improve availability before a final explanation is published, but the updates reviewed for this article did not establish a single guaranteed restoration time for all affected services and regions. Guardian’s technical update; Microsoft incident history.
Watch for an official service-restored notice for the specific incident affecting your organisation. If a service begins working again, there may still be delayed or failed background tasks, so organisations should verify time-sensitive email, calendar and workflow activity rather than assuming every action completed normally.
Outlook and Microsoft 365 outage: frequently asked questions
Does this mean Microsoft 365 has been hacked? No such conclusion is supported by the incident information reviewed. The reported problem concerns availability and infrastructure; Microsoft has not attributed this outage to a confirmed data breach.
Does the public status page saying “operational” mean business Outlook is fixed? Not necessarily. Consumer-product status and organisation-specific Microsoft 365 service health are different views. Administrators should verify the relevant Exchange Online and suite incidents.
Will unsent Outlook messages disappear? It depends on the client and whether a draft or queued message was saved. Once the service recovers, inspect the outbox and sent folder, and confirm critical messages with recipients before resending to avoid duplication.
Can users fix the outage themselves? A locally misconfigured device may need troubleshooting, but a confirmed Microsoft-side incident generally requires Microsoft to restore its infrastructure. Keep following authorised IT instructions and vendor updates.
Are all countries affected? There are international outage reports and Microsoft has discussed infrastructure across multiple regions, but no comprehensive verified count by country was available in the updates reviewed. It would be inaccurate to state that every Microsoft 365 user worldwide is offline.
The bottom line
This is a substantial Microsoft cloud-service disruption with confirmed Exchange Online problems and a broader Microsoft 365 incident. Microsoft has identified a probable infrastructure failure pathway and is working to restore capacity. The best immediate response is to check official service health, use approved alternatives for urgent work and avoid unnecessary account changes.
Has Outlook, Teams or another Microsoft 365 service stopped working for you? Which country are you in, what error are you seeing, and which service has been affected? Share your experience in the comments without posting passwords, screenshots of private messages or identifying account information.
Sources and editorial disclosure
Sources checked 13 November 2026 (AEDT): Microsoft incident notices reproduced by the University of Pennsylvania — EX1550543 and MO1550821; Microsoft public service health; Microsoft service-health documentation; Associated Press, 12 November; The Guardian, 13 November; WIRED, 12 November; The Verge, 12 November; and Australian Cyber Security Centre. This is a developing incident; affected services, geographic reach and restoration status may change after publication.
Editorial disclosure: Prepared with AI assistance and checked against the linked sources. Incident IDs and technical findings are attributed to Microsoft’s published updates. Reported outage counts are third-party submissions, not verified totals of impacted people. No cause involving hacking, loss of data or a universal shutdown of all Microsoft products is established here. This article offers general service-status and business-continuity information, not personalised IT or cybersecurity advice. The featured licensed photograph is illustrative and does not show a real Microsoft error or outage victim; an original separately generated AI illustration is saved in Canva and is not evidence of the incident. See the NextNews website disclaimer for general terms.
More in World News
Disclaimer
NEXTNews aims to keep its reporting accurate and up to date. Sources and dates are included where practical; information can change after publication. To flag an error or request a correction, contact our team. For important decisions, check the original source and see our full disclaimer.