The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
We've got a similar issue to this person:
Basically we have all our data locally in a Tabular AS instance. Access to this via PowerBI Desktop works perfectly and as expected. However when we deploy to app.powerbi.com we can't access any of the data.
Our network guys have verified the problem by setting up a new user who's local UPN is in the same format as Office 365 (eg
pbitestuser@companyname.com
And this works. However we have an organisation with hundreds of users who don't have UPN's formatted like this (our local logins are NETWORK/Person1.
My question is: Is there a workaround that doesn't involve federating all of our local AD accounts to Office 365?
This has been scoped as a costly and time consuming task however it's the only thing stopping us from being able to roll out PowerBI successfully (data is ready, tabular model ready, Desktop works fantastically, dashboards ready...this is our last hurdle).
Are there any options to help SSAS Tabular translate logins in the Enterprise Gateway??