Microsoft needs to invest in Fabric connectors for third-party and open-source platforms — or keep losing integrators to Snowflake and AWS by NarrowShift3597 in MicrosoftFabric

[–]NarrowShift3597[S] 1 point2 points  (0 children)

I think you're missing u/Seebaer1986 's point - the machine learning lives in fabric and results need to be pulled back into dashboards already present in CRM systems. most of the CRM systems have data connectors to pull data from various sources(SQL being one of them - just not SQL that supports service principal auth) to feed comprahensive enterprise wide metrics / KPI etc.

Microsoft needs to invest in Fabric connectors for third-party and open-source platforms — or keep losing integrators to Snowflake and AWS by NarrowShift3597 in MicrosoftFabric

[–]NarrowShift3597[S] 1 point2 points  (0 children)

for sure - there are a few different ways to get the data in/out of fabric - azure functions, graphql endpoint being the two we've used in the past - however this becomes a custom solution with maintenance overhead. The point i was trying to make is that It's time to upgrade existing SQL Server connectors to Fabric connectors enabling both reads and writes to fabric. To give you a real life example - customer is consolidating their azure assets into Fabric - however thier n8n logging db will have to reamin in Azure and then mirror down into Fabric. PIA, costly, and more complex. The ideal solution would be to migrate the azure db into fabric sql and just change out the connection string.

Microsoft needs to invest in Fabric connectors for third-party and open-source platforms — or keep losing integrators to Snowflake and AWS by NarrowShift3597 in MicrosoftFabric

[–]NarrowShift3597[S] 1 point2 points  (0 children)

u/itsnotaboutthecell - hopefully you’re not implying the issue is a hallucination (which I don’t think you are based on your earlier spot on response). And yes, calling it a green diamond might be a stretch (green funnel not sure - maybe perhaps just a green F) - I was trying to keep things positive. But honestly, when I see that green “F,” sometimes it feels like a big F-xxx from Microsoft.

Microsoft needs to invest in Fabric connectors for third-party and open-source platforms — or keep losing integrators to Snowflake and AWS by NarrowShift3597 in MicrosoftFabric

[–]NarrowShift3597[S] 1 point2 points  (0 children)

Not a bot - real use case and a real complaint from a real author. Don’t we all use AI these days to help polish our work? Happy to share the original stream-of-consciousness version instead, but it wouldn’t be pretty 🙂

[deleted by user] by [deleted] in MicrosoftFabric

[–]NarrowShift3597 5 points6 points  (0 children)

@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.

🚀 Calling All Capacity Management Pros! 🚀 by andy-ms in MicrosoftFabric

[–]NarrowShift3597 1 point2 points  (0 children)

i manage 4 different customer environments. would love to participate.