A major Microsoft 365 outage that began on 12 November 2026 has disrupted Outlook, Exchange Online, Microsoft Teams, Copilot and several connected cloud services. Microsoft says the incident is infrastructure-related and has found no indication of malicious activity. Recovery work is continuing on 13 November, with service improving but not yet fully restored everywhere.
Latest update – 13 November 2026, 19:35 GMT
Microsoft’s public service-status page is now showing all products operational, indicating that the major Microsoft 365 outage has moved out of active service degradation. KES email service is also restored. Some delayed messages may still arrive as Exchange Online finishes clearing queues and backlogs, so businesses should allow time for email delivery to normalise before treating individual late messages as a separate fault. Microsoft has continued to report no evidence of malicious activity associated with the incident.
What is happening with Microsoft 365?
Microsoft is dealing with a broad Microsoft 365 service incident centred on Exchange Online and infrastructure used by other cloud services. Users have reported problems sending and receiving email, opening mailboxes and using features in Teams, Copilot and other Microsoft 365 services that depend on Exchange or Microsoft Graph.
The disruption began on Thursday 12 November and continued into Friday morning. Microsoft has been restoring affected infrastructure and increasing available capacity, but the recovery has taken longer than initially expected.
Which Microsoft 365 services are affected?
The impact has varied by user and region, but the incident has affected more than just Outlook. Microsoft and independent reporting have identified disruption across Exchange Online and services that rely on the same Microsoft 365 infrastructure.
- Outlook and Exchange Online: problems accessing mailboxes, sending or receiving messages, and delays in email delivery.
- Microsoft Teams: some calendar, scheduling and Exchange-connected features have been affected, although core chat and meetings may continue to work for many users.
- Microsoft 365 Copilot: some users have experienced problems accessing Copilot Chat and work data.
- Microsoft Defender and Purview: some security and compliance experiences have also been affected.
- Microsoft Graph and connected apps: services that rely on Microsoft Graph or Exchange data may experience knock-on failures.
- Planner, To Do and other Microsoft 365 services: functionality can be affected where it depends on the impacted infrastructure.
What has Microsoft said caused the outage?
Microsoft has said the incident is linked to infrastructure problems and elevated load affecting servers and health-processing components. Engineers have been working to stop additional servers being affected, restore unhealthy infrastructure and increase service capacity.
Microsoft has also said it has no indication that the outage is the result of a cyberattack. The exact root cause may not be confirmed until Microsoft publishes its final post-incident review.
Is Microsoft 365 back online?
Yes. Microsoft’s public status page is now showing all products operational. Some users may still see delayed email or residual symptoms while Exchange Online clears queues and downstream services catch up, but the major service degradation is no longer being reported publicly.
Microsoft 365 administrators can check the tenant-specific Service health dashboard. If the admin centre itself is unavailable, Microsoft also provides a public service-status page.
Should users reset passwords or reinstall Outlook?
No. If the problem is caused by the Microsoft 365 service incident, resetting passwords, recreating Outlook profiles or reinstalling Office is unlikely to help and may create additional work once the service recovers. Check service health first before making local changes.
If only one user or one device remains affected after Microsoft reports recovery, normal troubleshooting may then be appropriate. During an active service incident, however, widespread symptoms are more likely to be Microsoft-side than a fault with an individual PC.
What should businesses do during the outage?
Businesses should focus on continuity rather than repeatedly troubleshooting systems they cannot control. Confirm the outage through Microsoft service health, tell staff what is affected, and use agreed alternative communication methods for urgent work.
- Use phone, SMS or another approved communication channel for urgent messages if email is unreliable.
- Do not repeatedly resend the same email unless necessary; delayed messages may still be delivered when queues recover.
- Avoid unnecessary password resets, Office reinstalls or profile rebuilds while the incident remains active.
- Record any critical business actions that must be completed later if a cloud application is temporarily unavailable.
- Keep staff updated so the helpdesk does not receive multiple reports for the same Microsoft-side incident.
- Check Microsoft 365 Service health for tenant-specific updates and recovery information.
Why does this outage matter for business continuity?
Microsoft 365 is highly resilient, but no cloud service is immune to outages. When email, collaboration and cloud applications depend on the same provider, one incident can affect several business processes at once. The practical lesson is to plan for temporary loss of service rather than assume it can never happen.
KES has previously covered how to keep your business running when Microsoft 365 goes down. That guide covers alternative communications, local copies of essential information and simple continuity planning for cloud outages.
It is also worth reviewing what happens when your business internet connection fails, because cloud-service resilience and connectivity resilience are related but separate risks.
What should KES customers do?
KES customers do not need to make changes simply because Microsoft 365 is experiencing an outage. If Microsoft is reporting a service incident, the priority is to wait for recovery and use alternative communication channels where necessary. If a problem continues after Microsoft confirms recovery, raise a support ticket so we can check whether anything local still needs attention.
Quick answers
Is Outlook down because of my computer?
If multiple users are affected at the same time and Microsoft is reporting a service incident, the problem is likely Microsoft-side rather than a fault with your PC.
Is the Microsoft 365 outage a cyberattack?
Microsoft has said it has no indication of malicious activity. The incident is currently being treated as an infrastructure and service-capacity problem.
Will delayed emails eventually arrive?
In many service incidents, queued messages are delivered as Exchange Online recovers, although delays can continue while backlogs clear. Avoid repeatedly resending important messages unless you have confirmed they failed.
Where can I check Microsoft 365 service status?
Microsoft 365 administrators should use the Service health dashboard in the Microsoft 365 admin centre. Microsoft also provides a public service-status page for major incidents when admin access is affected.
Sources
- Microsoft Learn: How to check Microsoft 365 service health
- Associated Press: Microsoft struggles to restore services as outage hits companies and governments worldwide
- Microsoft Service Status
Information checked 13 November 2026. Microsoft 365 service incidents can change quickly, so current Service health information should be checked before taking troubleshooting action.