Quick Answer
Microsoft 365 administrators can check their tenant’s service-health records to identify affected services, user impact and recovery updates after the November 2026 outage.
In This Article
What Happened
9to5Mac reported that more than 80% of Microsoft’s servers were unresponsive at the outage’s lowest point. Microsoft identified a latent defect introduced in July, the failure of one of two independent network gateways, and reduced gateway capacity as contributing factors.

According to Charles Lamanna, Microsoft’s Executive Vice President of Copilot, Agents, and Platform, approximately 15 hours before the outage, Teams failed over from the alternative networking gateway to the gateway that also supports Exchange Online.
Microsoft classified the incident as a service degradation rather than a cyberattack.
Are You Affected?
Service health covers Exchange Online, Outlook on the web, Teams, and other Microsoft 365 services.

Microsoft 365 administrators should sign in to the Microsoft 365 admin center, open Health and then Service health, and review the active incident. The tenant-specific dashboard lists Status, User impact, Affected services, Last updated and All updates, as well as an estimated recovery time when Microsoft provides one.
Teams impact varies by tenant, so administrators should check whether Teams appears under Affected services for their organization. Cross-service behavior involving Exchange may be affected even when unrelated Teams functions remain available.
What to Do Now
- Open Health, then Service health in the Microsoft 365 admin center and review the relevant Outlook, Exchange or Teams incident. If the admin center is unavailable, use the public Microsoft service health status page.
- Check the Affected services and User impact fields for your tenant, then compare them with the services and locations your organization used during the incident.
- Review Microsoft 365 administration reports for delayed or failed email delivery, unavailable applications and connectivity errors.
- Enable incident notifications through Manage notifications for the issue, or configure them under Service health, Customize and Email.
- Keep records of affected users, services and operational interruptions for internal review and any applicable customer or regulatory notifications.
Microsoft’s service-health guidance advises administrators not to reinstall Outlook, recreate profiles or clear Teams caches while the issue remains an active Microsoft-side service incident.
What the Evidence Shows
It remained deployed worldwide for more than three months before the failure. Microsoft said its normal load testing did not detect the latent issue because the test labs used a different traffic and hardware mix.
Microsoft said that capacity was scheduled to return through routine maintenance and health processes and that the service had sufficient capacity headroom, so the reduction had no impact on its own.
Key Considerations
- The July change had operated worldwide for more than three months without impact before the failure appeared under particular load conditions.
- Normal load testing did not reproduce the issue because of differences between test traffic, hardware and production conditions.
- Microsoft reported no indication of malicious activity and did not attribute the incident to a cyberattack.
- Several Microsoft 365 products were affected, so checking only email may not capture the full operational impact.
FAQ
What Caused the Microsoft 365 Outage?
Microsoft identified a latent defect from a July change, the failure of one of two network gateways, and reduced server capacity as contributing factors.
How Many Microsoft Servers Failed?
Microsoft also reported that nearly 14% of networking gateway capacity was unavailable because of an unrelated issue from the previous day.
Was the Microsoft 365 Outage a Cyberattack?
Microsoft said there was no indication of malicious activity and classified the event as a service degradation.
Which Microsoft 365 Services Were Affected?
Service health covers Exchange Online, Outlook on the web, Teams, and other Microsoft 365 services.
Why Did Service Restoration Take so Long?
Microsoft said it was taking longer than expected to fix the problem.
Sources
See our editorial disclaimer for how our articles are produced.
Run a free scan to see your AI Visibility Score, SEO rating, and local citation accuracy.