Forum Discussion
Unable To Publish PowerBI Report Build With SSAS Live Connection
Hi SMMubashir01 ,
Thanks for clarifying that you’re using a local Windows account and not AD. In this setup, the issue is that UPN mapping does not work with local accounts. For SSAS live connections, Power BI sends the signed-in Power BI account as the EffectiveUserName. That value must resolve to a valid domain identity in Active Directory. Local accounts aren’t part of a domain, so the mapping you tried with Mubashir-PC\Mubashir won’t be recognized by SSAS, and the connection will continue to fail.
In other words, SSAS live connections through the gateway require the SSAS server to be domain-joined and the accounts to be domain identities. Without AD, the translation from Power BI identity to SSAS user identity can’t happen, which is why you’re seeing the persistent “data source access error.”
You can review Microsoft’s explanation of how authentication with Analysis Services live connections works here:
https://powerbi.microsoft.com/en-us/blog/how-authentication-with-analysis-services-live-connections-works/There’s also a similar discussion on this in the community:
https://community.fabric.microsoft.com/t5/Power-Query/SSAS-MD-Power-BI-Gateway-Effective-user-names/td-p/210235Hope this helps. Please reach out for further assistance.
Thank you.
Thanks for your reply. Most of the guidance provided relates to Active Directory (AD), but in my case we are not using AD. Instead, I am only using a local Windows user account.
Here is what I have done so far:
Changed the On-Premises Data Gateway service account in services.msc from
NT Service\PBIEgwService → Mubashir-PC\Mubashir.In the Gateway Connection (Manage Connections and Gateway), added an EffectiveUserName mapping rule:
Replace: [email protected]
With: Mubashir-PC\Mubashir
Restarted the Gateway service.
Published the Power BI report again.
Result:
I am still getting the same error message:
"There was a datasource access error. Please contact the Gateway Administrator."
Community SupportHi SMMubashir01 ,
Thanks for clarifying that you’re using a local Windows account and not AD. In this setup, the issue is that UPN mapping does not work with local accounts. For SSAS live connections, Power BI sends the signed-in Power BI account as the EffectiveUserName. That value must resolve to a valid domain identity in Active Directory. Local accounts aren’t part of a domain, so the mapping you tried with Mubashir-PC\Mubashir won’t be recognized by SSAS, and the connection will continue to fail.
In other words, SSAS live connections through the gateway require the SSAS server to be domain-joined and the accounts to be domain identities. Without AD, the translation from Power BI identity to SSAS user identity can’t happen, which is why you’re seeing the persistent “data source access error.”
You can review Microsoft’s explanation of how authentication with Analysis Services live connections works here:
https://powerbi.microsoft.com/en-us/blog/how-authentication-with-analysis-services-live-connections-works/
There’s also a similar discussion on this in the community:
https://community.fabric.microsoft.com/t5/Power-Query/SSAS-MD-Power-BI-Gateway-Effective-user-names/td-p/210235
Hope this helps. Please reach out for further assistance.
Thank you.
- v-veshwara-msft
Hi SMMubashir01 ,
Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.
Thank you.