Fabric customers in the North Central US region may experience issues with capacity management operations.
At a glance · Microsoft's status
ResolvedLasted 16 h 46 min
- Microsoft says it started
- · on Microsoft Fabric support
- Earliest version we archived
- · our archive started 15:47 UTC, 13 Nov
- Ended
- · marked resolved
- Affects
- Microsoft Fabric
- Edited
- Not since we first saw it
- Source
- Microsoft Fabric support · checked 10 min ago
In short
Microsoft reported degraded service affecting Microsoft Fabric, starting 10:59 UTC on 25 Aug. Microsoft marked it resolved at 03:45 UTC on 26 Aug after 16 h 46 min. Microsoft has since published a post-incident report.
Microsoft says
Microsoft's latest update, , in short excerpts.
What happened?
Timeline
Times in UTC, Microsoft's own where it gives them.
25 Aug
MicrosoftMicrosoft says it startedon Microsoft Fabric support
26 Aug+16 h 46 min
MicrosoftResolved
27 Sep+33 days 9 h
MicrosoftEarliest version we archivedOur archive started 13 Nov 15:47 UTC; earlier versions were not recorded.
What Microsoft changed
Microsoft rewrites incident updates in place. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full current text is on Microsoft's page.
One version so far. If Microsoft edits it, each change shows here with what was removed and added.
First version we captured ·
As first seen: Final root cause analysis · 1 service
- Status
- Final root cause analysis
- Services
- Microsoft Fabric
Seen by us · Microsoft's timestamp · Microsoft's page
Affected services
Last updated