Microsoft confirms Power BI and Fabric outages restored on 30 May
Microsoft's service status page recorded incidents affecting Fabric capacities, Notebooks, and Spark sessions on 30 May 2026. The same report lists Power BI service issues during overlapping windows. All listed problems carry a restored status with no further action required. The disruptions were limited to specific hours and regions. No data loss or permanent configuration changes were reported. The note serves as the official timestamped record of the events.
Before today most teams treated Fabric as an add-on they could ignore until leadership asked for lakehouses. The shared control plane means any capacity-level fault now hits both new Fabric workloads and the semantic models that already feed their Power BI reports. After this incident the boundary between 'our existing reports' and 'Fabric experiments' has disappeared. A refresh failure or capacity throttle can now originate in Fabric even when the report itself has not changed.
Analysis
Assume every semantic model you publish could be throttled by a Fabric capacity event you did not trigger. Open each workspace, note which reports sit on Fabric-backed capacities, and add that list to the runbook you already keep for gateway and refresh issues.
Source note
Pulse published by Collab365 Spaces. Cite as "Microsoft confirms Power BI and Fabric outages restored on 30 May", Collab365 Spaces. 1 source referenced.