Microsoft 365 Outage Cuts Off Outlook, Teams and Copilot Worldwide
13 November 2026· AFQY News

New Zealand woke on Friday to a quiet inbox, and for once it was not good news. From just before 7.30am, people across the country and around the world found they could not reach Outlook, Teams, SharePoint or Copilot. Microsoft confirmed a widespread Microsoft 365 outage and said users in any region could be affected.
As of Microsoft’s latest update, at 10.01am New Zealand time, the outage was continuing but recovery had begun. Microsoft said a large number of its servers had become unexpectedly unavailable, and that a new way of checking their health had let some of them return to service. It was rolling that change out more widely.
This is a developing story. We will add updates below as Microsoft reports progress, each marked with the time.
Updated at 1.30pm, Sunday 15 November 2026
Microsoft says its services have recovered. On its status page for consumer services such as Outlook.com, Microsoft’s final update said services across the affected environments had fully recovered and the backlog of email messages had been processed. It recorded that incident as ending at 5.10am on Saturday, New Zealand time. By Saturday evening its public status page for business customers had returned to its normal message, with no active incident listed.
Recovery came in stages overnight on Friday. At about 3pm on Friday Microsoft said restarting the affected servers was showing signs of improvement, though it was still monitoring their stability. By early Saturday it was reporting “encouraging recovery progress”, with service availability and email delivery improving across a growing share of the affected infrastructure, and it had extended its email timeout to 48 hours to help preserve delayed messages. By Saturday morning email queues were significantly reduced and approaching normal levels, though some users could still see intermittent problems or delayed email.
Microsoft has also said there is no sign of an attack. “At this time, we have no evidence of malicious activity associated with this incident,” its status page said. It has not yet said what caused that secure-connection process to become overwhelmed. It has promised a full Post-Incident Report, with the root cause and the defence-in-depth actions it will take, once mitigation is complete.
"We know our customers rely on our services to get important work done every day, and regret the impact these outages had on those who depend on us. Our teams are reviewing what happened and how we can prevent similar issues going forward."
The timeline below sets out how the outage unfolded, in New Zealand time.
Updated at 2.30pm, Friday 13 November 2026
Microsoft has narrowed down the cause. In its update at 2.06pm New Zealand time, it said a process on the affected servers that is responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests.
Microsoft also said it had begun reverting a recent network configuration change that correlates with the start of the outage, and was monitoring to see whether that helps recovery. Earlier on Friday it had said none of its recent changes lined up with the start of the problem, before identifying a small number of configuration updates as possible contributors.
It is preparing a configuration change that can be applied across all the affected servers to fix the behaviour, and is testing it on a subset first before applying it more widely, alongside restarts of the affected infrastructure. The temporary traffic limits it described earlier are now in place in some locations, where it is watching whether servers stay stable while handling fewer connections before gradually letting more traffic back in. Its next update is due by 3pm.
What still works. Microsoft has also published a clearer list of what is affected. The problems are with features that depend on Exchange Online, its email service, and parts of its services that do not depend on Exchange Online keep working. In practice:
- Email is hit hardest. Users may be unable to reach their mailbox through Outlook on the web, the Outlook desktop app, phone mail apps or other connected apps, and email delivery may be delayed.
- In Teams, chat and online meetings remain largely functional, but features that rely on Exchange Online, such as calendars and scheduling meetings, may fail. For staff, Teams chat may be the quickest way to stay in touch while email is down.
- Files stored directly in SharePoint can still be opened, though features that depend on Exchange Online may not work.
- Copilot Chat may not load or respond, and Copilot may be unable to reach work data such as email, calendars and files.
- Safe Links in Microsoft Defender for Office 365 may be unable to check web addresses, which can affect people clicking links in Outlook and Teams.
- Schools using Microsoft 365 Education may find Assignments, Reading Progress and Speaker Progress affected.
- Apps that read email, calendars or contacts through Microsoft Graph may time out.
Microsoft’s list also includes Intune, Planner, To Do, Purview, Universal Print, some Microsoft 365 admin centre pages, exports of reports with sensitivity labels in Power BI and Microsoft Fabric, and Windows 365 Cloud PCs set up to use Microsoft Purview Customer Key.
Updated at 12.50pm, Friday 13 November 2026
Microsoft says recovery has started, but slowly. In its update at 12.06pm New Zealand time, it said it had begun returning some of the affected servers to service and that they were staying stable so far. It had also shifted traffic and connections onto other pathways where it could, and was seeing limited recovery in some regions.
Microsoft said it had streamlined its recovery process to bring the remaining servers back faster. It is also applying protective traffic management in one location to reduce the load on the affected infrastructure, and will extend that to other locations if it works. As capacity returns, users may see service come back gradually as their apps reconnect. Its next update is due by 1.30pm.
An hour earlier the news was less hopeful. At 11.11am Microsoft said the steps it had taken so far had not brought the relief it expected. It had found that a core process on the affected servers was becoming overwhelmed, which made the servers stop responding and added to the loss of capacity. To test a recovery approach, it was fully isolating part of its infrastructure, restarting the affected components and gradually letting traffic back in, to confirm services stayed stable before applying the approach more widely. It was also looking at whether isolating traffic within each region would let regions recover independently.
Microsoft has not said what caused the process to become overwhelmed, or whether rolling back the recent configuration updates it was assessing at 10.41am made a difference. Its current list of affected services also includes Microsoft Intune, Microsoft Defender for Office 365 and Universal Print, along with report exports in Power BI and parts of the Microsoft 365 Apps admin centre.
Updated at 10.55am, Friday 13 November 2026
In its update at 10.41am New Zealand time, Microsoft said it was still restarting and validating the affected servers to return them to service safely, and was looking for ways to speed that up. It was also assessing whether rolling back the small number of recent configuration updates it had identified could help recovery. Its next update is due by 11.30am.
TL;DR
- A Microsoft 365 outage began at 7.26am New Zealand time on Friday 13 November (1.26pm US Eastern time on Thursday), affecting users worldwide. Recovery came in stages overnight, and by Saturday morning Microsoft said email queues were approaching normal levels.
- Microsoft said the features affected were those that depend on Exchange Online, its email service. Email was hit hardest; Teams chat and online meetings remained largely functional, and files stored in SharePoint could still be opened. Copilot, Defender, Intune, Planner, To Do, Purview, Universal Print and some Microsoft 365 Education features were also affected.
- Microsoft found that a process on its servers that establishes secure connections was becoming overwhelmed, and began reverting a recent network configuration change that lined up with the start of the outage. It says it has no evidence of malicious activity, and will publish a Post-Incident Report with the root cause.
- Microsoft’s consumer status page records the incident there as ending at 5.10am on Saturday, New Zealand time, with services fully recovered and the email backlog processed.
- In New Zealand, Downdetector reports began at about 6.30am on Friday, and RNZ reported more than 130,000 outage reports early that morning.
- Administrators can follow the incident, and the Post-Incident Report when it is published, under advisory MO1550821 in the Microsoft 365 admin centre.
Timeline: how the outage unfolded
All times are New Zealand time.
Friday 13 November
- 3.45am to 4.53am. A separate Teams incident affects users in North and South America. Microsoft later says it is fully resolved, and does not say whether it is linked.
- About 6.30am. Users begin reporting problems on Downdetector, the NZ Herald reports.
- 7.26am. Microsoft records the start of the Microsoft 365 incident (1.26pm US Eastern time on Thursday). It first blames elevated load across several regions, then says the load comes from servers becoming unexpectedly unavailable, not from more traffic.
- Just before 9am. Microsoft says affected servers are failing automated health checks, and tests a workaround that bypasses the component processing them.
- 9.44am. Many affected servers become unresponsive during testing. Microsoft restarts them with the change in place.
- 10.01am. An alternative health check lets some servers return to service. Microsoft is investigating a small number of recent configuration updates.
- 10.41am. Microsoft is still restarting and validating servers, and assessing whether rolling back those configuration updates would help.
- 11.11am. Microsoft says its fixes have not brought the relief it expected. A core process on the affected servers is becoming overwhelmed.
- 12.06pm. Some servers are back in service and stable. Traffic has moved to other routes, and some regions see limited recovery.
- 2.06pm. Microsoft traces the problem to a process that establishes secure connections, begins reverting a recent network configuration change that correlates with the start of the outage, and puts temporary traffic limits in place. Its list of affected services now shows what still works, including Teams chat and meetings.
- About 3pm. Restarting the affected servers is showing signs of improvement, though Microsoft is still monitoring their stability.
Saturday 14 November
- By 2am. Microsoft reports “encouraging recovery progress” and extends its email timeout to 48 hours to preserve delayed messages.
- 5.10am. The end time Microsoft later records for the incident on its consumer status page, with services fully recovered and the email backlog processed.
- By 6am. Email queues are significantly reduced and approaching normal levels. Microsoft says it has found no indication of malicious or cyber activity.
- 6.42pm. Microsoft’s public status page for business customers returns to its normal message.
Still to come: Microsoft’s Post-Incident Report, with the root cause.
What happened
The trouble started overnight in the Americas. Microsoft first investigated reports of Exchange Online mailbox connection problems there, and a separate Teams incident affected users in North and South America between 3.45am and 4.53am New Zealand time, according to BleepingComputer. Microsoft has said the earlier Teams problem was fully resolved, and has not said whether the two incidents are related.
Reports of Outlook problems on Downdetector began to spike just before 1pm US Eastern time on Thursday, which is just before 7am on Friday in New Zealand, The Verge reported. Microsoft records the start of the Microsoft 365 incident at 1.26pm Eastern, or 7.26am New Zealand time. It soon confirmed that the problem was not limited to the Americas and that users in any region could be affected.
In Australia, where it was early on Friday morning, the ABC opened a live blog for readers unable to reach their email.
In New Zealand
Users worldwide began reporting problems on Downdetector at about 6.30am New Zealand time, the NZ Herald reported, adding that much of New Zealand’s systems appeared to be affected. RNZ reported more than 130,000 reports of problems on Downdetector early on Friday, noting that the actual number of affected users may vary.
Paul Spain, chief executive of Gorilla Technology, told the Herald the outage would be very embarrassing for Microsoft.
"So much of New Zealand's business relies on Microsoft's infrastructure, and when they break, they have a massive impact, not just on individual businesses but on the entire economy because it's breaking productivity."
Spain said it was a reminder for businesses to safeguard their systems. Moving everything from one vendor to another would leave a business in the same position, he said, and he suggested having more than one channel for critical functions so that a business does not grind to a halt.
What Microsoft says caused it
Microsoft’s first explanation was that part of its infrastructure was under elevated load across several regions. It then corrected that.
"We determined the elevated load isn't driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure."
Microsoft said it had paused all deployments, redistributed connection traffic across its worldwide infrastructure, moved more traffic away from the affected systems, and begun restarting servers to bring capacity back.
A later update narrowed the search. Microsoft said it had not identified any recent changes that lined up with the start of the problem, but that the failed health checks taking servers out of service may come from a specific component on those servers that processes the checks. It began deploying a targeted change to bypass that component on a subset of servers to see whether that restored them, took steps to stop more servers being removed from service, and started looking into why the affected servers were using unusually high amounts of processor time.
In its update at 9.44am New Zealand time, Microsoft said that while it was testing that change, many of the affected servers had become unresponsive, which stopped it confirming whether the change worked. It said it was restarting those servers so they would come back online with the change in place, and applying the same approach to other affected parts of its infrastructure.
By 10.01am the news was better. Microsoft said it had validated an alternative health check method on a subset of the affected infrastructure, which allowed those servers to return to service, and that it was applying the change more broadly. It was also preparing an automated process to keep detecting and restarting unresponsive servers while the change rolled out. And its review of recent changes had found a small number of configuration updates that it is investigating as potential contributors.
Knock-on effects
The outage reached beyond Microsoft’s own apps. OpenAI said it was investigating a problem with its Microsoft connectors, and Anthropic said an issue with an upstream provider was affecting its Microsoft 365 connector, the ABC reported. Tools that link to Microsoft 365 for email, calendars or files can stop working when Microsoft 365 does, even if the tool itself is running normally.
What tech leaders can do now
For most organisations there is nothing to fix at their end. The useful work is keeping people informed and avoiding changes that make the picture harder to read:
- Follow advisory MO1550821 in the Microsoft 365 admin centre, and Microsoft’s public status page at status.cloud.microsoft.
- Tell staff and customers what is happening through a channel that does not depend on Microsoft 365, such as text messages, an intranet hosted elsewhere, or the phone.
- Hold off on troubleshooting changes to local networks, devices or accounts, since the cause sits with Microsoft.
- Note which teams and services stopped, and for how long. That record will be useful when reviewing how dependent the organisation is on a single provider.
We will update this story as Microsoft reports progress.
Sources
- Microsoft: Microsoft 365 service health status
- BleepingComputer: Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide
- SecurityWeek: Microsoft 365 outage disrupts Outlook, Exchange Online and Teams
- The Verge: Microsoft Outlook is down
- ABC News: Live, Microsoft outage affects users worldwide, impacting Teams, Outlook and Copilot
- RNZ: Global outage hits Microsoft's Outlook
- NZ Herald: Microsoft investigates reports of Outlook mailbox access problems
- Microsoft: Azure status
- IBM: The IBM PC
- Computer History Museum: Microsoft MS-DOS early source code
- Computer History Museum: Xerox Alto source code
- The Digital Antiquarian: The IBM PC, part 2
- Computer History Museum: Fifty years of the personal computer operating system
- IEEE Spectrum: Did Bill Gates steal the heart of DOS?
- Doug Engelbart Institute: Doug's great demo, 1968
- Wikipedia: Apple Lisa
- Wikipedia: FingerWorks
- Apple: Apple reinvents the phone with iPhone (9 January 2007)
