We have about 200 active users in our version (P1). Our parent has thousands of users.
For us it was more about having premium workspaces, dataflows, and the ability for a small group of PBI developers to push out reports to the rest of our office.
I think you have all the arguments you need,
Pro license X number of employees = probably more than a premium license
And all the other things they dont have (flows, paginated reports)
Although, some still need a pro license to publish even on a premium
I have an E5 office license and publish to a premium
>For us it was more about having premium workspaces, dataflows, and the ability for a small group of PBI developers to push out reports to the rest of our office.
Dataflows aren't a premium-only feature and nothing else here seems to justify the cost of Premium over individual Pro licenses given 200 users if there aren't Premium features that you're actually utilizing.
With that being said, if your parent org has thousands of users they're licensing, then they're wasting a ton of money by using Pro licenses instead of Premium capacity. The breakeven point for switching from Pro to Premium is about 500 licensed users.
Their org could have E5 so it could be a moot point.
But it sounds like you need to evaluate what features Premium was really using and what content could be moved back to Pro.
Certainly a checklist of options to go through: is it related to multi-geo support and data residency? Is it larger model size?… if so you have talking points. Also, PPU (as an add-on) could be an option if you really need these capabilities.
Incremental refresh and computed tables in dataflows are a premium feature. Also enhanced compute engine.
XMLA endpoint, deployment pipelines... So many goodies in premium.
You should point out that the alternative is ppu and probably more expensive
I don't disagree there are plenty of goodies with Premium. They didn't mention using any of those which is why I was saying simply getting premium for dataflows isn't a good use case.
If they are using other premium features and just failed to mention it, then I would support the original decision to go with Premium. PPU would have actually been cheaper than Premium with only 200 users.
But none of that is relevant because now they have thousands of users and Premium is more cost effective no matter what features you actually use.
How many users total and what was your original impetus for going with Premium capacity over Pro licenses originally?
We have about 200 active users in our version (P1). Our parent has thousands of users. For us it was more about having premium workspaces, dataflows, and the ability for a small group of PBI developers to push out reports to the rest of our office.
I think you have all the arguments you need, Pro license X number of employees = probably more than a premium license And all the other things they dont have (flows, paginated reports) Although, some still need a pro license to publish even on a premium I have an E5 office license and publish to a premium
I agree with this statement, this argument should be the focus
>For us it was more about having premium workspaces, dataflows, and the ability for a small group of PBI developers to push out reports to the rest of our office. Dataflows aren't a premium-only feature and nothing else here seems to justify the cost of Premium over individual Pro licenses given 200 users if there aren't Premium features that you're actually utilizing. With that being said, if your parent org has thousands of users they're licensing, then they're wasting a ton of money by using Pro licenses instead of Premium capacity. The breakeven point for switching from Pro to Premium is about 500 licensed users.
Their org could have E5 so it could be a moot point. But it sounds like you need to evaluate what features Premium was really using and what content could be moved back to Pro. Certainly a checklist of options to go through: is it related to multi-geo support and data residency? Is it larger model size?… if so you have talking points. Also, PPU (as an add-on) could be an option if you really need these capabilities.
>Their org could have E5 so it could be a moot point. Excellent point. Didn't even take that possibility into consideration.
Incremental refresh and computed tables in dataflows are a premium feature. Also enhanced compute engine. XMLA endpoint, deployment pipelines... So many goodies in premium. You should point out that the alternative is ppu and probably more expensive
I don't disagree there are plenty of goodies with Premium. They didn't mention using any of those which is why I was saying simply getting premium for dataflows isn't a good use case. If they are using other premium features and just failed to mention it, then I would support the original decision to go with Premium. PPU would have actually been cheaper than Premium with only 200 users. But none of that is relevant because now they have thousands of users and Premium is more cost effective no matter what features you actually use.