Microsoft Fabric customers in the West Europe B cluster may have encountered errors when creating Fabric artifacts.
At a glance · Microsoft's status
ResolvedListed for 39 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 11:09 UTC on 11 Nov. Microsoft marked it resolved at 11:48 UTC, 39 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 Nov
MicrosoftFirst public post (version 1)
+39 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.
- Time Travel in Fabric Warehouse returns Incorrect Results When INSERT-SELECT uses the same table · Fabric and Power BI known issues · Same service; published 11 hours before it started ()
- SAP On-premises data gateway 3000.338.3 failures · Fabric and Power BI known issues · Same service; published 11 hours before it started ()
- Digital Twin Builder flow runs fail or show as Cancelled · Fabric and Power BI known issues · Same service; published 1 day before it started ()
Last updated