Microsoft 365 Outage Disrupts Outlook, Teams and Copilot Worldwide

A major disruption to Microsoft 365 affected users around the world, interrupting access to services including Outlook, Microsoft Teams and Microsoft Copilot. The incident began on Thursday, November 12, and continued into Friday as Microsoft worked to restore affected infrastructure.

The disruption showed how closely connected today's workplace applications have become: when shared cloud infrastructure experiences problems, several familiar services can be affected at the same time.

Which Microsoft services were affected?

Reports and service-health updates described problems across several Microsoft 365 products and features, including:

• Outlook and Exchange Online: Some users could not access mailboxes, send or receive messages, or use certain connection methods. Email delivery was delayed for some customers.
• Microsoft Teams: Some features that rely on Exchange Online, including calendar and meeting-related functions, were affected. The impact was not identical across all Teams features.
• Microsoft Copilot for Microsoft 365: Some users experienced problems loading Copilot Chat or accessing work information such as email, calendars and files.
• Other connected services: Microsoft reported effects on selected features in services such as SharePoint, Planner, To Do, Power BI and security administration tools.

The exact impact varied by service, region and connection method. It is therefore inaccurate to say that every Microsoft 365 product was completely unavailable. Associated Press coverage and Microsoft service-health incident details describe the reported scope.

What caused the Microsoft 365 outage?

Microsoft's updates attributed the disruption to infrastructure and server problems associated with Exchange Online and connected Microsoft 365 services.

The company said a number of servers became unexpectedly unavailable, placing additional pressure on the remaining infrastructure. Microsoft also described problems with server health checks and a core process on affected servers becoming overwhelmed.

Its recovery work included restarting and rebuilding affected servers, adjusting traffic flows, limiting certain traffic in some locations and gradually returning infrastructure to service.

Microsoft said it had found no evidence that malicious activity caused the incident. The company indicated that a fuller post-incident report would follow after mitigation. The precise root cause should not be described as finally established until that report is published. Microsoft incident updates reproduced by the University of Pennsylvania

How many users were affected?

The total number of affected users was not publicly established in the reporting reviewed for this article.

The Associated Press reported that Downdetector received outage reports from 74 countries and territories within about an hour of the disruption emerging. This indicates the incident had a broad geographic reach, but it does not mean that every user in those locations was affected.

Microsoft previously reported having more than 450 million paid commercial Microsoft 365 subscriptions. That figure represents its customer base, not the number of people affected by this particular outage. Associated Press

Is Microsoft 365 back online?

Microsoft reported improving service availability and email delivery during Friday, November 13. It also warned that some users could continue to experience intermittent access problems or delayed messages while recovery progressed.

Status note — November 14, 2026: This article describes the recovery information available in the cited reports and incident updates. Service status can change, and readers should check Microsoft's official service-health page for the latest information. Do not treat an earlier recovery update as confirmation that every service and region is fully restored.

What does this outage reveal about cloud services?

DailyBox Pulse analysis

Cloud platforms make it possible for organisations to use email, collaboration, file storage and AI tools without maintaining all the underlying infrastructure themselves. But this convenience also creates dependencies.

When several applications rely on shared services, a failure in one part of the platform can affect multiple products. The result can reach beyond missed emails: organisations may experience delays in meetings, workflows, customer communication and other operations.

The incident is a reminder that businesses should plan for temporary service interruptions. Practical steps include:

• Maintaining an alternative way to contact colleagues, customers and suppliers.
• Keeping important business processes documented outside a single cloud platform.
• Understanding which critical workflows depend on the same provider.
• Backing up important data and testing recovery procedures.
• Checking official service-status updates before assuming a disruption has ended.

These precautions do not eliminate outages, but they can reduce the operational impact when a major service becomes unavailable.

Frequently asked questions

What happened to Microsoft 365?

A global service disruption affected Outlook, Teams, Copilot and other Microsoft 365 services beginning on November 12, 2026. Microsoft worked to restore affected server infrastructure, with recovery progress reported on November 13.

Was Outlook down worldwide?

Outlook experienced widespread access and email-delivery problems. Reports came from many countries, but the impact varied by region and user. It is more accurate to describe this as a global disruption than to claim that Outlook was unavailable to every user worldwide.

Did the outage affect Microsoft Teams and Copilot?

Yes. Microsoft and news reports described issues affecting Teams and Microsoft 365 Copilot. Some Teams features that depend on Exchange Online were affected, while not every Teams feature necessarily stopped working.

Was the Microsoft outage caused by a cyberattack?

Microsoft said it had no evidence of malicious activity causing the incident. Its reported investigation focused on server availability, health checks and infrastructure recovery.

Where can I check Microsoft 365 service status?

Use Microsoft's official service-health page. Organisations with Microsoft 365 administrator access can also review detailed service-health information in the Microsoft 365 admin center.