Forum Discussion
Invalid Credentials - Snowflake Connection
We have a dashboard connected to Snowflake. It is in Direct Query mode and I have setup the connection as Single Sing-On. I have a buch of users for that dashboard all have been setup the exact same way but only 2 of them (2 of 15) are getting the error:
We have verified everything from Snowflake and it's all the same for all the users so why only 2 of them have issues? Is there any place I can check what credentials are being used? Snowflake is not getting any request.
Hi apacheco05 , you can try these steps to solve the query :
1. Reset Power BI + OAuth cacheLog out of Power BI Service
Clear cookies for:
powerbi.com
login.microsoftonline.com
Reopen browser and log in again
2. Re-authenticate dataset credentials in Power BI
Power BI Service → Workspace
Open Dataset → Settings
Go to Data source credentials
Click Edit credentials
Confirm:
Authentication = Single Sign-On (SSO)
Status = Signed in
Ask affected users to refresh the report once
3. Verify Azure AD UPN matches Snowflake LOGIN_NAME
Check in Azure AD:
User Principal Name (UPN)
Check in Snowflake:
SHOW USERS LIKE '%username%';Ensure:
LOGIN_NAME = Azure AD UPN
No extra spaces
Same domain
Same casing (recommended)
4. Confirm Snowflake default role exists
DirectQuery requires a valid default role.
Run:
DESC USER <username>;Verify:
DEFAULT_ROLE is set
Role still exists
Role has:
USAGE on warehouse
USAGE on database
USAGE on schema
If unsure, explicitly set it:
ALTER USER <username> SET DEFAULT_ROLE = <role_name>;5. Check Azure AD sign-in logs (critical diagnostic)
This tells you exactly why the login failed.
Steps:
Azure Portal → Azure AD
Go to Sign-in logs
Filter:
Application: Microsoft Power BI
User: affected user
Status: Failure
6. Verify Conditional Access / MFA policies
If only some users fail, they often fall under different policies.
Check:
Device compliance
Location restrictions
MFA enforcement
Temporary test:
Exclude one affected user from CA policy
Retry login
⭐Hope this solution helps you make the most of Power BI! If it did, click 'Mark as Solution' to help others find the right answers.
💡Found it helpful? Show some love with kudos 👍 as your support keeps our community thriving!
🚀Let’s keep building smarter, data-driven solutions together!🚀
2 Replies
Hi apacheco05 , you can try these steps to solve the query :
1. Reset Power BI + OAuth cacheLog out of Power BI Service
Clear cookies for:
powerbi.com
login.microsoftonline.com
Reopen browser and log in again
2. Re-authenticate dataset credentials in Power BI
Power BI Service → Workspace
Open Dataset → Settings
Go to Data source credentials
Click Edit credentials
Confirm:
Authentication = Single Sign-On (SSO)
Status = Signed in
Ask affected users to refresh the report once
3. Verify Azure AD UPN matches Snowflake LOGIN_NAME
Check in Azure AD:
User Principal Name (UPN)
Check in Snowflake:
SHOW USERS LIKE '%username%';Ensure:
LOGIN_NAME = Azure AD UPN
No extra spaces
Same domain
Same casing (recommended)
4. Confirm Snowflake default role exists
DirectQuery requires a valid default role.
Run:
DESC USER <username>;Verify:
DEFAULT_ROLE is set
Role still exists
Role has:
USAGE on warehouse
USAGE on database
USAGE on schema
If unsure, explicitly set it:
ALTER USER <username> SET DEFAULT_ROLE = <role_name>;5. Check Azure AD sign-in logs (critical diagnostic)
This tells you exactly why the login failed.
Steps:
Azure Portal → Azure AD
Go to Sign-in logs
Filter:
Application: Microsoft Power BI
User: affected user
Status: Failure
6. Verify Conditional Access / MFA policies
If only some users fail, they often fall under different policies.
Check:
Device compliance
Location restrictions
MFA enforcement
Temporary test:
Exclude one affected user from CA policy
Retry login
⭐Hope this solution helps you make the most of Power BI! If it did, click 'Mark as Solution' to help others find the right answers.
💡Found it helpful? Show some love with kudos 👍 as your support keeps our community thriving!
🚀Let’s keep building smarter, data-driven solutions together!🚀I deleted the connection and created it again and that worked!
Thanks!
