Forum Discussion

biapps's avatar
biapps
Frequent Visitor
5 months ago
Solved

Power BI Pro / Azure Databricks Standard Tier (LEGACY HIVE METASTORE) CONNECTIVITY

I AM GOING INSANE. For over 6+ years everything has worked perfectly.

I have an Azure Databricks setup that I connect to from Power BI Desktop using the Databricks host URL and HTTP path. I authenticate with either Azure Databricks token or OAuth/AAD, and Desktop connects without problems. I build the report, publish it to Power BI Service, and that part also works.

The problem starts in Power BI Online / Power BI Service.

I can no longer get the Power BI online platform to successfully connect to the Azure Databricks source in a reliable way, and I am trying to understand whether this is:

1. an authentication problem,
2. a connector issue in Power BI Service,
3. or some incompatibility between my legacy Databricks setup and the newer Power BI online connection flow.

Important details:

* I am using an organizational account.
* I do not have Premium capacity.
* My Databricks data is in a legacy `hive_metastore`.
* My Databricks cluster access mode is single-user, and that single user is me / the same account being used.
* Everything works in Power BI Desktop.
* Publishing from Desktop also works.
* The failure is specifically when trying to connect/manage credentials/create connections in Power BI Service / Power BI Online.

My Databricks connection info comes directly from the cluster (Host / HTTP Path)

In Power BI Service, under Manage connections and gateways, I have/had a working Azure Databricks connection using that host and HTTP path.

Errors I have received trying different things:

1. When trying AAD authentication:
“Unable to update connection credentials. We could not access the data source. Please make sure you have permission to access the data source and that your credentials are correct.”

2. When enabling “Single sign-on (use SSO via AAD for DirectQuery queries)”:
`AADSTS70008: The provided authorization code or refresh token has expired due to inactivity. Send a new interactive authorization request for this user and resource.`

3. When trying to create a brand-new Azure Databricks connection in Power BI Online:
`DataSource.Error: ADBC: Required parameter 'adbc.spark.host' or 'uri' is missing or invalid. Please provide a valid hostname or URI for the data source.`

This is the part that is confusing me the most:

* Desktop continues to work.
* The same Databricks host and HTTP path work there.
* But Power BI Online either fails authentication or throws this newer ADBC-related error when creating a new connection.

Has anyone successfully connected Power BI Service directly to an Azure Databricks cluster like this recently, without Premium capacity and without changing to a SQL warehouse?

Any guidance from someone who has dealt with Azure Databricks + Power BI Service recently would be hugely appreciated, because right now I am trying to determine whether the real problem is:

* stale OAuth credentials,
* Power BI Online’s newer Databricks connector behavior,
* a new service-side limitation,
* or a new network/gateway requirement.

  • Downgraded to the Power BI November 2025 version and after opening the reports in this version and uploading them again everything is working correctly. Seem like newer versions are affecting the connection with Azure Databrickcs.

  • Hello biapps
    Power BI Desktop continues to connect to legacy Azure Databricks clusters because it uses the local driver and direct credentials. Power BI Service, however, does not reliably support legacy Hive metastore clusters. Service requires a Databricks SQL warehouse with Unity Catalog and proper credentials (PAT, OAuth, or service principal). Using Pro alone may not suffice; Premium or PPU is often needed.

    Errors like ADBC: Required parameter 'adbc.spark.host' or expired OAuth tokens happen because the Service connector enforces these newer requirements, which Desktop bypasses. Downgrading Power BI Desktop may temporarily restore functionality, but long-term reliability requires migrating to SQL warehouses / Unity Catalog for Service connectivity.

    Official guidance: Connect Power BI Service to Azure Databricks

4 Replies

  • biapps's avatar
    biapps
    Frequent Visitor

    Downgraded to the Power BI November 2025 version and after opening the reports in this version and uploading them again everything is working correctly. Seem like newer versions are affecting the connection with Azure Databrickcs.

  • Hello biapps
    Power BI Desktop continues to connect to legacy Azure Databricks clusters because it uses the local driver and direct credentials. Power BI Service, however, does not reliably support legacy Hive metastore clusters. Service requires a Databricks SQL warehouse with Unity Catalog and proper credentials (PAT, OAuth, or service principal). Using Pro alone may not suffice; Premium or PPU is often needed.

    Errors like ADBC: Required parameter 'adbc.spark.host' or expired OAuth tokens happen because the Service connector enforces these newer requirements, which Desktop bypasses. Downgrading Power BI Desktop may temporarily restore functionality, but long-term reliability requires migrating to SQL warehouses / Unity Catalog for Service connectivity.

    Official guidance: Connect Power BI Service to Azure Databricks

  • v-priyankata's avatar
    v-priyankata
    Community Support

    Hi biapps 

    Thank you for reaching out to the Microsoft Fabric Forum Community.

    Olufemi7 Thanks for the inputs.

    I hope the information provided by user was helpful. If you still have questions, please don't hesitate to reach out to the community.
    Thanks.

     

  • v-sgandrathi's avatar
    v-sgandrathi
    Community Support

    Hi biapps,

     

    Following up to check whether you got a chance to review the suggestions given. If the issue still persists please let us know. Glad to help. 

     

    Thank you.