Forum Discussion
Fail to set up connection to Azure Databricks
Hi all,
Recently I am setting up on-premises data gateway to connect to an Azure Databricks. We created a service principal for authentication. When I try to create a connection with Databricks SQL warehouse in PowerBI service, I got below error message
Unable to update connection credentials.
Unable to connect to the data source. Either the data source is inaccessible, a connection timeout occurred, or the data source credentials are invalid. Please verify the data source configuration and contact a data source administrator to troubleshoot this issue.
ODBC: ERROR [HY000] [Microsoft][ThriftExtension] (14) Unexpected response from server during a HTTP connection: SSL_connect: certificate verify failed.We have created the service principal in databricks and granted the use permission on the SQL warehouse. Additionally, the gateway machine has been whitelisted to firewall.
Please advise the approach to troubleshoot this issue. Thanks in advance.
Hi Carrot123
This error usually isn’t about the service principal or warehouse permissions, but about SSL validation from the gateway machine to Databricks.
A few things to check:
- Test from the gateway server
- On the gateway machine, open a browser and try to access your Databricks workspace URL over HTTPS.
- If that doesn’t work or shows certificate warnings, your gateway can’t establish a clean SSL connection.
- Check proxy / SSL inspection
- In many cases, a corporate proxy or SSL‑inspection firewall is “breaking” the certificate chain and the Databricks ODBC driver doesn’t trust it.
- Ask your network team to either: Bypass SSL inspection for *.azuredatabricks.net, or Make sure the proxy’s root certificate is trusted on the gateway server.
- Certificate revocation checks
- Another common cause is that the driver can’t reach the certificate revocation (CRL/OCSP) endpoints.
- Have your network team allow outbound access from the gateway to the CRL/OCSP URLs for the Databricks certificate (often DigiCert).
- As a temporary workaround (if your security team agrees), you can disable revocation checks in the Databricks ODBC driver on the gateway by setting CheckCertRevocation=0 in the driver’s config file.
After making these changes, restart the gateway service and re‑enter the Databricks connection in Power BI Service. In most cases, the error disappears once SSL / certificate checks are correctly allowed.
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
- Test from the gateway server
2 Replies
Hi Carrot123
This error usually isn’t about the service principal or warehouse permissions, but about SSL validation from the gateway machine to Databricks.
A few things to check:
- Test from the gateway server
- On the gateway machine, open a browser and try to access your Databricks workspace URL over HTTPS.
- If that doesn’t work or shows certificate warnings, your gateway can’t establish a clean SSL connection.
- Check proxy / SSL inspection
- In many cases, a corporate proxy or SSL‑inspection firewall is “breaking” the certificate chain and the Databricks ODBC driver doesn’t trust it.
- Ask your network team to either: Bypass SSL inspection for *.azuredatabricks.net, or Make sure the proxy’s root certificate is trusted on the gateway server.
- Certificate revocation checks
- Another common cause is that the driver can’t reach the certificate revocation (CRL/OCSP) endpoints.
- Have your network team allow outbound access from the gateway to the CRL/OCSP URLs for the Databricks certificate (often DigiCert).
- As a temporary workaround (if your security team agrees), you can disable revocation checks in the Databricks ODBC driver on the gateway by setting CheckCertRevocation=0 in the driver’s config file.
After making these changes, restart the gateway service and re‑enter the Databricks connection in Power BI Service. In most cases, the error disappears once SSL / certificate checks are correctly allowed.
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
Hi grazitti_sapna,
Thanks for your reply. Found that the root cause is the data gateway instance failed to access cacerts.digicert.com port 80 which is blocked by firewall.
The connection can now successfully created after whitelisting the traffic on firewall.
- Test from the gateway server
