Microsoft Fabric Outage History

An issue affected Microsoft Fabric users in East US 2 capacities that use Activator rules, with problems triggering actions or viewing live feeds. The outage began at Jan 7, 2026 1:14 AM UTC and was resolved by Jan 7, 2026 4:59 AM UTC, lasting about 3 hours and 45 minutes. The impact was isolated to the Americas Fabric component serving East US 2, with affected users experiencing degraded functionality rather than a complete outage.

Microsoft Fabric's status page listed the incident as a degradation and stated engineering teams were investigating, with an update to follow. A second update at Jan 7, 2026 4:59 AM UTC indicated the issue was resolved and the service returned to normal. The incident involved 2 official status updates during its course.

Microsoft Fabric reported an outage affecting Copilot access from Notebook. Users across Americas, Europe, Asia Pacific, Middle East, and Africa experienced sign-in failures and loading errors when attempting to use Copilot in Fabric Notebooks, disrupting data analysis and collaboration workflows. The incident began around Dec 30, 2025 11:00 AM UTC and was resolved by Dec 31, 2025 12:19 AM UTC. Fabric posted several updates during the incident as engineers investigated and worked toward restoration, with the issue impacting multiple regions.

An outage affected Microsoft Fabric in the BrazilSouth region, causing degraded performance and intermittent access for tenants in Brazil. The Fabric status page flagged the issue at Dec 17, 2025 11:49 AM UTC as engineers began investigating a regional disruption. User reports described slow panel loads and intermittent service across multiple Brazilian cities, indicating a regional pattern centered on BrazilSouth.

The incident lasted about 7 hours and 50 minutes, with recovery observed by Dec 17, 2025 7:39 PM UTC when the status page returned to a healthy state. Microsoft Fabric issued two status updates during the incident to communicate investigation progress and resolution. The issue affected the Americas / Fabric component, with the BrazilSouth region bearing the brunt of the disruption.

Microsoft Fabric experienced a regional control plane issue affecting tenants in the UAE North region, with capacities impacted and potential disruption to workflows relying on management functions. The incident began at Dec 17, 2025 6:24 AM UTC as engineers investigated and prepared an update. The issue was resolved about 56 minutes later, with the UAE North component returning to normal at Dec 17, 2025 7:20 AM UTC. The provider issued two official updates during the incident, describing the investigation and subsequent restoration.

Microsoft Fabric experienced regional issues affecting Spark Jobs and Notebook operations for tenants in the West US2 region, with Americas Fabric users reporting problems beginning at 1:09 PM UTC. The issue later extended to Asia Pacific, with APAC experiencing degradation as updates were issued. Users attempting to run Spark jobs or access notebooks faced failures or degraded performance across affected regions. The outage lasted approximately 6 hours and 35 minutes, and was resolved by 7:44 PM UTC. The Fabric status page posted three updates during the incident, documenting ongoing investigation, regional impact, and restoration of services.

Power BI Customers in the Fairfax (GCC) environment experienced a brief outage affecting the Capacity Metrics app. The incident lasted roughly five minutes, starting at 7:44 AM UTC and ending at 7:49 AM UTC, with users potentially unable to access metrics during that window. The issue was scoped to the Americas / Power BI component.

Microsoft Fabric status updates showed engineers were actively working to fix the issue, and normal operation was restored after the short disruption. The status page indicated the affected component transitioned from up to warn and back to up as remediation completed, reflecting a rapid fix.

An incident affected the Europe Power BI component, with tenants located in WABI-UK-SOUTH-C-PRIMARY experiencing latency in scheduled model refreshes. End users may have observed delays in data refresh operations during the event. The issue started at Dec 12, 2025 2:19 AM UTC and was resolved by Dec 12, 2025 3:24 AM UTC, lasting roughly 1 hour and 5 minutes. The service issued 2 status updates during the incident and confirmed resolution when the component returned to normal. The impact appeared geographically limited to Europe, with no indication of broader outages.

Power BI on Microsoft Fabric experienced latency affecting tenants located in WABI-WEST-US-E-PRIMARY, with scheduled model refreshes delayed for about 35 minutes. The incident began on 9:54 PM UTC and was resolved by 10:29 PM UTC.

Microsoft Fabric's status updates showed the Americas / Power BI component moving from a normal state to degraded performance and then returning to normal. The provider issued 2 status updates during the incident. No user reports were recorded, indicating limited impact beyond the regional tenant group.

Microsoft Fabric experienced a brief degraded performance affecting activator creation in the Americas / Fabric component, with impact localized to the North Central US. The incident began at Dec 10, 2025 5:49 PM UTC and was resolved by Dec 10, 2025 7:34 PM UTC, lasting about 1 hour and 45 minutes. The status page showed the Americas / Fabric component moving from up to warn before returning to up.

The provider issued 2 status updates during the incident, communicating progress and the eventual resolution. The issue was contained to the North Central US region and did not indicate broader regional impact.

The incident began on 1:49 PM UTC with the West Europe region reporting degraded SQL connectivity and failures when executing SQL queries or creating/opening warehouse artifacts. User reports started around 2:00 PM UTC from Chicago indicating connectivity issues.

The issue expanded to Git integrations via public APIs, with 403 errors observed across Asia Pacific, Africa, the Americas, and the Middle East around 4:44 PM UTC and 4:49 PM UTC. The service returned to normal by 5:34 PM UTC across all listed regions.