Forum Discussion
Power BI Embedded questions
Yes Sunkari I believe you need an Azure subscription as you need to set up a Power BI Workspace Collection, and either a Azure SQL database or Azure SQL Datawarehouse (or HDInsights) - all done through the Azure Portal or using the API (which requires Azure credentials). I think you get one month of free credits when you sign up to Azure?
It is worth setting up a poc so that you understand the current limitations of of the Embedded beta offering so that you can track if and when these limitations are overcome and you can provide feedback to the team. My experience with the Power BI team so far is that they will move quickly to fill in the gaps.
I followed the steps here:
https://azure.microsoft.com/en-us/documentation/articles/power-bi-embedded-get-started/
Few more additions to above questions:
1) Can we create a workspace inside workspacecollection in Azure portal?
2) What level security is implemented?It seems it is implemented at Workspace level, is it correct? If no, we can implement at report level?
3) How can i implement row level security in this approach?
Hi Sunkari,
My response to your questions below:
1) Creating workspace is currently not available in Azure from the front end interface, it can be done through code. We are also waiting for this feature to be available on Azure so that we can manage workspaces from Azure.
2) I think you can implement report level security via ReportEmbedTokens. Following URLs can be helpful.
https://msdn.microsoft.com/library/mt710366.aspx
3) You can implement a RLS as well. Please have a look at the below URL:
https://powerbi.microsoft.com/en-us/documentation/powerbi-admin-rls/
Regards,
Adeel
Hi InsulaBIDev
By setting value of parameter, we want to change the data of report based on user role and region. So option of ReportEmbedToken is not relevant because it will force us to create different report for different users.
Second RLS is still not available in PowerBI Embedded.
Hi sadiqkhoja,
Currently you can send a querystring parameter (indicating the dataset name and column name) at run time by which you can filter the records by user role or region but end user will be able to clear that filter from the report so you cant actually restrict the user not to clear the filter (as per my understanding). As this is still in preview, we might expect more enhancements in this regard.
However we have done a work around and it was fitting our needs, we have created separate workspaces for each customer/organization (not user). A customer may have many users accessing the reports. So by forcefully applying the customer Id at design time (under Edit Queries/Parameter) to view their organization related data, we have controlled this.
Every organization will be accessing their own workspace and report which has its own data in it.
May be you can think of a work around like that?
