Snowflake data source refresh errors following July 2025 release

[reubwork]

In case anyone else finds this. I started getting weird errors refreshing a report in the past few days.

Data source error: The credentials provided for the Snowflake source are invalid. (Source at <service>.). The exception was raised by the IDbCommand interface. Table: <table name>

Testing locally using the same credentials is fine. 

Then I found that the Snowflake connector 2.0 has very recently gone to GA. 

https://powerbi.microsoft.com/en-us/blog/power-bi-july-2025-feature-summary/#post-30545-_Toc20338870...

[v-lgarikapat]

Hi @reubwork ,

Thanks for sharing this just trying to better understand your setup so I can offer the right troubleshooting steps. You mentioned the Snowflake refresh is failing in Power BI Service with a credentials error, but it's working fine locally. Just to clarify a few things: are you connecting to Snowflake using OAuth, username/password, or some other method? Are you using a gateway for the dataset, and if so, is it an on-premises or personal gateway? Also, when you say it works locally, do you mean in Power BI Desktop, and does the refresh succeed there without any issues? Did you recently update or republish the report using the July 2025 version of Power BI Desktop? And finally, have you tried re-entering or updating the data source credentials in Power BI Service after the issue started? The reason I ask is that the Snowflake Connector 2.0 just went GA with the July release, and it might have introduced some changes that impact existing configurations, especially around authentication. A bit more info would really help us narrow this down.

We truly appreciate your continued engagement and thank you for being an active and valued member of the community.

We look forward to hearing from you.

Best regards,
Lakshmi

[amol_mahajan]

I'm facing this exact same issue. We're using snowflake cloud. It works fine on PBI Desktop and fails when published that too at random times. And corrects itself after sometime. We don't use SSO logins we use global usernames with assigned roles / service accounts. Can you share what could be causing this?

[reubwork]

hi there,

I've had a lot of issues with the server side refresh of snowflake queries (not locally)... up until the July release which is a big improvement. 

If you're using SQL Logins and passwords... you need to get off that this year as Snowflake are disabling logins without MFA. 

So we've switched to using Programmable Access Tokens... https://docs.snowflake.com/en/user-guide/programmatic-access-tokens

The intermittent thing is strange and suggests some kind of data handling issue to me... I've not seen any network transport issues. (Is your power bi capacity in the same region as Snowflake?) 

You can force it to use the old connector with the Implementation option. default is the new version which is 2.0

// declare connection
snowflake_connection = Snowflake.Databases(
"sonovate.west-europe.azure.snowflakecomputing.com",
warehouse_name,
[Role = role_name, Implementation="1.0"]
),

[amol_mahajan]

Using [Implementation="2.0"] solved my issue. Thanks!
I had other data sources along with snowflake and only those reports were failing. After forcing this in power query the refresh are working fine.
Thanks!

[reubwork · Accepted solution]

This turned out to be user error. 

We're switching from using Snowflake sql login and password, to using Snowflake service users with Programmable Access Tokens. 

When creating a PAT, you're required to specify an explicit single Snowflake role. Then, if you try and use any other role in the power query ingest it'll fail. 

So, user error. 

[v-lgarikapat]

Hi @reubwork ,

Thank you for the updates and for sharing the resolution. It's greatly appreciated and will be helpful to others in the community as well.

Thank you for being an active and valued member of the community. 

Best Regards,

Lakshmi

[v-lgarikapat]

Hi @reubwork ,

I wanted to follow up and confirm whether you’ve had the opportunity to review the information we provided. If you have any questions or need further clarification, please don’t hesitate to reach out.

We truly appreciate your continued engagement and thank you for being an active and valued member of the community.

We look forward to hearing from you.

Best regards,
Lakshmi

[v-lgarikapat]

Hi @reubwork ,

I just wanted to check if your issue has been resolved. If you still have any questions or need help, feel free to reach out I’m happy to assist.

Thank you for being an active part of the community. Looking forward to hearing from you!

Best regards,
Lakshmi

[v-lgarikapat]

Hi @reubwork ,

I just wanted to check if your issue has been resolved. If you still have any questions or need help, feel free to reach out I’m happy to assist.

Thank you for being an active part of the community. Looking forward to hearing from you!

Best regards,
Lakshmi

[lbendlin]

ok, what is your question?