We started to receive this error on the Microsoft “Emissions Impact Dashboard” recently.
Although the error message was clear enough I wasn’t sure how I could provide MFA to Power BI and the majority of the guidance online states to remove MFA as a requirement which is almost always a poor option in my experience.
The error we were receiving was as follows via an email notification –
Emissions Impact Dashboard has failed to refresh.
Read more: How to Fix Power BI “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”
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”,”parameters”:{“ConnectionDetails”:”{\”kind\”:\”Web\”,\”path\”:\”https://gw.us-il301.gateway.prod.island.powerapps.com/customerenrollmentservice/emissiondata\”}”,”CredentialType”:”OAuth2″,”DatasourceType”:”Web”},”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 ‘https://gw.us-il301.gateway.prod.island.powerapps.com’.\r\nTrace ID: 960ac688-57b2-4f0e-a957-4b49359b1b00\r\nCorrelation ID: 90deac3e-b6b2-415c-b972-143bdfe24b09\r\nTimestamp: 2023-05-24 23:15:03Z”}},{“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 ‘https://gw.us-il301.gateway.prod.island.powerapps.com’.\r\nTrace ID: 960ac688-57b2-4f0e-a957-4b49359b1b00\r\nCorrelation ID: 90deac3e-b6b2-415c-b972-143bdfe24b09\r\nTimestamp: 2023-05-24 23:15:03Z”}},{“code”:”DM_ErrorDetailNameCode_UnderlyingHResult”,”detail”:{“type”:1,”value”:”-2146233088″}}],”exceptionCulprit”:1}}} Table: TenantUsage.
The Solution
The solution in this case is to manually refresh the credentials used in the Data Source of the App. This can be done by following the steps below –
- Navigate to the affected Power BI Dashboard.
- Select the ellipses (…) in the menu at the top, then select View dataset.
- Click File then Settings.
- Expand the Data source credentials section.
- Click Edit credentials and then select Sign in.
- You’ll be asked to provide any required credentials again or be able to select a new user here.
- Refresh the data source and it should now populate as expected.