Forum Discussion
Enterprise Gateway - greyed out, why?
Ou, one important thing I forgot to mention... My on-premises SharePoint has other credentials than I have on my computer or for the Power BI service. Power BI = Office 365 = my Computer. For SharePoint I have other credentials. Thats the reason why I cannot use the personal gateway, i think. In the Power BI Desktop I can give each data source alternative credentials, thats perfect. But you don't have the possibility to do that for a data source on app.powerbi.com. So I thought in my Case I need the enterprise version. But it's greyed out...
- TealCanady10 years agoAdvocate II
If you have different credentials in your on premise data sourc; the users online technically can't access the data because you can't add their credentials in. A common occurence of this is using mydomain.local in active directory. You may need to establish a UPN for these users in Activie directory using their online accounts.
https://powerbi.microsoft.com/en-us/documentation/powerbi-admin-power-bi-security/Hope this helps!
Teal Canady
Sr. Data Architect
- ajone10710 years agoNew Member
Hello,
I have this same error. I am confused by your response. Are you saying that individuals on a .local domain need to add a UPN to allow the Enterprise/Personal data gateways to work? What would the UPN look like to work with MSFT cloud services?
Please advise as this has been a major headache for me. I have had to use a 3rd party tool called PowerUpdate to get my refresh to work.
Thanks,
Adam
- TealCanady10 years agoAdvocate II
Adam,
Can you connect through the desktop edition of power bi to the sharepoint list? If so then I may be way off base and all you would have to do is push the local power bi desktop file to the cloud; provided they are the same data source then it will use the enterprise gateway for the future. If not then an explination of UPN is below.
So to connect to your on premise data source lets go through the scenario. You have installed the Power BI Enterprise Gateway on a server and everything connects to Sharepint etc. You have a user online that has access, [email protected].In the app.powerbi.com you login with [email protected]
Locally you log in to sharepoint with [email protected]
Power BI can't make the connection to sharepoint because there are no permissions for [email protected] present. When Power BI connects to the enterprise gateway it calls on your Active Directory Server to get an effective username; so it tries to look up [email protected] and it does not exist.
A UPN on user [email protected] that reads as [email protected] allows the security to translate those two different users. A UPN makes it so that when you login and try to query with [email protected] it uses the security from [email protected] as the effective username.
I'm sorry to say I don't have sharepoint to test this out for you; i'm basing this on my experience with on premise tabular models.Teal Canady