Forum Discussion

pmscorca's avatar
pmscorca
Icon for Post Prodigy rankPost Prodigy
3 months ago
Solved

User Data functions to implement a backed for an industry solution

Hi, I'd like to know if user data functions represent a good and valid feature in order to implement an industry solution (for many customers), safeguarding the intellectual property. Any suggests ...
data engineering
User Data Functions
  • tayloramy's avatar
    tayloramy
    3 months ago

    Hi pmscorca, 

     

    If you want to safeguard the business logic, then a custom workload is what you are looking for. 

    Once a data function is deployed to a tenant, users in that tenant will be able to access them and view the logic. 

     

  • v-prasare's avatar
    v-prasare
    3 months ago
    Hi @pmscorca ,
    A template app can be considered for distributing your solution to non‑Fabric users, but it doesn’t replace a workload from an architecture or IP‑protection perspective.
    According to Microsoft documentation please refer below, Power BI template apps are primarily designed to package and deploy prebuilt datasets, reports, and dashboards to any Power BI customer and allow users to install and customize them within their own tenant.
    While this makes them effective for solution distribution and reuse, customers can still install, modify, and access the underlying artifacts, which means they don’t inherently protect your ingestion or transformation logic. In contrast, Fabric custom workloads are designed as extensible applications embedded in the platform, where your logic runs within your controlled service layer and integrates into Fabric via secure APIs and authentication.
     
    Therefore, template apps are best suited for delivery and onboarding, whereas protecting backend logic in multi‑customer scenarios typically requires a workload or an external service layer.
deborshi_nag's avatar
deborshi_nag
Icon for Super User rankSuper User
3 months ago

Hello pmscorca 

 

I would say Fabric Data Functions are a useful foundation, offering a serverless environment to centralize business logic, making them suitable for scaling industry solutions. They provide execution-level access without exposing the code, which is important when creating multi-customer solutions. However, when designing for multiple customers, it’s important to consider access control, authentication, and data segregation. This may mean setting up separate workspaces, identities, or function instances for each customer to prevent cross-tenant risks.

 

In summary, this is a practical feature, but it needs to be paired with the right architecture and permission model!