Forum Discussion
pmscorca
Post Prodigy
3 months agoUser 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 ...
- 3 months agoHi @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.
pmscorca
Post Prodigy
3 months agoHi, implementing a template app instead of a workload, with non-Fabric users in mind?
Thanks
v-prasare
Community Support
3 months agoHi @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.