Service degradation
Microsoft 365 admin center · degraded service
Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center
Posted 13 Oct 21:02 UTC, left the provider's feed by 13 Oct 22:38 UTC.
Unknown
Duration: the provider stated no start
6Other incidents at the same timeWhat it affected
As the provider names itWhat the provider posted
Newest first- 13 Oct 21:02 UTC User impact: Admins may have been unable to review Service health or Message center postings in the Microsoft 365 admin center. More info: Admins' "What's new" tab in the Microsoft Teams admin center may have been blank and displayed an error stating, "We can't load data. Try again." Final status: We've completed our monitoring period and validated that the rollback of the service update containing the misconfiguration successfully remediated impact. Scope of impact: This issue affected some admins attempting to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. Start time: Monday, October 12, 2026, at 9:54 PM UTC End time: Tuesday, October 13, 2026, at 7:35 PM UTC Root cause: A recent service update introduced a misconfiguration which caused the Service Health and Communications API to return authentication errors, resulting in impact. Next steps: - We're analyzing the offending service update to determine why the potential for impact wasn't caught during our internal update testing and validation phases. This further analysis will help us to improve our update implementation processes moving forward to ensure similar impact scenarios don't occur in the future. This is the final update for the event.
Around it
From the sources ChangeIntel reads; a match in time is not a causeElsewhere at the same time
- Cloudflare Audit Logs v2 ingestion is missing multiple Cloudflare products
- GitLab.com Increase of HTTP 50X errors on GitLab.com
- Cloudflare Elevated Errors in China Network Colos
- Cloudflare Cloudflare One Clients are incorrectly challenged on some sites
- Cloudflare Network Performance Issues in LAX
- GitHub [Retroactive] Actions workflow run logs delayed
What changed
First observed 14 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.
Keep track
- Service status now: every provider ChangeIntel reads, with ongoing incidents first.
- Status RSS feed: new and ended incidents as they happen.