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 19:53 UTC, left the provider's feed by 13 Oct 21:07 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 19:53 UTC User impact: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center. More info: Users may also see nothing in the "What's new" tab in the Microsoft Teams admin center and are returned an error stating "We can't load data. Try again." Current status: We're continuing to monitor recovery, and we anticipate some users will start to see remediation at this time. To ensure impact is fully remediated, we've extended our monitoring period, and we anticipate impact to be resolved by our next scheduled update. Scope of impact: This issue affects some admins who may be unable 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. This section may be updated as the investigation progresses. Start time: Monday, October 12, 2026, at 9:54 PM UTC Estimated time to resolve: We anticipate impact to be resolved by Tuesday, October 13, 2026, at 10:00 PM UTC. Root cause: A recent service update introduced a misconfiguration which causes the Service Health and Communications API to return authentication errors, resulting in impact. Next update by: Tuesday, October 13, 2026, at 10:00 PM UTC
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
- GitHub [Retroactive] Actions workflow run logs delayed
- Cloudflare Network Performance Issues in LAX
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.