01-25-2017 01:29 AM
This "fix" is very unfortunate and a huge deal-breaker for our company.
Like Bhartman30 - I too work in a company where a small amount of Pro-users (aprox. 5 developers) keep and maintain the dashboards/reports in a PowerBI group so that we can fill in for each other. But it was previously possible for all the end-users (currently aprox. 200 people) to view the final reports with free-licenses.
Now without prior warning all end-users has been locked out of the reports, and they suddenly require a Pro-license simply to view the reports. This is a huge stepback both for our current work-processes in the company, but also a stepback for our journey to furhter integrate PowerBI in the company.
Historically we have been using Tableau, but during the last year we have slowly moved towards Microsoft PowerBI due to a more attractive pricing model. Tableau costs 2.000$ per developer for a lifetime license, while PowerBI only cost 10$ pr. month per Pro-license. But with Tableau only the report developers need a license while all end-users can view reports free of charge.
Our hope was to expand the use of PowerBI from the current 200 end-users to about 2.000 end-users. The pricing argument is now all of the sudden no longer a valid argument for us to help push this PowerBI integration since it is now:
5 developers x 2.000$= 10.000$ (lifetime)
2.000 end-users x 0$ = 0$
5 developers x 10$ = 50$ (per year)
2.000 end-users x 10$ = 20.000$ (per year)
01-25-2017 08:21 AM - edited 01-25-2017 12:52 PM
If you were storing a report within a Group Workspace and/or allowing your report to connect to data sources using an On-Premises
Gateway, while the users consuming the report were users with free licenses, you were in direct conflict with the documentation.
I do not believe this is a setback, but rather a planning step that did not take place on the individual(s) that architected the solution.
01-25-2017 12:42 PM - edited 01-25-2017 12:43 PM
Unfortunately in my experience with MS documentation and actuals, there are numerous direct conflicts.
In this case they could have just as easily changed the wording in the documentation and left the feature of Workspaces functioning with Free Licenses. However, they chose to remove a working feature that many people have been using. So in this case it is neither an architectural issue or a user issue, it is a decision by MS team to eliminate a functioning feature.
Have a great rest of your day!
01-25-2017 12:50 PM
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.
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 dataset that refreshes more frequently than daily.
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.
01-26-2017 12:13 AM
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.
01-31-2017 02:32 AM
Indeed we need the group workspace to work together on the dashboards as developers. It is the only way to back-up eachother in publishing the dashboards.
Now we have to crecreate them on our personal accounts and hope nothing goes wrong in our absense !
Please make a distinction between developing in PRO en consuming the reports. We are willing to pay for developers and super-users, but not for the whole company!
02-13-2017 11:00 AM
You seem to miss the point of everyone's frustrations. While what you say is true of "what is pro content," some of those items are things that make using PowerBI a total deal breaker for mostly every company out there in one way or another.
For example, RLS. Consuming a report locked down for security, shouldn't not require the end user to have a pro-liscense!
I want to automate about 10 Excel reports to avoid manual reporting, and then share truncated data specific to one employees stats and performance without them seeing their peers numbers. ME having a pro-liscense makes sense to have the ability to lock out their ability to filter the report/dashboard to a co-worker. For them to read it? Insanity!
Microsoft would probably see a higher drive in adoption of pro subscriptions if they allowed view only access to all users of any reports created with pro features. Consumption is very different from collaboration or content creation.
The pro liscense truly should be based upon a user's ability to create not consume. This would be like charging an extra $10 a month to everyone in an organization to read a read only word document on top of their O365 subscription. In my org, where we have 60,000+ employees, if MS thinks we would pay $600,000 a MONTH for the privalge of reading a report, they are out of their bloody minds.
In the above scenario, we will spend $0. If they allowed consumption of reports made with pro liscense, we might have a thousand users a month who would be able to have a pro liscense. That would be revenue vs. no revenue, and it seems to be a consensus as these things keep coming up.
We are already paying for 40,000 O365 subscriptions....
02-15-2017 09:34 PM
Also dishearted to see this fix go out. It will probably be a deal breaker for my organization as well as the costs to deploy to my group of thousands of employees will be significantly higher than competing software from Tableau or Qlik Sense.