Fabric customers in the North Central US region may experience issues with capacity management operations.
At a glance · Microsoft's status
ResolvedListed for 25 h 47 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:12 UTC on 25 Aug. Microsoft marked it resolved at 22:00 UTC on 26 Aug, 25 h 47 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.
25 Aug
MicrosoftFirst public post (version 1)
26 Aug+25 h 48 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.
- INSERT statements using IDENTITY_INSERT must specify target columns · Fabric and Power BI known issues · Same service; published 4 hours after it started ()
- Apache Airflow Job shows stale “Broken DAG” error after a Git-synced DAG file is renamed or deleted · Fabric and Power BI known issues · Same service; published 4 hours after it started ()
Last updated