PPU Dataflow Error = Premium caller trying to read premium per user information.

[nishantdatanomy]

Hi, 

I have a dataflows in a PPU workspace that uses a linked table from the same PPU workspace. It worked fine in February however it is no longer working and giving me the following error.

Any ideas what might have changed?

PPUInformationNotAllowedForPremiumCaller: Premium caller trying to read premium per user information.

Thanks

Nishant

[TR_KY_PBI]

Last week, my case rep received an update from the Product Manager:

"

I talked to our product manager and he confirmed this is the desired behavior.

He admits that the documentation is not clear enough, and is going to update it.

But the general idea is PPU license is a limited license, one of the limitations is you can’t share data between tenants.

so a dataset from a different tenant (which also uses PPU) can’t pull data from a dataflow in a different tenant also using PPU)"

Any luck finding an alternative solution?

[nishantdatanomy]

Hi 

I can confirm that this is the desired behaviour of the product. I had created a ticket and the conclusion was that the same. 

In my case, I was trying to do this in my client's tenant. When I try to create the dataflow in my client's tenant. When I try to create a linked table, it was showing me the list of dataflows from my tenant, although I was trying to create the dataflow in my client's tenant (I was using guest account). 

As I was tyring to access the dataflows between 2 tenants, the error makes sense. 

Nishant

[TR_KY_PBI]

Hey @nishantdatanomy  - any luck getting this sorted out?

After a few weeks of waiting for action from the team managing my case, I received this response:

Quote:

“You cannot have a dataflow run in a PPU workspace, be imported into a Power BI dataset in another workspace, and then allow users without a PPU license to consume the content.”

Unfortunately, the case team seems stuck on the same line from the documentation, and doesn't seem to understand our issue has nothing to do with non-PPU users. 

Hopefully you are beving better luck than I am!

[v-xiaoyan-msft]

Hi @nishantdatanomy ,

Based on the above information, if you are a Power BI Pro licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

The link of Power BI Support: Support | Microsoft Power BI

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community

Best Regards,
Community Support Team _ Caitlyn

[TR_KY_PBI]

@nishantdatanomy - Not a bad idea creating a case. 

Be aware that I have had an open case with Microsoft (currently with their "internal team") on this issue for more than 4 weeks, but the more open cases they have related to this problem, (hopefully) the more resources they dedicate to its resolution

[v-xiaoyan-msft]

Hi @nishantdatanomy ,

After verifying with our product the reply  is:

Based on the documentation: https://docs.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-features-limitations

Quote: “When a dataflow is refreshed in a Premium Per User (PPU) context, the data is not visible to non-PPU users”

And on this: https://docs.microsoft.com/en-us/power-bi/enterprise/service-premium-per-user-faq

Quote: “You cannot have a dataflow run in a PPU workspace, be imported into a Power BI dataset in another workspace, and then allow users without a PPU license to consume the content.”

Both connectors should have no allowed it. It's a design issue.

Best Regards,
Community Support Team _ Caitlyn

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

[TR_KY_PBI]

Both @nishantdatanomy and I are having this issue entirely in Premium workspaces using PPU licenses.  I'll let him confirm, but in my case, all workspaces/users involved are Premium/PPU.  There are no non-PPU users or workspaces involved.

[nishantdatanomy]

I agree with @TR_KY_PBI. 

The issue is not with Power BI Desktop. My issue is with PPU workspace. In my case, both child and parent dataflows are in the same workspace so it can't be due to the limitations of PPU workspaces

Thanks

Nishant

[TR_KY_PBI]

I am having the same issue:

Error = "PPUInformationNotAllowedForPremiumCaller"

I receive this error any time I attempt to query a dataflow in a Premium workspace from a dataflow or dataset in another service tenant.  It had been working fine since earlier in the year (Feb), but began failing on 3/15.  I am able to  connect from a .pbix w/o any issues.

I've had critical a case open with Microsoft for almost 4 weeks; they seem to have no idea what is going on.  Been getting the same response (we are working on the issue....  update you asap....  appreciate patience....)

Current workaround is to manually refresh all linked datasets in pbix every day and republish.  Not sustainable.

Anyone else having this issue?

[nishantdatanomy]

@v-yingjl 

This same issue was resolved by you for Power BI Desktop. However, I am getting this error in Power BI Service. Can you pleased look into this as well as it seems they are related. 

https://community.powerbi.com/t5/Issues/PPUInformationNotAllowedForPremiumCaller-Premium-caller-tryi... 

Thanks

[nishantdatanomy]

No, I am not trying to access this in Power BI Desktop. 

I get this error message when I try to create a dataflow in Power BI Service. 

[nickyvv]

There is a similar issue reported here:

https://community.powerbi.com/t5/Issues/PPUInformationNotAllowedForPremiumCaller-Premium-caller-tryi...

Are you also trying to access the dataflow in Power BI Desktop? Please try un- and re-installing Power BI Desktop and try again.