I am able to connect to Azure Databricks from Power BI Desktop and see preview but not able to load data into power bi getting below error need support

Bochkar, Sriraj (Contractor) 0 Reputation points
2026-09-08T09:33:18.15+00:00

User's image

Hi Team, Need help asap for the issue which i am facing, thanks in advance

Azure Databricks
Azure Databricks

An Apache Spark-based analytics platform optimized for Azure.

0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-09-08T09:33:49.03+00:00

    The error shown is consistent with a network name-resolution problem during result-file download from Azure Databricks, not the initial connection itself. That explains why preview works but the full load fails.

    Use this checklist:

    1. Verify outbound network access from the machine running Power BI Desktop.
      • The error includes: Couldn't resolve host name.
      • This indicates DNS resolution or outbound access is failing when Power BI tries to download result files from cloud storage.
    2. If the connection is going through a proxy, confirm the proxy configuration is supported.
      • The Azure Databricks connector supports web proxy.
      • Automatic proxy settings defined in .pac files are not supported.
      • If the environment relies on .pac, switch to a supported Windows system-wide proxy configuration.
    3. If a firewall or network security policy is in place, allow the required certificate authority endpoints.
      • Azure Databricks SSL certificates use DigiCert.
      • Add *.digicert.com to the firewall allow list so certificate revocation validation can succeed.
    4. If the environment uses private networking and SSL verification errors are involved, adjust certificate revocation handling.
      • Create this file if it does not exist: C:\Program Files\Microsoft Power BI Desktop\bin\ODBC Drivers\Simba Spark ODBC Driver\microsoft.sparkodbc.ini
      • Add: 
             [Driver]
     CheckCertRevocation=0
      • This is a workaround for CRL-check failures caused by restricted outbound network access.
      • Warning: disabling certificate revocation checking reduces certificate-validation security and should be used only when network restrictions are the cause.
    5. Check the Power BI Desktop version.
      • Built-in automatic detection of Windows system-wide HTTP proxy configuration requires Power BI Desktop version 2.104.941.0 or later.
      • If native SQL queries are being used, that requires version 2.112.603.0 or later.
      • Databricks service principal M2M OAuth requires version 2.143.878.0 or later.
    6. Reconnect and test with a small load.
      • Open Get Data > Azure Databricks.
      • Reauthenticate if needed.
      • In Navigator, select a small table first and try Load.
      • If preview succeeds but load still fails, that further points to network restrictions during result retrieval rather than authentication.
    7. If using Partner Connect, regenerate the connection and test again.
      • In Azure Databricks: Marketplace > Partner Connect integrations > Power BI.
      • Choose the compute resource, download the connection file again, open it in Power BI Desktop, then authenticate and test the load.

    The most relevant documented causes for this pattern are:

    • unsupported proxy configuration such as .pac
    • blocked certificate revocation endpoints
    • private-network SSL verification issues requiring CheckCertRevocation=0

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Senthil kumar 2,410 Reputation points
    2026-09-08T11:47:55.9666667+00:00

    Hi @Bochkar, Sriraj (Contractor)

    Root cause : connectivity or credentials issues may be.

    Solution :

    • Make sure your PC or gateway can reach the data source host.
    • If the dataset uses Azure Data Lake, Synapse, or SQL Server, re‑authenticate the connection:
    1. In Power BI Desktop → Data Source Settings → Edit Permissions.
    2. Clear and re‑enter credentials.
    3. Refresh the dataset.
    • Sometimes the connection string points to an outdated region or alias. Confirm the server name matches your current Azure region (e.g., eastus.azuredatalake.net).
    • Power BI and Analysis Services cache result files locally. Clear them: %LocalAppData%\Microsoft\Power BI Desktop\AnalysisServicesWorkspaces Then reopen Power BI and refresh.

    Thanks.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.