Forum Discussion
How creating a Python custom library
- 2 months ago
Hi pmscorca,
That is correct. Here is an example of a custom workload with the extensibility toolkit: https://community.fabric.microsoft.com/t5/Extensibility-Toolkit-Gallery/Fabric-Job-Registry/m-p/5006346
Hi, thanks for your reply.
Let's assume that my solution is composed of a lakehouse, a pipeline for data ingestion, a notebook for data transformation, a semantic model and a set of Power BI reports.
I don't want to offer a service on my tenant; it needs to be on the customer's tenant as much as possible.
In a such case, you say that implementing a custom workload is the right way to follow, ok.
So, what does a customer workload create on the customer tenant? Lakehouse plus pipeline plus notebook plus semantic model plus reports? F.e. if the custom workload creates a notebook, is the related code protected?
Hi pmscorca,
A custom workload can create anything that you can code.
There's built in APIs to access system storage, and Fabric has lots of APIs for creating lakehouses, accessing lakehouse data, ect.
I would recommend that you don't use a notebook for data transformation, and instead build a "data transformation" item that does everything you need it to do, and keeps the logic hidden from the end users.
Once you have built this out, then you need to get it published to the Azure marketplace, and from there anyone can purchase it from you.
Note that code is only protected for your custom item types, so if your workload creates a default item type like a notebook using the APIs, then that will behave just like any normal notebook and the customer will be able to see the code.
However if you create a custom "transformation" item type, then your code will be hidden.
- pmscorca2 months agoKudo Kingpin
Hi, thanks for your reply.
So, in a custom workload it is enough to create some custom items in order to protect the code and all these custom items can reside on the customer's tenant, isn'it?
Thanks
- tayloramy2 months agoSuper User
Hi pmscorca,
That is correct. Here is an example of a custom workload with the extensibility toolkit: https://community.fabric.microsoft.com/t5/Extensibility-Toolkit-Gallery/Fabric-Job-Registry/m-p/5006346