Error while connecting Snowflake from PBI Service

[srlabhe]

Hi Team,

I have a report which I can refresh successfully from PBI Desktop, but when I publish same report to PBI service in a workspace and try refreshing from there , it shows me below error:

Appreciate help 

[powerbidev123 · Accepted solution]

Hi @srlabhe 

You can troubleshoot through these steps:

1. Check the Snowflake Host Name

Verify the server name/URL used in the Snowflake connector.

It should follow this format:

php-template

Copy

Edit

<account>.snowflakecomputing.com

Avoid using localhost, IP addresses, or incomplete hostnames.

2. Gateway Configuration (If Required)

If you're using an on-premises data gateway, ensure:

The gateway is installed and running.

The Snowflake connector is installed on the gateway machine.

The data source is added to the gateway under Manage Gateways in Power BI Service with matching credentials and server name.

• Note: For Snowflake, gateway is not required if using a cloud connection via OAuth2, unless you access Snowflake via a private endpoint/VPN.

3. Use VNet/Data Gateway for Private Endpoints

If your Snowflake account is accessible only via private IPs or a VNet, you must use a VNet data gateway or private link-enabled integration.

4. Update or Re-enter Credentials

Go to:

Workspace → Dataset settings → Data source credentials

Re-authenticate using OAuth2, ensuring the correct user and organization level.

If this fails, DNS resolution is the issue.

[v-ssriganesh]

Hello @srlabhe,

We hope you're doing well. Could you please confirm whether your issue has been resolved or if you're still facing challenges? Your update will be valuable to the community and may assist others with similar concerns.

Thank you.

[v-ssriganesh]

Hello @srlabhe,

Hope everything’s going great on your end! Just checking in has the issue been resolved, or are you still running into problems? Sharing an update can really help others facing the same thing.

Thank you.

[v-ssriganesh]

Hello @srlabhe,

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @BhavinVyas3003 & @powerbidev123  for sharing valuable insights.

Could you please confirm if your query has been resolved by the provided solution? If so, please mark it as the solution. This will help other community members solve similar problems faster.

Thank you.

[BhavinVyas3003 · Accepted solution]

Option 1: Use Snowflake Public Endpoint (if allowed)

• Edit your connection string in Power BI Desktop to use the public Snowflake host, not the privatelink URL.
• Republish the dataset.
• This works without any special setup.

Option 2: Set Up Azure Virtual Network Data Gateway

• Deploy an Azure VNet Data Gateway in the same VNet as your Snowflake PrivateLink.
• Configure the data source in Power BI Service to use that gateway.
• This allows Power BI Service to resolve the PrivateLink URL securely.

[powerbidev123 · Accepted solution]

Hi @srlabhe 

You can troubleshoot through these steps:

1. Check the Snowflake Host Name

Verify the server name/URL used in the Snowflake connector.

It should follow this format:

php-template

Copy

Edit

<account>.snowflakecomputing.com

Avoid using localhost, IP addresses, or incomplete hostnames.

2. Gateway Configuration (If Required)

If you're using an on-premises data gateway, ensure:

The gateway is installed and running.

The Snowflake connector is installed on the gateway machine.

The data source is added to the gateway under Manage Gateways in Power BI Service with matching credentials and server name.

• Note: For Snowflake, gateway is not required if using a cloud connection via OAuth2, unless you access Snowflake via a private endpoint/VPN.

3. Use VNet/Data Gateway for Private Endpoints

If your Snowflake account is accessible only via private IPs or a VNet, you must use a VNet data gateway or private link-enabled integration.

4. Update or Re-enter Credentials

Go to:

Workspace → Dataset settings → Data source credentials

Re-authenticate using OAuth2, ensuring the correct user and organization level.

If this fails, DNS resolution is the issue.