The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Hello Power BI Pros,
I have a power bi file which connects directly to a container inside an azure blob storage, the connection type is anonymous since the container "Public access level" is set to "Container", I personaly don't need to set the blob storage key after publish since I'm calling directly the container:
let
Source = AzureStorage.Blobs("https://xxxpowerbistorage.blob.core.windows.net/11123456-0000-000x-f123-44e1e7959c56")
in
Source
However, when I sent the .pbix file to my work colleagues (we all have pro licenses) and they publish it to the online portal in their workplaces, they cannot refresh and they face this error:
And this is how it looks in dataset settings:
I don't have any issues when I refresh the dataset online and I don't need to enter any credentials!
Thank you!
Solved! Go to Solution.
The issue was not exactly in my colleague account! the datasource credentials (blob storage key) were cached in my power bi online account since I used it before for different reports! 😑 that's why I could connect without any problem!
The issue was not exactly in my colleague account! the datasource credentials (blob storage key) were cached in my power bi online account since I used it before for different reports! 😑 that's why I could connect without any problem!
Hi @walid140891 ,
As stated in the error message, your colleague needs to configure the data source credentials correctly for the report to refresh successfully.
When you connect to a data source and create a report in Desktop, you have provided the correct credentials for that data source, so when you just share the PBIX file with colleagues, the colleague also needs to verify that they have permission to open the PBIX file.
You can:
(1) Have colleagues open the PBIX file in Desktop and enter the data source credentials, then publish the file, and finally configure refresh for the file on Service.
(2) You publish the PBIX file to the workspace, and then configure the gateway and data source credentials for the report, and distribute the usage rights of the gateway and data source credentials to colleagues, and then colleagues use the credentials to reconfigure the data source.
Please refer to the following document for more information.
Share Power BI reports and dashboards with coworkers and others - Power BI | Microsoft Learn
Configure scheduled refresh - Power BI | Microsoft Learn
Add or remove a gateway data source - Power BI | Microsoft Learn
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello @v-tangjie-msft ,
Thank you for your answer, my colleagues opened the .pbix file in power bi desktop and even deletes the credentials and set it again and they could refresh data in the power bi desktop application! but again once they publish they receive the same error.
We don't use gateways to refresh datasets!
This .pbix file is tend to be sent to our customers later when it works fine.
Hi @walid140891 ,
What is your data source?
If your data source cannot be directly accessed by Power BI (such as an on-premises data source), then refreshing must require a gateway. If your data source is a cloud data source, the refresh works fine once the credentials are configured correctly on Power BI Service instead of Desktop.
I hope this document is helpful to you. Data refresh in Power BI - Power BI | Microsoft Learn
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
54 | |
25 | |
14 | |
14 | |
12 |
User | Count |
---|---|
104 | |
37 | |
28 | |
22 | |
21 |