Introduction to Power BI Embedded0%

Introduction to Power BI Embedded

Beginner12 min read•Updated: Jul 11, 2026

Introduction to Power BI Embedded: Architectures & Use Cases

Enterprises frequently need to deliver interactive Power BI dashboards directly inside custom web applications, client customer portals, or corporate intranet systems (e.g., Salesforce, SharePoint, custom React/Node.js web portals).

This capability is powered by Power BI Embedded.

1. The Two Core Architectural Models of Embedding

When architecting an embedded BI solution, developers must choose between two distinct identity and licensing approaches:

Output

                            Power BI Embedding Architectures
                                           |
           +-------------------------------+-------------------------------+
           |                                                               |
  "User Owns Data" (Embed for Org)                                "App Owns Data" (Embed for Customers)
- Intended for internal employees                               - Intended for external third-party clients
- Users authenticate via corporate Microsoft 365                - Users log into custom portal (JWT / Auth0 / DB)
- Every user MUST have a Power BI Pro/PPU license               - End-users do NOT need any Power BI license!
- Example: Embedding an internal HR dashboard into SharePoint   - Example: A SaaS app providing billing analytics

2. Technical Workflow: "App Owns Data" (Customer Portal)

In customer-facing SaaS applications, requiring thousands of external clients to purchase Microsoft Power BI licenses is commercially unviable. The App Owns Data pattern solves this:

Output

1[External User] ---> Logs into Custom Web Portal (React / Angular)
                            |
                            v
                 [Backend API (Node / Python)]
                            |
                            v (Authenticates with Azure Entra ID using Service Principal)
                 [Azure Entra ID / Microsoft Graph]
                            |
                            v (Requests Embed Token with RLS identity)
                 [Power BI REST API]
                            |
                            v (Returns Embed URL + Secure Token)
                 [Web Frontend (Power BI JavaScript SDK)]
                            |
                            v
                 [Interactive Dashboard Rendered inside <iframe>]

Key Components:

1
Service Principal (App Registration): A headless service account registered in Microsoft Entra ID with permissions to access Power BI workspace assets.
2
Embed Token: A time-limited, encrypted JWT token generated by your backend server granting the client browser permission to view a specific report and dataset.
3
Power BI Client JavaScript SDK (powerbi-client): The client-side npm library used to initialize, interact with, and dynamically filter the embedded iframe.

Interactive Quiz• Knowledge Check

Multiple Choice Questions

Question 1

What is the fundamental difference between "Embed for your organization" and "Embed for your customers"?

Question 2

Which client-side JavaScript library is used to embed and control Power BI reports inside web applications?

Question 3

What security entity in Microsoft Entra ID (Azure AD) is recommended to authenticate the backend server in an "App Owns Data" embedded architecture?

Question 4

Can Row-Level Security (RLS) be enforced when using "App Owns Data" embedding for external users?

Question 5

What Azure dedicated resource tier is commonly purchased to power commercial-grade Power BI Embedded applications?

Next Lesson

Use Cases

Continue learning with hands-on practice, examples, and exercises in the upcoming topic.

Related Lessons

Previous Lesson	Next Lesson
Creating Mobile Views	Use Cases

Practice Quiz

Test your understanding of this lesson with 5 questions. Each question has one correct answer.

Previous Next

PreviousPrevNext