Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Vote for your favorite vizzies from the Power BI Dataviz World Championship submissions. Vote now!
Unable to update connection credentials. The on-premises data gateway's service account failed to impersonate the user.
Kindly help me resolve this error.
Solved! Go to Solution.
Hii @a-vdarute
If the error still persists after assigning permissions and restarting the gateway, the most likely cause is a Kerberos / impersonation mismatch between the gateway and the data source. As a next step, try switching the data source to use explicit credentials (for example, SQL authentication instead of Windows), or configure Kerberos delegation (double-hop) correctly if Windows authentication is required. Also verify that the same gateway is mapped to the dataset, the service account password hasn’t changed, and re-add the data source in the gateway cluster before updating credentials again.
Hi @a-vdarute,
Thank you for reaching out to Microsoft Fabric Community.
Thank you @rohit1991 for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Hi @a-vdarute,
We wanted to kindly follow up to check if the solution provided by the user for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Hii @a-vdarute
This error usually occurs when the on-premises data gateway service account does not have permission to impersonate the user credentials used for the data source. Make sure the gateway is running under a domain service account (not Local System), that this account has Log on as a service rights, and that the authentication method matches the data source (for example, use SQL authentication if Kerberos delegation isn’t configured). After updating permissions, restart the gateway service and re-enter the credentials in the Power BI Service.
Thank you for your response, @rohit1991 .
I have followed all the steps you suggested, including granting the required permissions to the gateway service account and restarting the On‑premises Data Gateway service. However, I am still encountering the same error.
Hii @a-vdarute
If the error still persists after assigning permissions and restarting the gateway, the most likely cause is a Kerberos / impersonation mismatch between the gateway and the data source. As a next step, try switching the data source to use explicit credentials (for example, SQL authentication instead of Windows), or configure Kerberos delegation (double-hop) correctly if Windows authentication is required. Also verify that the same gateway is mapped to the dataset, the service account password hasn’t changed, and re-add the data source in the gateway cluster before updating credentials again.
Vote for your favorite vizzies from the Power BI World Championship submissions!
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 19 | |
| 13 | |
| 10 | |
| 9 | |
| 7 |
| User | Count |
|---|---|
| 47 | |
| 40 | |
| 39 | |
| 25 | |
| 25 |