Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi
Anybody else came across this? We had a few of our dataflows failing during scheduled refresh over the weekend. They are all connected to different sources (eg SharePoint folders, OneDrive folders, direct API pulls via HTTP), but the various errors all indicate credentials problems.
Now - we do use the same service account to authenticate some of these, but also others that refreshed fine. There are also no failed logins registered in those account logs in AAD against the MS365 logins or the SharePoint authention itself. Conversely for example the API pulls are secured through their own secrets and do not use those credentials at all. So we do not believe it was an account lock or password issue. There really is no pattern here 😕
I attempted to fix by resetting the dataflow credentials, but in one flow the option was greyed out entirely. And in the others, editing resulted in various errors with account & password combo which I know for sure is working fine elsewhere.
I have been able to work around this by recreating all of these flows which forced the credentials re-creation to. The new flows work and refresh without a hitch. But I would like to root cause this as we have no idea what has triggered it, why only these few flows were affected, or when/why it could reoccur.
Any point in the right direction to get to the bottom of this problem appreciated.
_Anna
Solved! Go to Solution.
Thank you @lbendlin. We did log directly and they confirmed it was an issue on their end. Also mentioned we were not the only ones affected.
To quote their support: "we have received a confirmation from the Product team that there was a regression in the backend which is fixed by the team."
Dataflows refreshed fine after that.
Thank you @lbendlin. We did log directly and they confirmed it was an issue on their end. Also mentioned we were not the only ones affected.
To quote their support: "we have received a confirmation from the Product team that there was a regression in the backend which is fixed by the team."
Dataflows refreshed fine after that.
We have seen similar behavior on our tenant. If you have a Pro license you can consider raising a Pro ticket at https://powerbi.microsoft.com/en-us/support/pro/
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
56 | |
27 | |
23 | |
21 | |
19 |
User | Count |
---|---|
48 | |
24 | |
20 | |
20 | |
17 |