Miscellaneous topics that do not fit into specific categories.
Microsoft is reporting an active Microsoft 365 service degradation on November 13, 2026, and customers should monitor Microsoft 365 admin center → Health → Service health for tenant-specific recovery updates rather than troubleshoot individual devices.
Microsoft’s public status feed reports that a core process on affected servers became overwhelmed, causing servers to stop responding and reducing service capacity. Mitigation includes isolating infrastructure, restarting affected components, rerouting traffic, and gradually returning servers to service; limited recovery has been observed in some regions, but restoration is not yet universal.^1^
Check the status affecting your tenant
- Sign in to the Microsoft 365 admin center with an administrator account.
- Open Health → Service health.
- Under Active issues Microsoft is working on, select the relevant incident.
- Review User impact, Affected services, Status, and All updates.
Service health is tenant-aware and therefore provides more precise information than the public status page. Service Support admins and Helpdesk admins can also view it.^2^
If the admin center is unavailable, use Microsoft’s public service status page. That page is intended as the fallback when an incident prevents access to the admin center or its Service health functionality.^3^
What to do now
- Avoid making broad tenant, identity, DNS, or client configuration changes while the incident remains active.
- Record the incident ID and timestamps for internal tracking.
- If your symptoms are not listed in Service health, select Report an issue there.
- If the incident is already listed, Microsoft advises following its Service health updates rather than opening a duplicate support request.^3^
- After restoration, check Health → Service health → Issue history for the final update or any published post-incident report.^2^
References