Dev.to
7/21/2026

Microsoft Fabric Apps Are a Distribution Channel, Not a Marketplace: Who Should Build One
Short summary
Microsoft Fabric's Workload Dev Kit lets ISVs build native surfaces inside Fabric alongside Lakehouse and Power BI, making it a distribution channel rather than a marketplace listing. The workload runs on the ISV's own infrastructure but renders inside the customer's Fabric tenant with Entra ID identity flow and OneLake data access. This structurally reduces security review friction since data stays in the customer's tenant, but requires real engineering investment beyond the happy-path sample.
- •Fabric workloads are a distribution channel inside the buyer's daily tool, not an app store listing
- •Data stays in the customer's tenant under existing Entra ID roles, shrinking security review surface area
- •Budget for real engineering — frontend/backend contracts and item lifecycle take more than configuration
Generated with AI, which can make mistakes.
Is this a good recommendation for you?



