What Power BI is inside Fabric#
Power BI is Microsoft's business analytics platform for turning data into insights, and inside Microsoft Fabric it is one of the core workloads, supplying the platform's analytics and visualization layer [S1]. It has three main pieces: Power BI Desktop, a Windows app for authoring data models and report design; the cloud-based Power BI service, for publishing, sharing, and collaboration; and mobile apps for viewing reports on the go [S1]. The recommended workflow follows that split — author and model in Desktop, then publish to the service for team sharing [S1].
If you already use Power BI outside Fabric, nothing is lost: existing content and workspaces carry over without migration, using the same account you already have [S1]. Inside Fabric, Power BI shares platform-level features with other workloads — OneLake integration, Direct Lake mode, Dataflows Gen2, Purview governance, and Copilot — while Desktop and the visuals marketplace stay Power BI-specific [S1].
The building blocks you'll actually touch#
Two roles split most activity in the Power BI service: designers, who build and publish content, and consumers, who view and drill into it to make decisions [S2]. A report is one or more pages of interactive visuals built from exactly one semantic model, organized around a specific set of business questions [S2]. A dashboard is different — a single screen of tiles that can pull from multiple reports and models at once, built for at-a-glance monitoring [S2]. An app bundles related dashboards, reports, and models into one package for distribution, and publishing an app is the preferred way to reach a large audience rather than sharing items one at a time [S2]. Everything lives inside a workspace, a collaborative container where Admin, Member, Contributor, and Viewer roles control access — in Fabric, that same workspace can also hold lakehouses and notebooks [S2].
A worked example#
A designer builds a sales report in Power BI Desktop, connecting to a lakehouse table and adding a few DAX measures. They publish it to a shared workspace. A colleague with Contributor access opens it in the service, adds a filtered dashboard tile for their region, and pins it. The team lead then bundles that dashboard and report into an app and distributes it org-wide, rather than sharing the individual items [S2].
What goes wrong#
- Forgetting the licensing floor. Creating Power BI items outside your personal My Workspace and sharing them always requires at least one Pro or PPU per-user license, regardless of capacity size [S3].
- Confusing a dashboard with a report. A report is multi-page and tied to one model; a dashboard is one screen that can span several [S2].
- Assuming legacy dataflows are the current path. Power BI service dataflows are now legacy; Fabric's Dataflow Gen2 is the platform successor [S2].