Microsoft 365 outage disrupts Outlook and Teams; full recovery not confirmed

November 14, 3:07 am Sydney update: residual problems remain

Microsoft's latest public notice still lists service degradation. The company says it is addressing remaining effects and checking recovery across different connection methods to confirm that service remains stable. This is not a full-restoration announcement, and the notice does not provide a guaranteed finish time. Microsoft says it has no evidence of malicious activity associated with the incident; a full account of the cause and further protective measures is promised after mitigation.

The current description centres on Exchange Online and services that depend on email or calendar data. Outlook on the web, desktop Outlook, Exchange ActiveSync and REST connections may fail to open mailboxes, and delivery can be delayed. Copilot Chat may fail to load or respond, or may be unable to use work email, calendar and files. Microsoft Graph requests for mail, calendars and contacts may time out, also disrupting related management and notification functions.

Most core Teams calls, meetings, group chats and channel messages remain functional, according to Microsoft. Calendar scheduling, invitations and edits can fail, as can creating live or virtual events, some Copilot and app-chat features, contact changes and private or shared channel creation or deletion. Standard channels continue to work. Direct access to files stored in SharePoint remains functional, but sharing files with people outside an organisation may fail even when that sharing is permitted by its settings.

The impact list also covers some Microsoft 365 administration pages and app-management tools, recently used files, education features, Defender and Purview functions, Planner operations, To Do, Universal Print and intermittent Intune work. Fabric and Power BI operations involving sensitivity labels may fail. Microsoft mentions removing a label as a possible workaround only where an organisation's data-protection policies permit it; users should not bypass those controls simply to finish an export.

Power Apps and Field Service mobile sign-in may fail intermittently. Microsoft's notice suggests the web versions as a possible alternative and says users already signed in may avoid further disruption by not signing out, clearing app data or reinstalling during the incident. For Windows 365, the stated connection problem concerns customers using Microsoft Purview Customer Key for their tenant and Cloud PCs, not every Cloud PC. These are possible impacts, not proof that every account or feature is failing. The public status page separately continues to say that no Azure issues have been detected.

Recovery update, 13 November, 11 pm Sydney time

Microsoft says service availability and email delivery are improving across a growing part of its affected infrastructure in Europe. Japan is comparatively more stable and North America is also improving, but some users may still face intermittent problems. This is recovery progress, not an announcement that all services have been restored.

The company says work is continuing on the remaining disruptions and on clearing email queues and backlogs. Its extended 48-hour email timeout window remains in place to help protect delayed messages. Microsoft says it has found no evidence of malicious activity linked to the incident and plans to publish a full post-incident report after mitigation is complete.

November 13, 22:04 Sydney update: partial Asia-Pacific recovery

Microsoft says it has completed recovery actions across portions of the affected infrastructure in Asia-Pacific and is gradually restoring traffic. Its public status update, timed at 22:04:50 in Sydney, reports improvements in mailbox access and processing delayed emails. Some users may still encounter intermittent problems; this is not an announcement that every account or all affected services have returned to normal.

The company is extending the recovery work to affected infrastructure in other regions while adding capacity and stabilising service. Clearing email queues remains a priority, and the extended 48-hour email timeout is still in place to help protect delayed messages. Microsoft continues to report no evidence of malicious activity associated with the incident and says a fuller account of the cause and preventive measures will follow mitigation. It has not supplied a firm completion time for full recovery.

Earlier reporting retained for context

November 13, 9:10pm Sydney: recovery remains incomplete

Microsoft's latest public notice, updated at 9:01:07pm Sydney time on November 13, said recovery had progressed in phases, with global telemetry and customer reports showing incremental improvement across several workloads. Service health remained variable and capacity had not fully returned to normal. Network and traffic-management actions were continuing.

The current scope is narrower than saying every Microsoft service is down. Exchange Online and email-dependent features are affected: Outlook mailbox access and delivery may fail or be delayed; Copilot Chat may not load or respond, and work-data access may fail. Most core Teams calls, meetings, group chats and channel messages remain functional, according to Microsoft, while Exchange-dependent calendar scheduling, invitations, viewing and edits may fail. Direct access to SharePoint files remains functional, and the public page separately reported no Azure issues detected.

Microsoft said it was continuing to prioritise email queues and backlogs and had extended the email timeout window to 48 hours to help preserve delayed messages. This is a recovery measure, not a promise that every delayed message will arrive at a particular time or proof that every mailbox has recovered.

The company said it was not aware of malicious activity causing this incident. That is its current assessment, not an independently completed forensic finding. A full root-cause and prevention report is promised after recovery. No guaranteed full-restoration deadline was provided in the checked notice.

OpenAI's status page continued to investigate errors in the Microsoft 365 connector, including failures with new connections and tools not behaving as expected. Anthropic's status notice said the Microsoft incident was causing most mail, calendar and search requests through its Microsoft 365 connector to fail, with Claude for Outlook also affected. These are Microsoft-integration failures, not evidence that all ChatGPT conversations, the entire Claude service or all AI APIs are unavailable.

Anthropic also opened a separate investigation at 8:58pm Sydney time into authentication failures affecting Claude.ai and Claude Code. Its status page listed disruption across Claude.ai, Claude Code and the developer console while the Claude API remained operational. The company had not established that this new authentication incident had the same cause as the Microsoft connector failures.

Earlier reporting retained for context

November 13 evening check: no all-clear; humour follows disruption

Microsoft's public status page continued to show service degradation at the evening check in Sydney. Published reports describe the same developing disruption, not three separate outages. Reports also describe users sharing jokes about using a spreadsheet instead of an email inbox, drawing on a familiar music-video scene. These posts show reactions to the disruption, not evidence that a spreadsheet is a working substitute for Outlook or that the service has fully recovered.

A widespread Microsoft 365 disruption has left users struggling to open Outlook inboxes, send and receive email and connect to other workplace services. Microsoft's public service-health page still listed service degradation when checked on Friday, November 13, Sydney time. Some recovery had been reported, but the company's latest displayed update said affected servers could become unresponsive again when traffic returned. Full restoration was not confirmed.

What Microsoft has confirmed

The official page said users might be unable to connect to multiple Microsoft 365 services. Its potentially affected list included Exchange Online, Teams, SharePoint Online, Microsoft Copilot 365, Defender XDR, Planner, To Do, Intune and Defender for Office 365. It also described disruption to several Purview services, parts of the Microsoft 365 Apps Admin Center and Universal Print. These are potential impacts, not proof that every customer or every feature was unavailable.

There were narrower conditions for some products: the page said Power BI users could intermittently have trouble exporting reports with MIP sensitivity labels to PDF. For Windows 365, the connection issue described applied to customers whose tenant and Cloud PCs were configured to use Microsoft Purview Customer Key. The page separately said no Azure issues had been detected at that time. It would therefore be misleading to describe every Microsoft cloud product as down.

Recovery remains uneven

In the latest update displayed, timestamped November 13 at 00:08:53 UTC, or 11:08:53am in Sydney, Microsoft said servers initially returned to service appeared healthy but could stop responding again after receiving traffic. Networking and platform specialists were examining diagnostic data to identify the trigger. The company said it was temporarily restricting some traffic types in specific locations and rebuilding a subset of affected servers using an earlier software configuration. Wider use of that approach depended on positive results.

Earlier recovery attempts included redirecting traffic, restarting and validating servers, protective traffic management and reviewing recent configuration changes. Limited improvement in some regions did not mean all services had recovered.

What the report totals mean

Outlook problem reports on Downdetector rose to about 130,000 shortly after 1pm US Eastern Time on Thursday, November 12, then fell to about 77,000 just before 3pm. More than 131,000 Outlook reports were recorded around 18:15 GMT. These are time-specific figures from an outage tracker, not a verified total of affected people, organisations or failed messages. Falling reports alone do not prove service has returned for everyone.

Reports described people unable to load inboxes or send and receive email, as well as difficulties using Teams and Copilot. Microsoft said the connectivity issue could affect users in any region. That does not establish that every country or every account was affected equally, nor does it establish a specific impact on any individual reader's mailbox.

Australian organisations report disruption

Australian businesses and government services reported disruption on Friday, November 13. Downdetector recorded more than 4,400 Australian Outlook problem reports by 8:20am and more than 5,500 around 9am. These different time-specific counts are not a census of affected Australians. Service NSW said some transactions in service centres and call centres were unavailable at the time of its statement. Local councils and the ACT government also acknowledged impacts. This does not establish that every office, school or government service was closed.

A Microsoft spokesperson earlier said there was "no indication" the outage had been caused by a cyberattack. Australia's national cyber security coordinator was looking into the outage. Reports dated November 12 in the United States and November 13 in Australia describe the same developing disruption across time zones, not a second separate outage.

Cause and current limits

Microsoft's earlier explanation was that unexpectedly unavailable servers, rather than an overall rise in traffic, shifted load onto the remaining infrastructure. Recent configuration changes were being examined, but a completed root-cause finding was not available in the material reviewed. The reviewed sources did not establish a cyberattack, data theft or permanent loss of email. No guaranteed restoration deadline was given in the status text checked for this report.

Service conditions may change after this check.