Power BI Desktop Snowflake Refresh Fails: “Cannot Convert Null to Text” While Service Still Works

[nokt3]

Hi all, I’m seeing a sudden Power BI Desktop refresh failure with Snowflake-backed Power Query tables. Has anyone else seen this with recent Power BI Desktop / Snowflake connector builds? Is there a known regression or recommended workaround?

Power BI Desktop version: 2.155.756.0
Install type: Microsoft Store app
Connector: native Snowflake connector
Pattern: Snowflake queries fail in Desktop, but the same SQL runs successfully in Snowflake and the dataset/report still refreshes in Power BI Service.

Representative M pattern:
let
Source =
Value.NativeQuery(
Snowflake.Databases(
"<snowflake_account>",
"<warehouse>",
[Implementation="2.0"]
){[Name="<database>"]}[Data],
"<native SQL query against a Snowflake view>",
null,
[EnableFolding=true]
)
in
Source

Desktop refresh error: cannot convert the value null to type Text.

Things already tried:

• Restarted machine
• Uninstalled/reinstalled Power BI Desktop
• Cleared/re-authenticated data source credentials
• Removed [Implementation="2.0"]
• Removed [EnableFolding=true]
• Replaced select * with explicit column casts
• Tested multiple Snowflake queries/tables

[HugoR]

Hi, Same here, having the same problem this morning. Can't process the connection with Snowflake with the Key Pair authentication.

[Rafael_Rommano]

We’re having the same problem here. Queries on the service from Snowflake are still working. The solution for now has been to create a dataflow.

[rtbreneman]

Same issue here. Problem exists in 2.155.332.0 and 2.155.756.0, both June 2026 releases. A coworker running 2.154.1260.0 64-bit (May 2026) does not have problem. As others have mentioned, we're using Key Pair authentication and online service refreshes continue to run so the issue seems to be limited to the June 2026 release of the desktop app. Issue was first noticed by our team on 6/9/26, but our org auto pushes updates to Power BI Desktop, so that could have impacted the timing and when we noticed the problem.

[rtbreneman]

I opened a MSFT support ticket regarding this issue. They confirmed it's a June 2026 release issue. It's being escalated to the product team but a fix may need to wait until the next release. As a workaround we were able to uninstall and downgrade to a previous version (in this case April since they don't have a link to May). Here is the link to download previous versions: https://learn.microsoft.com/en-us/power-bi/fundamentals/desktop-latest-update-archive?tabs=powerbi-d...

[nokt3]

thank you!! uninstalled the Microsoft store version and rolled back to the april release worked, much appreciated!

[davidcoe_msft]

This is because when the user does not provide a passphrase for the certificate (the field is optional and only needed for encrypted PKCS#8 keys), the value is null, and the ADBC Snowflake driver fails rather than treating the key as unencrypted. There fix is fix for the July release. The workaround is to provide optional passphrase to an empty string before passing it to the driver.

[Filipgab]

I'm experiencing a similar issue after the latest Power BI Desktop update, but with the SAP connector. Report connects to SAP Business Warehouse Application Server using DirectQuery. SAP .NET Connector 3.1 is installed on the machine. After updating Power BI Desktop to the latest version (2.155.756.0), the report no longer loads and fails with the following error: "Something went wrong. Sequence contains more than one element" After rolling back Power BI Desktop to the previous version, the same report works again without any changes to the PBIX file, SAP connection, credentials, or SAP .NET Connector installation. Is this a known issue and whether there is any recommended workaround also? @davidcoe_msft 

[CathyP]

I have exact same problem. The suggested workaround to rollback sorted for me for the moment. I am using key pair authentication

[wgt0213]

Hi everyone. My team has been in touch with Microsoft. They are actively looking into the issue and anticipate a fix for the July release.

For now, those using Snowflake + KPA and are hitting this error upon local refresh: Try editing your KPA credentials and for the passphrase (which is technically optional), put any string - I put 'test'. It should succeed in connecting. It is not a long-term sustainable solution but it is a recognized workaround.

Per Microsoft (also posted in this forum): "This is because when the user does not provide a passphrase for the certificate (the field is optional and only needed for encrypted PKCS#8 keys), the value is null, and the ADBC Snowflake driver fails rather than treating the key as unencrypted. There fix is fix for the July release. The workaround is to provide optional passphrase to an empty string before passing it to the driver."

[music43]

This is exactly what I am experiencing. More live testing from Microsoft.