Founder | CEO @ RADACAD | Coach | Power BI Consultant | Author | Speaker | Regional Director | MVP
Power BI Fabric Web Apps let developers create custom web applications that query semantic models and present data in tailored visualizations. This approach is for developers and BI teams looking to build interactive experiences beyond a conventional report canvas. Reza Rad (RADACAD) [MVP] demonstrates the approach and describes how the apps can work with semantic models.
Traditional Power BI reports use PBIR, a JSON-based format that calls Power BI services to render report experiences. Fabric Web Apps offer another route: build a web application with HTML and JavaScript, and connect it to a semantic model. The app can present reporting as part of a custom interface rather than as a standard report.
The key distinction is that this approach queries the semantic model directly. An app can use existing model definitions and generate DAX for queries, instead of requiring a separate proxy model. The app can also use Vega-Lite visualizations, a format for describing data charts, as part of its web experience.
This approach is aimed at developers who want to build a custom reporting experience, including teams using AI tools to generate HTML and JavaScript. The starting point is a semantic model containing the data the application needs to query. The model supplies a connection to the data; the web app supplies the interface and visualization experience.
Fabric Apps are described as being in preview. That makes it sensible to evaluate the approach in the context of development and testing rather than assume it is a replacement for established Power BI report delivery.
The scaffolding is intended to take care of parts of web development that developers would otherwise have to assemble, including authentication and semantic-model queries. That lets the builder focus more on the application experience and the questions it should answer.
A Fabric Web App is a different development route, not simply a Power BI report with a new name. It involves building a web application, so teams should decide whether they need a custom interface before choosing it over a traditional report. The preview status also makes testing and evaluation important before relying on it for a production workflow.
Check that the semantic model or models contain the data the app needs, and that the generated queries and visualizations meet the intended requirements. If the goal is conventional report authoring, PBIR and the Power BI report experience remain the alternative described here.
They are custom web applications that can query Power BI semantic models and present data in a tailored interface with visualizations.
Yes. Different pages can query different semantic models directly, without creating a proxy model.
The app scaffolding can generate DAX for queries against a semantic model.