Forum Discussion
Fixes to Power BI Pro License Required Dialogs
I would love to see where the conflict was found within regards to this issue. Would you be willing to point it out?
The problem is not "Workspaces" in general, but with Group Workspaces. The content within a Group Workspace is and has been, clearly defined as a Pro feature all along.
The individual architecting the solution needs to clear those items before creating a solution of any size.
A Free user consuming content from within a Group Workspace is a clear, very clear violation of the documentation.
Thoughts?
https://powerbi.microsoft.com/en-us/documentation/powerbi-power-bi-pro-content-what-is-it/
Power BI Pro content - what is it?
Power BI free and Pro licenses are different based on the kind of content users can consume. If your content contains any of the following items, it's Power BI Pro content:
Data from a DirectQuery dataset, such as SQL Server Analysis Services tabular data, Azure SQL Database, Azure SQL Data Warehouse, or Apache Spark for HDInsight.
Data from a dataset that refreshes more frequently than daily.
Data from a dataset that connects to on-premises data using the Power BI Gateway - Personal or the On-premises Data Gateway.
Data from a live connection to Azure Analysis Services.
Data (including reports, dashboards or tiles) from a dataset that uses Row-level security (RLS).
A dashboard or report that's installed from an organizational content pack.
A dashboard, report, or dataset that's contained in a group workspace.
A dashboard that contains data streamed at a rate above 10k rows/hour.
Conversely, if your content contains only the following items it will be consumable by both Power BI free and Pro users:
A dashboard or report connected to content packs for services (e.g. Dynamics CRM, Salesforce, and Google Analytics).
A dashboard or report with data imported from files such as Excel spreadsheets, Power BI Desktop, and CSV.
Tiles pinned from a report in SQL Server Reporting Services.
For example, if you create a manufacturing dashboard that updates progress multiple times during the day, anyone consuming that dashboard would need a Power BI Pro license. Or, if you create a report using the Power BI Gateway - Enterprise, then another that uses the personal gateway, anyone consuming or interacting with either of those reports would need a Power BI Pro license.
If you want to share your Power BI Pro content with users, they can sign up for a free trial of Power BI Pro, and gain access to your content during the trial period.
For a list of Power BI Pro features (and how those features compare to a free Power BI license), take a look at Power BI Pricing.
I understand the "fix" is to align with documentation, but I still don't understand the design choice behind this (other than money obviously).
To use a web-analogi:
If I store my website on my personal server where only I have access, I can administrate it free of charge, and likewise the visitors can view the site free of charge.
If I instead stored my website on a corporate server, I'd need to pay for a pro-license, and so would all other admins and web-developers working on the particular site. But the visitors should not need to pay(?)
This is the case with Tableau where only developers and admins need to pay, not every single end-user.