Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. 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/
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.