Databricks Community

Victor2 · a week ago

When i try to create the connection, I get the error message "Connection test failed. Please review your configuration and try again."

Here is the response in the network trace:

My connection credentials are correct. So, i'm not sure what i am doing wrong. Could anyone help on how to unblock myself?

mark_ott · Wednesday

The error message "Connection test failed. Please review your configuration and try again." when connecting Databricks to Power Platform can occur due to several common issues, even if your credentials are correct.

Key Troubleshooting Steps

Double-check that your Databricks access token is still valid and has not expired. Expired or revoked tokens are a frequent cause of authentication failures.
Verify the server hostname and HTTP path match the exact values in your Databricks workspace. Small typos or outdated URLs can trigger connection errors.
Ensure your network firewall or proxy settings are not blocking communication with Databricks. SSL inspection or missing certificates can also interfere; updating your local root certificates or explicitly disabling certificate revocation checks in the ODBC driver configuration sometimes fixes the issue.
Check for any Data Loss Prevention (DLP) policies or admin-level restrictions in your Power Platform or organization that might block the connector or restrict the permissions needed to connect.
Confirm that you are running the latest supported version of the Databricks ODBC driver for your integration tool, as compatibility mismatches are another common pitfall.

What to Try Next

Reauthorize your connection in Power Platform, updating or refreshing credentials and tokens as prompted.
Review any organization-enforced security policies or blocked device states that could be affecting your access.
If behind a network proxy or firewall, consult with your IT team to ensure Databricks service traffic is not being filtered or blocked.
For persistent failures, check driver logs or Databricks workspace event logs for additional error details that could pinpoint the misconfiguration.