Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi all,
Something strange is going on, hope you can help me. I only experience this refresh problem with two of our customers.
The situation: I published a dataset with connections to azure datalake (ondemand.sql.azuresynapse.net). Next I enabled the refresh schedule and put in my Oauth credentials.
The next day I get this message:
Report has failed to refresh.
Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.
{"error":{"code":"DMTS_OAuthTokenRefreshFailedError","pbi.error":{"code":"DMTS_OAuthTokenRefreshFailedError","details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access
Really strange as this only happens with two of our customers. Any ideas?
Hi @RH205 ,
Has your problem been solved, please accept the correct answer as solution if it has been solved.Thank you
Best Regards,
Xianda Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @RH205 ,
The error code AADSTS50076 suggests that a configuration change requiring MFA for access might be the root cause of this issue.
I think you can check if there have been any recent changes in your organization's security policies that mandate the use of MFA for accessing resources like Azure Data Lake. This could be the reason why the refresh is failing for these specific customers.
At the end of the checking step, if the error is not effectively resolved, you can republish the report and then configure a scheduled refresh.
Best Regards,
Xianda Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
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.
| User | Count |
|---|---|
| 11 | |
| 11 | |
| 9 | |
| 9 | |
| 8 |