Fabric customers with capacities located in WestUS region might experience issues with CRUD operations.
At a glance · Microsoft's status
ResolvedListed for 3 h 40 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 20:25 UTC on 12 Aug 2025. Microsoft marked it resolved at 00:05 UTC on 13 Aug 2025, 3 h 40 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.
12 Aug 2025
MicrosoftFirst public post (version 1)
13 Aug 2025+3 h 40 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.
- Dataflow Gen2 with CI/CD does not disallow cloud connections over gateways · Fabric and Power BI known issues · Same service; published 4 hours after it started ()
Last updated