Forum Discussion
DataFlow connectio to Power BI Rest API stopped working
Hi community.
As a magic trick my Power BI Dataflow pulling data from Power BI Rest API to query dataset refresh times stopped working.
I had this dataflow workign for a year now, one week ago stopped working with the message "An error occurred while communicating with another service, please try again later"
This error is on the first step where I am getting the Token from Power BI REst API.
Another issue is if I want to "get a new source" insight my dataset and I select another "dataflow", it will fail with same message.
How service work:
- I can interact with the Rest API using Postman using same parameters, it works ok
- If I create a new dataflow gen1 and copy/paste the code, the token negotiation works well.
It seems unexpected change in Microsoft has affected Dataflow Gen1 but not new ones when I create them
Solution:
a) Microsoft fix the issue they introduce.
b) I have to re-implement my dataflows (3 of them) and update all the reports currently pulling data from it as the guid will change and all my reports will stop working
Any idea ?
Regards and thanks
Hi.
After a support session with Microsoft, it seems we are forced now to use Privacy Level=Organiztional when you have connections to more than once source and few other issues they are enforcing now without comunicating.
- When you have a dataflow pulling data from more than one source
- Connection must have as Privacy level = "Organizational"
- It was a good practice before but now we are forced to set it up this way.
- On the other hand, my dataflow has been connecting to api.powerbi.com, now I have to setup the "Skip test connection" to get it working again, as some new fabric updates went trough the last month. In general, when using a token to interact with an API, we will have to skip connection always to avoid issues.
I hope this helps in case we face issues related to it...remember, to always use "Organizational"
- When you have a dataflow pulling data from more than one source
5 Replies
Hi.
After a support session with Microsoft, it seems we are forced now to use Privacy Level=Organiztional when you have connections to more than once source and few other issues they are enforcing now without comunicating.
- When you have a dataflow pulling data from more than one source
- Connection must have as Privacy level = "Organizational"
- It was a good practice before but now we are forced to set it up this way.
- On the other hand, my dataflow has been connecting to api.powerbi.com, now I have to setup the "Skip test connection" to get it working again, as some new fabric updates went trough the last month. In general, when using a token to interact with an API, we will have to skip connection always to avoid issues.
I hope this helps in case we face issues related to it...remember, to always use "Organizational"
- When you have a dataflow pulling data from more than one source
Hi. Well, it sounds like it depends on the hurry. If you need to fix this like now, you might need to go option b, recreate and edit all datasets to call the correct dataflow.
Otherwise you should rise a ticket to support becuase it looks like an issue. The message suggest that too. https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
I hope that helps,
Ticket already created, I will have a call with a microsoft support engineer, but I have no hope for a quick resolution.
Hi rivasrd ,
Thanks for reaching out to the Microsoft fabric community forum.Just checking in to see how things went with your support ticket and the call with Microsoft. Were they able to provide any updates or next steps?
Thank you.
rivasrd may be you can try these manually once
- Refresh Credentials Manually
- Go to Power BI Service → Workspace → Dataflow → Settings
- Under Data source credentials, re-authenticate or refresh the token manually
- This has resolved similar token errors for some users
- Recreate the Dataflow (Safest but Costly)
- As you noted, creating a new Gen1 dataflow and pasting the same code works
- Unfortunately, this changes the GUID, which breaks downstream dependencies unless you update all linked reports
- Try Gen2 Dataflows
- If you're on Premium, consider migrating to Dataflow Gen2, which offers better integration with Fabric and more robust token handling
- Browser-Specific Quirks
- Some users found that setup only works in Edge or Chrome, not Firefox or Safari
- Clear Cache & Reauthenticate
- Sign out of Power BI Service, clear browser cache, and sign back in
- Try editing the dataflow in an incognito window to bypass stale session tokens
- Refresh Credentials Manually
