Forum Discussion
Helper IMicrosoft Fabric Workload
Helper IAnonymous , lbendlin
I probably expressed myself badly because I am French-speaking and I use translation.
My organization already uses Microsoft Fabric very widely in all these aspects of preparation, transformation and visualization of data passing through pipelines, notebooks, lakehouse, warehouse, streamhouse, machine learning, KQL database, power bi, etc.
I would like to add in this data environment the aspects of governance, management and data solution and, among other things, to do this, I would like to be able to develop, for example, small home applications to update pilot data used to configure the data solutions that we offer to users in Fabric.
There is now the notion of workload (https://learn.microsoft.com/en-us/fabric/workload-development-kit/development-kit-overview) which allows ISVs to enrich Microsoft Fabric with solutions based for example on data on OneLake directly, lakehouse, warehouse,...
My question is that this seems to reserve or at least, intended only for use by ISVs and not for organizations in general for their internal needs because we must publish the solution on the Microsoft market, etc.
Developing in Fabric would avoid us having an independent solution and independent infrastructure, it would be great if everything that revolves around data were 100% in Fabric.
Super UserYeap, Fabric is pretty much the opposite of what you call "internal" - hence my question about Power BI Report Server which is the legacy on-premise option. I am not even sure if it will survive the full migration to Fabric.
- Master
no, I never talked about Power BI Report Server, no connection with what I'm saying and we don't use that!
I don't understand what you're saying, everything we put in Fabric is strictly for us internally.
When I say internal, I mean for the use of our organization, it's not physical, we're 100% Cloud!
I think we don't understand each other!
- lbendlin
Yes, we seem to be talking about different things.
Fabric is fully capable of handling a scenario where a company like yours wants to use all the Fabric features exclusively for "internal" consumption. There are many different target audiences for Fabric, and each of the target audiences can use different combinations of components to achieve their goal.
What gave you the impression that it is only targeted at ISVs?
- Master
No, I'm talking about workload development in Fabric: (https://learn.microsoft.com/en-us/fabric/workload-development-kit/development-kit-overview)