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
ResolvedListed for 7 h 28 min
- First posted
- on the Fabric support page
- Ended
- · marked resolved
- Affects
- Microsoft Fabric
- Edited
- Not since we first saw it
- Source
- Microsoft Fabric support · checked 1 min ago
In short
Microsoft reported degraded service affecting Microsoft Fabric, first posted on the Fabric support page at 17:05 UTC on 11 Aug. Microsoft marked it resolved at 00:34 UTC on 12 Aug, 7 h 28 min after it was first posted.
Microsoft says
Microsoft published no text with this incident.
Timeline
Times in UTC, Microsoft's own where it gives them.
11 Aug
MicrosoftFirst public post (version 1)
12 Aug+7 h 29 min
MicrosoftResolved
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: Resolved · 1 service
- Status
- Resolved
- Services
- Microsoft Fabric
Seen by us · 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 17 hours before it started ()
Last updated