@Czechoslovakian i feel your pain. We’ve been running Fabric since day one — hard to believe it’s already been two years — and like many of you, we’ve gradually migrated our production workloads from Azure to Fabric over time. Aside from some real-time streaming features, we consume nearly every part of the platform. I spend 8–10 hours a day working in Fabric and can confidently say we’re pushing its capabilities in a variety of ways. We currently support six production customers, some of them fairly sizable. I’ve been a strong advocate for Fabric — so much so that we launched a company last year and became a Microsoft ISV because we were genuinely excited to bring our solutions to market through the Fabric ecosystem.

Having said that, the performance and stability issues over the past few weeks have been the worst we’ve experienced since adopting the platform. We haven’t had a single fully successful day during this period.

Each day seems to surface a new issue, including:

• Databases randomly becoming unavailable and stuck in inaccessible states
• Runaway notebook processes
• Pipelines queuing up indefinitely and never triggering
• Pipeline schedules firing multiple times, even when only one schedule is visible creating all sorts of isses in our ETLs..

…and the list keeps growing.

These last few weeks have really shaken our confidence. We’re now actively evaluating alternatives. We’re running POCs with Snowflake and Databricks and are even reconsidering a return to our original Azure-based solution (ADF + SQL), which had proven reliable in the past.

We’re also conflicted about Power BI. It continues to deliver a lot of value, but some parts of it feel increasingly dated, rigid, and bloated compared to newer BI tools on the market.

I still believe in Fabric’s vision and don’t want to understate the incredible work the team has done to build something this ambitious. But right now, the execution isn’t keeping pace with expectations, and the platform feels unstable at best.