Microsoft’s official statement on the current major outage (as of November 13, 2026):
We are deeply sorry for the disruption this incident has caused our customers and partners. We know the trust they place in our services and take that responsibility extremely seriously. We are seeing broad recovery and stability across our services.
This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. We have addressed the underlying issue and continue to restore service to remaining customers and regions.
Given the scale of demand, we restored services gradually, validating stability at each stage. While this took longer, it helped ensure a stable restoration.
We will provide a full post-incident report once our review is complete.
This statement was posted by the official @Microsoft and @MSFT365Status accounts on X on November 13, 2026. The outage, which began around midday Thursday (November 12) and has lasted roughly 24 hours, has disrupted Microsoft 365 services including Outlook/Exchange Online, Teams, SharePoint, Copilot, and related tools for users worldwide.
Key points from Microsoft:
- Not caused by a cyberattack, malicious activity, or AI/agents.
- Root cause tied to a technical issue from an earlier network capacity upgrade that appeared after a recent network change.
- Underlying issue has been addressed; recovery is proceeding in stages for stability.
- Broad recovery and stability are being observed, though some users may still see intermittent access issues or delayed email delivery as queues clear and traffic is rebalanced.
- A full post-incident report is promised after the review.
Microsoft’s public service health status page (status.cloud.microsoft) continues to list service degradation for Microsoft 365, noting that some users may be unable to connect to multiple services. Latest status updates indicate infrastructure is stabilizing, with improved sign-in/access in places, but no firm ETA yet for full normalization of mail flow.
For the most current details, check the official Microsoft 365 Status account (@MSFT365Status), the service health page, or the Microsoft 365 admin center (incident references such as MO1550821 / EX1550543 have been cited in updates).
