Not able to access dataflow

[Anonymous]

Hi community,

I am suddenly having issues wih accessing any dataflow in a premium workspace.  I am getting the error as follows:

ProPlusInformationNotAllowedForNonProPlusCaller: ProPlusInformationNotAllowedForNonProPlusCaller
Details:
Error=ProPlusInformationNotAllowedForNonProPlusCaller
RequestId=2caac5ec-8c1b-45f6-b086-ebaadfc0eb41

Can anyone suggest some solution??

[v-robertq-msft]

Hi, @Anonymous 

To make sure you can access any dataflow within your premium workspace, I think you should first go to check if the Dataflow option has been enabled in the admin center if you have the admin account of your tenant:

You can also follow this document to make some troubleshooting:

https://docs.microsoft.com/en-us/power-query/dataflows/troubleshooting-dataflows-issues-creating-dataflow

More info about “Configure and consume a dataflow”

Best Regards,

Community Support Team _Robert Qin

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

[Anonymous]

All the settings are good, still getting the error, have raised a ticket with the support.

[graemeg]

I am experiencing exactly the same problem with the same error.  Power BI desktop will not connect to a Dataflow in a Premium per User Capacity Workspace.  I have Premium per User licencing.

[Anonymous]

@graemeg  I am still awaiting response from Microsoft Support. Any solution at your end?

[graemeg]

No response from Microsoft and no solution.  I'm going to run a test today going through a very specific set of steps to see if I can reliably replicate the problem using a new workspace.

[Anonymous]

Hi @graemeg, 

any solution at your end?  Microsoft Support mentiond they will be fixing the bug in the last week of May.

[graemeg]

Unfortunately no solution.  I tried it again with a different dataset (linking two dataflows together in the Power BI service) which requires premium capacity workspace in the service.  Getting the same error from the Power BI desktop.  Very frustrating.  I guess I need to wait until the last week of May for Microsoft to fix the bug.