Microsoft 365 Outage Spreads Across Services as Recovery Drags On

Microsoft’s disruption has become a wider Microsoft 365 incident, extending well beyond the Outlook access problems that first drew attention on Thursday. As of the company’s 09:57 UTC update on Friday, 13 November, recovery was still under way across affected infrastructure. Microsoft said service was improving in some workloads but remained variable, with capacity not yet back to normal. The outage is now affecting organisations that rely on email-linked functions across Teams, Copilot and a range of security and administration tools.

This is a material development since TechBooky’s first report on the outage. The issue began on 12 November and has continued into the next working day in multiple regions. Microsoft’s incident messages, mirrored by the University of Pennsylvania, list the broad Microsoft 365 event as MO1550821. They say features that interact with Exchange Online and email are affected, while parts of those same products that do not depend on Exchange may still work. That distinction is important: the incident is not proof that every Microsoft service is completely offline.

Exchange Online users may be unable to reach mailboxes through Outlook on the web, desktop Outlook, mobile sync or other connections. Email delivery may also be delayed. Microsoft says Teams’ core calls and group chats largely remain available, but calendars, meeting scheduling and other Exchange-dependent functions can fail. Copilot Chat may not load or may be unable to use work data such as email, files and calendars. Microsoft Graph requests for Exchange data can time out, which may disrupt applications built on top of those APIs.

The company’s impact list also includes Microsoft 365 admin pages, Planner, To Do, parts of Power Apps, Intune, Purview and Defender. Some SharePoint external sharing features and labelled Power BI exports may be affected. For IT teams, these are not merely inconvenient user-facing errors. Trouble with administration, security policy evaluation and audit-related services can complicate the work of managing the incident while it is happening. The affected features differ by product and customer, and Microsoft has not said that all users experienced every problem.

The Associated Press reported disruption to businesses and some government operations as the incident spread across time zones. That real-world impact explains why the story has moved beyond an Outlook headline. A missed email can delay a decision; a failed calendar or workflow integration can stop a meeting, approval or service request. The dependency between Exchange and other Microsoft 365 products is becoming visible at scale.

Microsoft says engineers have been draining traffic from affected infrastructure, restarting and remediating systems, then returning them to service in stages. Earlier changes did not deliver the expected improvement. The company has also worked on network and traffic management while monitoring whether restored capacity stays stable as users reconnect. Its latest note described incremental improvement rather than a completed fix.

Email is a particular concern because delayed messages can accumulate while access is unreliable. Microsoft says it is prioritising queues and backlog processing and has extended an email timeout window to 48 hours to help preserve delayed mail during recovery. That should not be mistaken for a promise that every message will arrive within 48 hours; it is a mitigation intended to reduce the risk of mail being lost while systems stabilise.

The company says it has no evidence of malicious activity associated with this incident. It has not published a full root-cause report, so claims that a cyberattack caused the outage would be premature. Microsoft says it will issue a post-incident report after mitigation is complete. Organisations should follow the official Microsoft service-health page and their tenant-specific admin-centre notices for the most relevant status, since the experience may differ across regions and services.

For now, the practical response is to avoid treating a falling complaint count as proof of full recovery. Administrators should check delayed mail and automated workflows as access returns, and keep alternative contact routes available for urgent work. The central question is not just when Outlook opens again, but when the connected services and queued messages operate reliably end to end.