Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Compete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.

Reply
Suparo
Frequent Visitor

Unable to use On-premises Dataflows connection in powerbi service

I've been using the Dataflows type connection in dataflows gen 1 to reference an other table i created in another dataflow. But the connection stopped working. I get the below error for the connection:

Unable to start OAuth login for this data source. Connection string is not supported.

Details: Server: Query contains unknown function name: PowerPlatform.Dataflows Unknown function name: PowerPlatform.Dataflows is a valid Mashup library function name format. Hence fail the operation. Please have this information handy if you choose to create a support ticket. Session Id: 8e860f28-a25a-4b48-8f74-ef27aa6b3f34 RequestId: d5889dd6-0cce-4ce8-8e49-4fad3f46431a Cluster URI: https://api.powerbi.com Status code: 400 Time: Wed Jul 30 2025 09:29:48 GMT+0200 (Central European Summer Time)
1 ACCEPTED SOLUTION

Hi @Suparo ,


Thank you for raising this issue. Others have encountered it as well, and it is related to recent Microsoft backend updates affecting Dataflows Gen1 connections, particularly with cross-dataflow references.

The PowerPlatform.Dataflows function for referencing other Gen1 dataflows is being deprecated, which causes “Unknown function name” and OAuth errors, since this method is no longer supported.

For Power BI Pro users:

  • Gen2 Dataflows, which allow linked dataflows, require a Premium or PPU workspace and are not available in Pro-only workspaces.
  • In Power BI Service, Power BI Datasets (now called Semantic Models) are not listed under “Get Data” and can only be accessed via Power BI Desktop.

Recommended actions:

  • Option 1: Use Power BI Desktop to connect to your dataflow as a dataset. Open Desktop, go to Get Data > Power BI Datasets, select your dataflow’s dataset (if it has refreshed), build your report, and publish it to the Service. This avoids OAuth errors and is the preferred workaround for Pro users.
  • Option 2: If possible, upgrade a workspace to PPU or Premium to use Gen2 and enable cross-dataflow references without these issues.

If you need help setting up the Desktop connection, please let me know. I am happy to assist.

Thank you.

 

View solution in original post

9 REPLIES 9
rohit1991
Super User
Super User

Hi @Suparo ,

 

This is catching a lot of people lately! Microsoft is phasing out the old Dataflows Gen1 connector, which is why you’re seeing those OAuth and cross-referencing errors.

 

Here’s what works:

 

  • If you can, move your dataflows to Gen2. Gen2 supports cross-referencing and is where all the new features are landing.

  • Or, in Power BI Desktop, connect using "Get Data" > "Power BI Datasets" Instead of the old Dataflows option, pull your tables in as Datasets. This method is stable and gets around the OAuth/connection problems.

That should get you back up and running. If you need help migrating to Gen2 or setting up the Datasets connection, just shout and I’ll walk you through it.


Did it work? ✔ Give a Kudo • Mark as Solution – help others too!

Hi Rohit
I have PowerBI Pro so I don't have access to Gen2. 
And I can't find Power BI Datasets or Semantic Model when I select Get Data. (I'm trying it in powerBI Services so i can plan the refresh of the dataflow)

Hi @Suparo ,


Thank you for raising this issue. Others have encountered it as well, and it is related to recent Microsoft backend updates affecting Dataflows Gen1 connections, particularly with cross-dataflow references.

The PowerPlatform.Dataflows function for referencing other Gen1 dataflows is being deprecated, which causes “Unknown function name” and OAuth errors, since this method is no longer supported.

For Power BI Pro users:

  • Gen2 Dataflows, which allow linked dataflows, require a Premium or PPU workspace and are not available in Pro-only workspaces.
  • In Power BI Service, Power BI Datasets (now called Semantic Models) are not listed under “Get Data” and can only be accessed via Power BI Desktop.

Recommended actions:

  • Option 1: Use Power BI Desktop to connect to your dataflow as a dataset. Open Desktop, go to Get Data > Power BI Datasets, select your dataflow’s dataset (if it has refreshed), build your report, and publish it to the Service. This avoids OAuth errors and is the preferred workaround for Pro users.
  • Option 2: If possible, upgrade a workspace to PPU or Premium to use Gen2 and enable cross-dataflow references without these issues.

If you need help setting up the Desktop connection, please let me know. I am happy to assist.

Thank you.

 

Hi @Suparo ,

 


I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

Hi @Suparo ,

 

I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

Thank you.

 

Hi @Suparo ,

 

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you.

Thank you.



Thank you.


v-tejrama
Community Support
Community Support

Hi @Suparo ,

 

Thank you @jaineshp  for the response provided!

Has your issue been resolved? If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.

Thank you for your understanding!

jaineshp
Power Participant
Power Participant

Hi @Suparo ,

This is a known issue with Dataflows Gen1 cross-referencing. The PowerPlatform.Dataflows function is being deprecated. Here's the fix:

Solution:

  1. Switch to Dataflows Gen2 (recommended) - the cross-dataflow references work properly there
  2. Alternative: Use Get Data → Power BI Datasets instead of the Dataflows connector to reference your dataflow tables

Quick Steps:

  • In Power Query: Get Data → Power Platform → Power BI Datasets
  • Select your workspace and the dataflow table you need
  • This bypasses the OAuth issue entirely

Root Cause: Microsoft is phasing out the old PowerPlatform.Dataflows connector in favor of the newer Power BI Datasets connection method.

Try the Power BI Datasets approach first - it should resolve your connection issue immediately.

Best Regards,
Jainesh Poojara | Power BI Developer

Hi Jainesh
I have PowerBI Pro so I don't have access to Gen2. 
And I can't find Power BI Datasets or Semantic Model when i select Get Data.

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.