Power BI Embedded Overview:

• Solutions: Two solutions - Embed for customers (app owns data) and Embed for organization (user owns data). For the scenario, Embed for customers is used.
• Licensing (Embed for customers - app Owns Data): Capacity needs to be purchased/licensed. Two types of capacity-based licenses - Embedded (available with Power BI Embedded in Azure, billed hourly, can be scaled up/down, node in A SKU category) and Premium Per Capacity (available with Power BI Premium from Microsoft 365 admin centre, billed monthly, node in P SKU category, can't be paused/resumed). Content creators need a Power BI Pro license.
• Authentication: An embedding identity is required. It can be a service principal (app uses it to acquire Azure AD token after admin enables its use and registers a security group) or a master user (must have Power BI Pro or Premium Per User license and belong to workspace admin or member role, can't require MFA). Authentication flow involves acquiring Azure AD token using non-interactive flow and then generating embed token using Power BI REST API. For the scenario, Service Principal is used as it is more secure.
• APIs: Power BI Embedded APIs provide programmatic access. Power BI REST API has various operation groups for managing and embedding content. Power BI Client API is a client-side library with different categories like powerbi-client, powerbi-models, and powerbi-report-authoring to control and edit embedded content. The next article covers PowerBI Embedded Demo application.