Forum Discussion
Power BI Dashboards Failing: Unable to Update Data Source Credentials
Hi Team,
I am experiencing an issue with the Power BI service where all of my dashboards are failing with an “Access Denied” error. I do have access to the data sources, but when I try to update the credentials in the service, I receive the following message:
“Failed to update data source credentials: We're sorry, an error occurred during evaluation.”
Kindly assist me in resolving this issue.
Thank you!
Hi v-anyerr ,
Thanks for sharing those details and the screenshot. Since you’re able to refresh the dataset in Desktop and the issue only appears in the Service when updating credentials, this usually points to a service-side authentication or connector issue rather than your credentials.
A couple of things you can try that often resolve this.
1.Clear and Re-add Credentials
Go to Power BI Service → Dataset → Settings → Data source credentials.
Remove the existing credentials and re-authenticate using the same method you used in Desktop (OAuth/Basic).2.Re-Publish the PBIX
Sign out and sign back in on Power BI Desktop, then republish the report. This forces a token refresh on the Service side.
3.Check Privacy Levels & Parameters
Make sure they’re set consistently in both Desktop and Service.
If it still fails after trying these steps, it could be related to a temporary issue with the connector (we’ve seen similar behavior recently with cloud connectors like Google Sheets). You can also check the Power BI Support page for any active incidents.
As a quick workaround while this gets resolved, you can manually refresh from Desktop and republish to keep your dashboards up-to-date.
Let us know if these steps help or if the issue persists we can dig deeper together.
Regards,
Akhil.
6 Replies
Hi v-anyerr ,
Thanks for sharing those details and the screenshot. Since you’re able to refresh the dataset in Desktop and the issue only appears in the Service when updating credentials, this usually points to a service-side authentication or connector issue rather than your credentials.
A couple of things you can try that often resolve this.
1.Clear and Re-add Credentials
Go to Power BI Service → Dataset → Settings → Data source credentials.
Remove the existing credentials and re-authenticate using the same method you used in Desktop (OAuth/Basic).2.Re-Publish the PBIX
Sign out and sign back in on Power BI Desktop, then republish the report. This forces a token refresh on the Service side.
3.Check Privacy Levels & Parameters
Make sure they’re set consistently in both Desktop and Service.
If it still fails after trying these steps, it could be related to a temporary issue with the connector (we’ve seen similar behavior recently with cloud connectors like Google Sheets). You can also check the Power BI Support page for any active incidents.
As a quick workaround while this gets resolved, you can manually refresh from Desktop and republish to keep your dashboards up-to-date.
Let us know if these steps help or if the issue persists we can dig deeper together.
Regards,
Akhil.Thank you. It seems to have been a temporary issue, which is now resolved, and I am able to set up the auto refresh.
Hi, Thank you for your response. I am able to refresh the data source successfully in Power BI Desktop. However, I am encountering an issue when configuring the schedule auto refresh in Power BI Service. Here is the error screenshot
If source is on-prem → install & map an On-premises data gateway.
Go to Service → Dataset → Data source credentials, delete & re-enter with the correct auth type.
Check parameters & privacy levels → update them in Service.
For Web APIs with headers → must use a gateway or switch to query-string/basic auth.
Hi Shahid12523 , Thank you for your reply. My data source is cloud based, and I am using a cloud connection, so no gateway is required. It was running fine until this morning, from then it has started failing with “Access Denied” error. I tried to update my credentials but getting the following error,
“Failed to update data source credentials: We're sorry, an error occurred during evaluation.”
