Microsoft Fabric Workload

[Master]

Why Microsoft Fabric workloads seem to be reserved only for ISVs and there is no internal use in the enterprise planned, to develop a data solution specific to our organization ?

[Anonymous]

Hi @Master ,

Thanks for the reply from lbendlin .

While Microsoft Fabric does provide an integrated solution for Independent Software Vendors (ISVs) —— Microsoft Fabric ISV Partner integration with Fabric - Microsoft Fabric | Microsoft Learn , that doesn't mean that organizations can't use Fabric for their own data solutions.

Fabric is a unified platform for an organization's data and analytics needs. Fabric includes features such as Power BI, Synapse, and Data factory for connecting to data sources, building, transforming, and visualizing data.

You can refer to the documentation below to learn how to use Fabric in your organization:

Microsoft Fabric documentation - Microsoft Fabric | Microsoft Learn

Microsoft Fabric enterprise documentation - Microsoft Fabric | Microsoft Learn

If you do need Fabric to develop data solutions specific to your organization in your planned enterprise, you can submit a idea on Home.

If you have any other questions please feel free to contact me.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[Master]

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

[lbendlin]

Yeap, 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]

@lbendlin 

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)

[lbendlin]

So you want to create workloads for your internal usage? Ok, I guess.  Go do it. Nowhere there does it say that workloads are for ISV scenarios.

[Master]

that's exactly my point, if you look at the documentation, the fact that you have to publish your solution on the market, etc. everything is done so that Microsoft partners publish paid solutions.

is it wise to think, is it possible (this does not seem to be the case), to create a solution strictly for the use of my organization?

if we are obliged to publish the solution on the market, this is not the case. So that's why I say that it is reserved for ISVs.

[lbendlin]

I see what you mean now.  There is a "Free (get it now)"  option but you would still have to publish your workload onto their marketplace. 

Have you considered Power BI Embedded instead?  What types of workloads are you considering developing?

[lbendlin]

Can you please elaborate? Are you referring to Power BI Report Server?