Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hi,
Hope everyone is doing well.
There are several topics that deal with this error, but none that answers my problem.
Context :
- a report and a semantic model that leverages the Direct Query mode for Snowflake
- a Pro workspace
- 3 Workspace viewers and contributors
- 3 people, that are not members of the Workspace, added to the app audience (which shows the report from the 1st bullet point)
My problem is :
- I have no issue in Power BI Desktop or Service
- The 3 members of the Workspace have no issue in Power BI Service
- The 3 people from the app audience can see the app BUT they SOMETIMES see an "Error fetching the data for this visual. Couldn't load the data for this visual" for some visuals and not all of them. They also see a red "Invalid credentials" banner when viewing the app.
It SEEMS like the error appears solely for the visuals that hit the Direct Query table, which holds the finest grain of data, while the visuals that hit the Power BI aggregated tables SEEM to work correctly. however this may be an invalid assumption since I'm not even sure the aggregated tables are being hit in Service because SSO is activated for Snowflake + sometimes all visuals show this error.
Help 🙂
Solved! Go to Solution.
Hi @Danyboyyy ,
Thank you for reaching out to Microsoft Fabric Community.
These steps might resolve the “Invalid credentials” and DirectQuery visual errors for non-workspace users in apps.
Grant Build permission on the dataset to the app audience users, navigate to Workspace which contains Dataset, click on Manage Permissions, Add users, Grant Build Access.
Enable SSO correctly:
Go to Workspace , click on dataset settings expand data source credentials.
Ensure “Use SSO via Azure AD” is enabled and “Use user's credentials” is checked.
Verify Snowflake access, Ensure app users have the right Snowflake roles and are not blocked by network policies.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thank you!!
Hi @Danyboyyy ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If the responses has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you!!
Hi @Danyboyyy ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you!!
Hey,
I did not forget but I'm afraid I have not yet. What I know for now is that "Build" was not the issue since it hasn't changed anything.
I still have to have confirm for SSO and Snowflake access. Then i'll come back here 😉
Best,
Hi @Danyboyyy ,
Thank you for reaching out to Microsoft Fabric Community.
These steps might resolve the “Invalid credentials” and DirectQuery visual errors for non-workspace users in apps.
Grant Build permission on the dataset to the app audience users, navigate to Workspace which contains Dataset, click on Manage Permissions, Add users, Grant Build Access.
Enable SSO correctly:
Go to Workspace , click on dataset settings expand data source credentials.
Ensure “Use SSO via Azure AD” is enabled and “Use user's credentials” is checked.
Verify Snowflake access, Ensure app users have the right Snowflake roles and are not blocked by network policies.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thank you!!
Hi,
Thank you for your answer ! I'll try that and will come back to update the status 🙂
Hi @Danyboyyy ,
Thank you for the response!! We will be waiting for your reply, Please let us know if you still face any issues?
Hi @v-sathmakuri ,
I'm sorry I could not come sooner, I just only had the opportunity to check access with my business users.
Turns out that the problem was actually fully related to Snowflake : the business users accounts had been disabled by the DBA. Everything works now that the users are enabled.
For reference :
- The build permission was not needed (they don't have it now and they can fully access the reports)
- The SSO was already correctly enabled
Thank you for your help and sorry again for how long it took for me to come back 🙂
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.