Fabric customers with tenants located in Europe regions might have experienced issues using Data Agent functionality when Code Interpreter is…
At a glance · Microsoft's status
ResolvedLasted 26 h 37 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 21:57 UTC on 10 Aug. Microsoft marked it resolved at 00:34 UTC on 12 Aug after 26 h 37 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.
10 Aug
MicrosoftMicrosoft says it startedon Microsoft Fabric support
12 Aug+26 h 37 min
MicrosoftResolved
27 Sep+47 days 22 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
Changes around this incident
Possible connection
Changes to the same services that took effect shortly before the incident started. A shared service and time is not evidence that the change caused it.
- Warehouse recovery fails to restore the original name when a Warehouse with the same name already exists · Fabric and Power BI known issues · Same service; published 2 hours after it started ()
Last updated