How powerbidevcamp/app-owns-data-starter-kit works
Project type and purpose
• This is a multi-project full-stack starter kit for App-Owns-Data embedding with Power BI.
• It includes four web applications, a shared class library, a SQL Server database, integration with Azure AD for identity, and calls to the Power BI Service API.
• The purpose is to demonstrate best practices for multi-tenant embedding, workspace provisioning, user authorization, and custom telemetry.
File-structure overview
• Top-level solution: AppOwnsDataStarterKit.sln
• Five projects under solution:
• AppOwnsDataAdmin (ASP.NET MVC)
• AppOwnsDataWebApi (ASP.NET Core Web API)
• AppOwnsDataClient (jQuery/Bootstrap SPA)
• AppOwnsDataReactClient (React-JS/Material-UI SPA)
• AppOwnsDataShared (Class library with EF Core models & services)
• Shared:
• Database migrations under AppOwnsDataShared/Migrations
• Client apps each have TS/webpack configs, libman or npm package files, and generated bundle.js in wwwroot.
• Admin and WebApi have appsettings.json for AzureAD, PowerBI, and DB.
• External templates under Admin/wwwroot/PBIX and AppOwsDataUsageReporting.pbix at the solution root.
Key README insights
• Solution architecture uses:
• A custom SQL database (AppOwnsDataDB) via EF Core Code-First in Shared library.
• AppOwnsDataAdmin: provisions tenants (creates Power BI workspaces, imports PBIX/RDL templates, patches parameters & credentials, refreshes datasets) using service-principal profiles.
• AppOwnsDataWebApi: backend for client SPAs, generates Power BI embed tokens (Client Credentials Flow, service principal), enforces per-user authorization by querying AppOwnsDataDB for permissions, and logs telemetry.
• AppOwnsDataClient & AppOwnsDataReactClient: two SPA implementations that authenticate users via Azure AD (MSAL.js), call WebAPI endpoints, receive embed tokens, and embed Power BI reports (view/edit/create).
• Custom telemetry: SPAs call WebAPI ActivityLog endpoint; WebAPI logs events in DB; AppOwsDataUsageReporting.pbix analyzes usage/performance.
Components
• Server-side components (hosted on IIS/Azure App Services):
• AppOwnsDataAdmin (ASP.NET MVC)
• AppOwnsDataWebApi (ASP.NET Core Web API)
• AppOwnsDataShared (Class Library, EF Core)
• AppOwnsDataDB (SQL Server)
• Client-side components (user’s browser):
• AppOwnsDataClient SPA (jQuery/TypeScript)
• AppOwnsDataReactClient SPA (React-JS/TypeScript)
• Power BI JavaScript Client Library
• External services:
• Azure AD (Identity Provider)
• Power BI Service API (embedding, workspace & report management)
• (Optional) Dedicated Power BI Capacity (P or A SKUs)
Relationships and data flows
• Client SPA → Azure AD: user authentication (acquire access token for WebAPI).
• Client SPA → AppOwnsDataWebApi: call /UserLogin, /Embed, /ActivityLog endpoints, passing access token.
• AppOwnsDataWebApi → Azure AD: Client Credentials Flow to get app-only token (to call Power BI REST).
• AppOwnsDataWebApi → AppOwnsDataDB via AppOwnsDataShared → store/retrieve Tenants, Users, ActivityLog.
• AppOwnsDataWebApi → Power BI Service REST API: generate embed token, import RDL, etc.
• AppOwnsDataAdmin → Azure AD: authentication for admin users, then uses service principal profiles via Power BI REST API to provision tenants.
• AppOwnsDataAdmin → AppOwnsDataDB: record tenants and service principal profile IDs.
• AppOwnsDataAdmin → Power BI Service: create workspaces, import PBIX/RDL, set params, refresh.
• AppOwnsDataClient/ReactClient → Power BI JavaScript API: client-side embed using embed token received from WebAPI.
Architectural patterns & principles
• Layered architecture:
• UI (SPAs)
• API layer (AppOwnsDataWebApi)
• Business/data layer (AppOwnsDataShared + EF Core + SQL DB)
• External integration layer (Power BI REST, Azure AD)
• Shared library for reuse (AppOwnsDataShared)
• Separation of concerns: admin vs. user workloads
• Secure token flows: OAuth2 Client Credentials for backend, MSAL.js for front-end.
• Multi-tenant isolation via service-principal profiles.
Essential elements
• Components: AppOwnsDataAdmin, AppOwnsDataWebApi, AppOwnsDataClient, AppOwnsDataReactClient, AppOwnsDataShared, AppOwnsDataDB, Azure AD, Power BI Service, Dedicated Capacity
• Flows:
• User → SPA → WebAPI → DB & Power BI
• SPA → Azure AD (login)
• Admin App → WebAPI & Power BI provisioning