As per the title; I'm using PowerBI Embedded to serve reporting from our Multi Tenant Retail / Hospitality Application - Secured using RLS. I would like to add the ability for users to add in their own sales forecasts into the PowerBI model, and understand the only way to currently do this within PowerBI is to use PowerApps. I couldn't find an answer to the above question - so was wondering if anyone could put me in the right direction, or has had experience with this?
Only PowerApps users in the same tenant can access the embedded app.
suggests that using this technique with Power BI Embedded won't work, as the App Owns Data scenario suggests that your users aren't "in your tenant", but are user accounts in your application domain. I'm interpreting the text, and am looking for clarification from MS, please.
You are right. The App Owns Data model in Power BI have its corresponding Report access credential "Stored" within the code, so external users could see the reports without entering their credential, while PowerApps Embedding scenario still need the same tenant users to sign in to use.
So for the Power BI App owns Data scenario, to use PowerApps embedding (custom Visual) is not available.
For PowerApps Share to external users, please check the following idea for the current status:
Besides, as I have shared earlier, currently the custom Visual could only get the Power BI Filter data into PowerApps as Read-Only data, to modify the data, additional modifications need to be done when building the PowerApps Visual.
And for the updated data to sync back to Power BI, you need to wait until the next data refresh schedule.
The latest on this from the PowerApps ideas forum, posted by a Microsoft staffer last week: "We will have a private preview and public preview dates earlier than Oct [i.e. 2019]. Exact dates are still to be determined."
It's a good thing I tested this as a client of mine asked about using PBI Embedded with some form of user input, and I initially thought the PowerApps custom chart would be the obvious solution. I guess we'll have to handle user input outside of the PBI embed with some JS API glue to tie it together.