Fabric Apps is a new Microsoft Fabric item type (preview, announced at Build 2026) for building and hosting web applications directly inside Fabric. The "data app" template connects a custom web dashboard to a Power BI semantic model and queries it with DAX — with hosting, authentication, and row-level security handled by Fabric. No embed tokens, no separate infrastructure.
If you've ever scoped a Power BI Embedded project, that last sentence should make you sit up. Because what Microsoft just shipped looks a lot like embedded analytics without the embedding — and the licensing implications are, so far, almost completely undocumented.
What is a Fabric data app?
A data app is one of two templates for Fabric Apps. The default ("operational") template provisions a managed SQL database and generates GraphQL APIs from TypeScript data models. The analytical template — the data app — skips the database and instead connects to a published semantic model, querying it with raw DAX through the executeQueries REST API, just like a Power BI report does under the hood.
The difference is everything around the query. There is no canvas, no formatting pane, no visual gallery. A data app is source code: React and TypeScript for the frontend, Vega-Lite or D3.js for the visuals, a .dax file per visual, CSS for theming. You scaffold the project with Microsoft's Rayfin CLI, develop locally, and deploy with a single rayfin up command. Fabric hosts the static assets in OneLake, brokers authentication through Microsoft Entra ID single sign-on, and enforces the semantic model's row-level security on every query.
Kurt Buhler of Tabular Editor, who published the first deep technical analysis of data apps, puts the difference well: "if a Power BI report is Lego, then a data app is a 3D printer." You get total control over every pixel — and total responsibility for it. Microsoft's expected workflow is that most people won't write this code themselves: the template ships with agent skill files so AI coding agents like GitHub Copilot or Claude Code can build the dashboard for you. Buhler reports building bespoke dashboards roughly 80% faster with a data app and an AI agent than recreating the same design as a Power BI report.
Fabric Apps vs Power BI Embedded: what changes?
For years, putting a custom-branded, pixel-controlled dashboard in front of users meant choosing between Power BI Embedded and a custom-built dashboard: an Azure app registration, a service principal, embed tokens, the JavaScript embedding API, your own web app to host it all, and a capacity SKU to run it. A data app collapses most of that stack — it's essentially a custom-built dashboard where Fabric supplies the hosting and auth.
That last row is the interesting one.
The licensing question nobody has answered yet
Here is what we know, and what we don't.
The known rules. For Power BI items — reports, dashboards — the rules are established: on an F64 or larger capacity, viewers with a free Fabric license can consume content; below F64, every viewer needs a Pro or PPU license — a cost that adds up fast for agencies and service businesses. Non-Power BI Fabric items (notebooks, pipelines, warehouses) have never carried that per-viewer requirement — a free license suffices to consume them on any F capacity.
The open question. A Fabric App is not a Power BI item type. It's a Fabric workload item, shared through item-level "Run and interact" permission, consuming capacity units like any other Fabric workload. Microsoft's documentation states the capacity cost of a data app is simply that of its DAX queries — the same as a Power BI report against the same model. What it does not state is whether a viewer opening a data app on, say, an F8 needs a Pro license the way they would for a Power BI report on that same capacity.
Read that again, because the two possible answers lead to very different places:
- If free users can view data apps on small F SKUs, a data app becomes a way to serve DAX-powered dashboards to unlimited internal viewers on an F2 — something that would otherwise require Pro licenses for every viewer or a jump to F64 (a roughly 30x price difference in capacity alone).
- If the Power BI viewer rules apply — perhaps because the executeQueries API call is metered as Power BI consumption — then nothing changes economically, and the appeal is purely about flexibility.
Our working assumption is that Microsoft will close any gap before general availability; a licensing loophole this size rarely survives preview. But as of early June 2026, the documentation is silent, and that silence is exactly why you should test this against your own tenant before building plans on it. We'll update this post as soon as Microsoft documents the behavior or our own testing settles it.
Where data apps break down
Before anyone declares Power BI Embedded dead, three hard limits:
No external users. Deployed Fabric Apps authenticate exclusively through Fabric SSO with Entra ID. There is no app-owns-data equivalent, no anonymous access, no custom auth provider. If you're an ISV embedding analytics into a product for customers outside your tenant — the core Power BI Embedded scenario — data apps cannot replace that today.
AI dependence. Most BI developers don't write React. The realistic workflow is agent-built code, which means your dashboards are only as maintainable as your team's ability to prompt, review, and troubleshoot generated code — plus a token bill that didn't exist before.
Preview-grade maturity. Tenant admins must enable two settings ("Fabric Apps (preview)" and "Dataset Execute Queries REST API"), features are shifting, and functionality that Power BI gives you for free — drillthrough, export to Excel, even multi-page navigation — must be coded from scratch.
Verdict
For internal embedded scenarios — a bespoke operational dashboard for a department, a branded data experience inside your tenant — data apps are a serious alternative to both Power BI Embedded and heavily-hacked Power BI reports, available today. For external-facing ISV embedding, Power BI Embedded keeps its job for now. And for everyone in between, the licensing question is the one to watch: it will decide whether data apps are merely interesting or genuinely disruptive.
We help teams figure out exactly this kind of question — Power BI, Fabric, embedded analytics, and what viewers actually cost. If Fabric Apps is on your radar, get in touch.
FAQ
Do Fabric Apps replace Power BI reports?No. Microsoft positions data apps as an additional option. Power BI reports remain simpler, more mature, and better suited for self-service scenarios; data apps target bespoke, code-first dashboards.
Do viewers of a Fabric data app need a Power BI Pro license?As of June 2026, Microsoft has not documented this. Power BI items require Pro for viewers below F64 capacity; Fabric Apps are a different item type and may not inherit that rule. Test against your own tenant and treat any assumption as provisional.
Can I use Fabric Apps for customer-facing embedded analytics?Not currently. Fabric Apps require Entra ID SSO, so only users in your tenant can access them. External-user scenarios still require Power BI Embedded.
What skills do I need to build a data app?A data app is a TypeScript/React web project with Vega-Lite or D3.js visuals and hand-written DAX queries. Most BI developers will rely on AI coding agents; familiarity with DAX and basic web concepts helps you review what the agent builds.
