Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi,
We're currently trying to use an Azure Data Lake Storage (gen2) as data source for a Power BI report, specifically for its finegrained ACL capabilities.
The issue is as follows: When designing the report in Power BI Desktop, it's easy to work with the connector. Data is retrieved and refreshed without issue. However, when publishing it to a Power BI Service workspace, it is no longer able to refresh due to invalid credentials. When trying to update the credentials, the same issue occurs:
Things we've already checked:
1. Check if ACL's are arranged correctly (also works fine locally)
2. Use a service account without 2FA enabled for scheduling
3. Check if PowerBI and storage account are in same tenant (yes)
Is this just not supported, or is this a bug?
Thanks for the help!
Kind regards,
Maarten
Solved! Go to Solution.
@lmb2This seems to be a different error, specifically saying the credentials you are using are incorrect. For me I was unable to update the credentials, even though they were correct.
It is worth noting that we tested this again last May, using the exact same setup as initially, and it worked without issue. Perhaps there was a delayed release to our tenant, but it is now functioning as described.
I have the same issue. The error message is only "Invalid Credentials (SessionID: XXX)". Any idea on what is causing it?
@lmb2This seems to be a different error, specifically saying the credentials you are using are incorrect. For me I was unable to update the credentials, even though they were correct.
It is worth noting that we tested this again last May, using the exact same setup as initially, and it worked without issue. Perhaps there was a delayed release to our tenant, but it is now functioning as described.
Thanks for your reply @V-lianl-msft, but as mentioned in the topic start, we've already verified the tenant id's for both the storage accounts' Azure subscription and the o365 subscription are the same. This should mean that they're connected right? Is there any way to verify this other than comparing the tenant id's of both subscriptions?
Anyone else perhaps with the same issue or an idea on how to fix this?
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.