External Users Access to Report

Hi DPCCGF​ ,

For 750 external field users, the answer is app-owns-data embedding, not per-user access. You embed the report in a web app, authenticate the officers with your own auth, and the app connects to Power BI/AAS through a single service principal. The 750 never need Power BI licenses or guest accounts in your tenant, so you skip the whole per-user B2B security nightmare. If different agencies should only see their own data, you enforce that with AAS roles and effective identity in the embed token, so isolation is handled centrally rather than per user. (Skip Publish to Web here, it's fully public, which is a non-starter for law enforcement data.)

You can build this yourself with the powerbi-client SDK, but at 750 external users it's real infrastructure to stand up and maintain: capacity, embed token generation and refresh, and per-agency RLS. That's exactly the problem we solve at DataTako, an out-of-the-box embedding layer that handles the tokens, the licensing side, and the agency isolation for you, so you get the officers into the report without wiring it all up yourself. Happy to walk you through how it'd map to your AAS setup if useful.

Paco
Helping data analytics leaders distribute their reports