Source Data Objects are disabled When using Lakeflow Connect for Hubspot

Question

Completed all these below steps as outlined in the documentation and still we are not able to choose the core CRM objects using the Lakeflow Connect for Hubspot (preview mode)

• The HubSpot CRM-object preview is enabled.
• A fresh HubSpot OAuth app was created with the required CRM read scopes.
• A new Unity Catalog connection was created and the OAuth flow completed successfully.
• The HubSpot account has administrator access to the relevant CRM modules. CRM objects such as Contacts, Companies, Orders, Deals, Line Items, and Products are still unavailable for selection, while Marketing Hub objects are selectable.

Any advise here is much appreciated.

Answer 1

What you are seeing appears to be an availability limitation of the current Lakeflow Connect HubSpot connector rather than an OAuth or Unity Catalog configuration problem.

The important detail is that the current Azure Databricks documentation states that the managed HubSpot connector supports ingestion from HubSpot Marketing Hub. The connector reference currently lists Marketing Hub objects such as marketing emails, forms, campaigns, marketing events, and related tables.

That lines up exactly with your observation:

• Marketing Hub objects are selectable
• CRM objects such as Contacts, Companies, Deals, Orders, Line Items, and Products are disabled
• OAuth completes successfully
• A newly created Unity Catalog connection behaves the same way

So I would not continue adding CRM scopes or recreating the OAuth application. The current connector is not exposing those CRM Hub objects for managed ingestion.

Microsoft's documented limitation is essentially that other HubSpot hubs are not currently supported by this managed connector. The documentation recommends contacting your Azure Databricks account team if ingestion from other hubs is required.

For the current implementation, I would either restrict the Lakeflow pipeline to the supported Marketing Hub tables or use another ingestion path for the CRM objects until Databricks expands the managed connector.

Microsoft Learn resource:

https://learn.microsoft.com/training/?wt.mc_id=studentamb_521824

Answer 2

Hello @vinodhgudivada

Based on the current Azure Databricks documentation, this behavior is expected with the managed HubSpot Lakeflow Connect connector.

The key limitation is that the connector currently supports ingestion only from HubSpot Marketing Hub. Microsoft explicitly states: “The HubSpot connector only supports ingestion from HubSpot Marketing Hub.”

Therefore, CRM objects such as Contacts, Companies, Deals, Line Items, Orders, and Products being unavailable while Marketing Hub objects remain selectable is consistent with the documented connector limitation.

This also means that recreating the OAuth app or adding CRM read scopes won't make those CRM objects available through the currently supported managed connector. The connector's documented source-table reference currently lists Marketing Hub-related tables such as email_events, marketing_emails, forms, marketing_campaigns, and marketing_events.

I recommend contacting your Azure Databricks account team if you need ingestion from HubSpot hubs other than Marketing Hub.

One point of confusion is that the pipeline documentation includes examples using contacts and companies, even though the current limitations/reference documentation restricts the connector to Marketing Hub. Given that discrepancy, rely on the current connector Limitations and Reference pages for supported objects.

References:

HubSpot connector limitations

HubSpot connector reference

Ingest data from HubSpot

---

Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.