Why is my #PowerBI dataflow refresh failing
I was recently testing out the new awesome dataflows in Power BI, and no matter what I did my dataflow refresh would fail.
I was getting the same error no matter what I did.
In order to find the error details for my dataflow I did the following:
- I went into my App Workspace and then clicked on the settings Icon and then Settings
-
I then clicked on Dataflows in the settings
-
I then clicked on Refresh History and selected the download button
- This then downloaded the CSV as shown below.
This is the error that I was getting.
I thought let me see if I can try out a few different scenarios to troubleshoot where the issue was coming from.
- I tried creating an App Workspace in V1 – Still failing on the refresh
- I tried creating an App Workspace in V2 – Still failing on the refresh
-
Next, I thought it might well possibly be my M code or a connection to my data.
- I used Power BI desktop to create a table where I entered the data manually and did one transformation.
- IT STILL FAILED
- All of them were failing with the Duration being 0 or 1 second, that to me was a little worrying!
-
Starting to doubt myself, I am fortunate to have other Power BI tenants that I could try and see if it worked on another Power BI tenant.
- Low and behold it worked perfectly on another Power BI tenant.
Now I was thinking, what is going on with my own Power BI tenant?
Was it something I did?
Was there some setting that I possibly changed?
I then reached out to the Power BI team and asked for assistance.
I must give a big shout out to Anton, Sagiv and Bat-chen from the dataflows team, they assisted me in troubleshooting the issue.
The cause of why my Power BI dataflow refresh was failing
The reason it was failing is because on the account I was using I have got Multi-Factor Authentication (MFA) enabled.
This now makes total sense, because in the other Power BI tenant I was testing on, it was a standard account with no MFA enabled.
As you can see below in the muti-factor authentication settings my account has a status of Enforced
Short Term Solution
The wonderful people from the dataflows team advised as a short-term solution to use an account that does not have MFA
I tested this and it worked perfectly!
Long Term Solution
The people in the dataflows team, are fixing this problem but it will take some time.
Once I have an update from them and I can verify that it does indeed work, I will update this blog post.
Conclusion
I hope that you now know if you have an account with MFA and are currently using it for dataflows you could get some unknown errors.
And that there is both a short term and a long-term solution.
Any questions or comments please leave it in the section below!
Thanks for reading.
I ran into the same problem with MS Flow refreshes failing because of MFA, and came to the conclusion that for production purposes it’s best to use “service” shared accounts rather than regular mailboxes used by individuals. With browser profiles it’s relatively painless to switch to a different account whenever you need to admin your recurring processes (Power BI refreshes, dataflow refreshes, Flow, etc). Another benefit is that you don’t have to worry about what happens to your recurring processes whenever individuals leave the team.
You can push notifications sent to that service email to “human” mailboxes with Flow, or configure Outlook to load the shared mailbox. This setup also solves the fact that Power BI only sends refresh notification failures to the owner of the dataset (so you’ll want to transfer dataset ownership to the service account).
Hi there,
Thanks for the details in your comment. and I totally agree. If possible use a Service Account, which makes the entire process easier and not so difficult to configure.
Hi there Gilbert – curious if you’d heard any updates from the dataflows team since your blog post. I’ve recently encountered this issue and will go with a service account, as both you & Olivier have suggested..
Hi Greg,
As far as I know I have not heard any updates unfortunately!
Thanks for the reply Gilbert! I’ll go with the short term option you presented for now.. Thanks for this blog post!