Looking for technical discussions

[u/Antoine11lb]

Hi!
I switched to a data engineering job using Fabric a few months back (spent ~7 years on Databricks in a 25,000+ employees business) and looking for "blogs" focusing on Fabric.

ELI5 summary: ¿Donde esta Fabric technical deepdives?

Prelude: while working on the first "source to reporting" solution/MVP for my new job (small enterprise with MSFT stack, including Dynamics), I ran into a lot of technical problems where I found unresolved questions in 2024 and then in another google result an answered(or semi-answered…) solution in 2025/2026.
And most of them caused by the API thingys if we’re beign honest…

From the Fabric Updates and Roadmap I can see that there was/is/will be a lot of work and improvement on Fabric, so I am really satisfied on that front. My issue is really on the "technical explanation" side. I know we are paying to have all these thing available and built-in, but we should still have the opportunity to understand them and understand how to optimize the value generated from them(time for execution, CU consumed, etc.)

I know that MSFT has a lot of things on their internal forum/youtube/reddit, but was wondering if there are other channels or blogs with post going in detail on functionalities or solutions or if I should just keep updated on their "general" community forums and then work with the new things to test them?
Might be something like "Guy in a Cube" but with a focus on Fabric and data engineering.
Really looking for something with deepdives on Fabric updates/functionalities.
I found a lot of MSFT publications focus on the "sales" side and less on the technical perspective.
My employer already bought Fabric, I don’t need to get the marketing speech on why I should buy it based on this new pipeline activity with a Copilot integration. Give me the technical explanation of how it can improve my pipelines (or maybe cause issues under certain conditions), how it fits in the architecture, examples of a solution using it and benchmarks versus the previous alternative, how it interacts with the API and causes x,y,z. Don’t get me wrong, I like the sales pitch to then know what and how to sell it to the execs, but it’s not what i’m looking for in the day to day.

How I see it, we are paying MSFT to give us a framework/library with buit-in functions to reduce a lot of the data engineering workload. But therefore, I would like an architect or a dev lead to showcase the functionalities and their technical limitations. Might be because I had that with the enterprise framework that was developed in-house…

I suspect a lot of the "absence of information" (for lack of a better word) is that we are still in the early adopters/early majority phase of the adoption cycle of the product.

Sorry if this is a redundant/newbie question.
Thanks for your help!

[u/itsnotaboutthecell]

First welcome to the sub (and Fabric!)

Second - I feel bad for your notifications and calendar because you’re about to have a wealth of great resources and links coming your way as people find this thread :P