What happened
Microsoft reported continuing recovery work on Friday evening after a worldwide disruption to its Microsoft 365 workplace services. Its public status update at 20:02 UTC on 13 November said infrastructure was stabilising, but queued messages were still being processed and traffic redistributed. The company gave no estimate for full recovery.R1
The update made a distinction between regaining access and receiving delayed messages. Customers might find that sign-in works again before email delivery returns to normal, Microsoft said. That means a successful login does not, by itself, establish that all mail has arrived.R1
Microsoft listed possible problems accessing Exchange Online mailboxes through Outlook and other connections. It also described effects on parts of Copilot, administration tools and other services. Its account specifically said functions that did not depend on Exchange Online could remain available.R1
Why it matters
The impact varied within individual products. Microsoft said most core Teams functions, including calls, meetings and ordinary channel messages, were unaffected, while calendar and scheduling functions could fail. It also said direct access to files stored in SharePoint remained functional, despite possible problems with external sharing.R1
UK public bodies’ notices likewise describe disruption without reporting a complete halt to their work. The Maritime and Coastguard Agency said it had problems sending and receiving email. It expressly said search and rescue services were unaffected.R2
The Security Industry Authority said some systems were affected, including those supporting its ACS approval processes, and responses could be slower. It said it could still grant, refuse, revoke and suspend licences. Its notice also warned that incoming and outgoing emails could be delayed. It said it was monitoring the situation.R3
The background
Central and North West London NHS Foundation Trust initially warned that Outlook and Teams messages might not reach their recipients. Its advice asked staff to use other communication methods and business continuity plans. However, a 4.50pm update on the same page said the issue had been resolved and people could contact its teams normally.R4
That local resolution does not establish worldwide recovery. The trust’s notice concerns its own services, while Microsoft’s later evening bulletin still listed degradation across its affected products. The two updates describe different scopes and should be read with their publication times in mind.R1R4
What happens next
Microsoft scheduled its next public update by midnight UTC on 14 November. The evening bulletin did not provide a complete recovery time or a final explanation of the underlying cause. Continued access improvements and the clearance of delayed messages remain separate measures of recovery.R1