The Power of No-Code/Low-Code Data Analysis on Embedded Report Development

Hi JoseAntonioPine ,

If you buy a Fabric capacity (F SKU or Premium P SKU), you do not need to buy Power BI Embedded (A SKU) separately. Fabric capacity already includes Power BI and supports embedding. Only buy an A SKU if you specifically want “Power BI Embedded only” without any Fabric workloads.

How this maps to your scenario

You have a Fabric workspace and a front‑end app that embeds a Power BI dashboard pointing to OneLake (e.g., Direct Lake to a Lakehouse/Warehouse).
Use a Fabric capacity (F SKU) or Premium per capacity (P SKU). Both:
Host Fabric items (Lakehouse/Warehouse) and Power BI content
Support embedding (embed tokens) so your app’s users don’t need Power BI licenses
Do not use only an A SKU if you need OneLake/Direct Lake/Fabric items. A SKUs are Power BI-only and don’t run Fabric workloads.
Alternatives depending on who your viewers are

External customers (app owns data): Requires capacity. Use F or P capacity (recommended for Fabric/OneLake). No need for A if you have F/P.
Internal users (embed for your organization):
Option 1: Everyone has Pro or PPU licenses; no capacity required (PPU content must be in a PPU workspace).
Option 2: Put the workspace on F/P capacity and allow free users to view without per‑user licenses.
Licenses you still need

Authors/publishers need at least Power BI Pro to publish to workspaces (even when those workspaces are on capacity).
Viewers in an external “customers” scenario don’t need Power BI licenses if you use embed tokens on capacity.
Quick setup checklist

Purchase/assign an F capacity in the same region as your Fabric items.
Assign your Fabric workspace to that capacity.
Ensure your dataset/report uses your OneLake item (Direct Lake/Warehouse/Lakehouse).
In Power BI Admin, enable service principal access to APIs; register an app (service principal), add it to the workspace, and generate embed tokens for your app.