Databricks and SAP Expand Enterprise Data Access for AI

Databricks and SAP are expanding their partnership to give customers simpler, more performant access to SAP application data across cloud and on-premises, according to a Databricks announcement. The centerpiece is SAP Application Data Foundation, described as making data from SAP applications available in SAP Business Data Cloud, including SAP Databricks. Existing SAP Databricks and SAP BDC Connect are available now; several expanded capabilities remain planned. Databricks report.

What SAP Application Data Foundation Is Designed to Do

According to the Databricks announcement, SAP Application Data Foundation provides a cloud-native way to access data from SAP applications for consumption in the SAP Business Data Cloud engine of choice, including SAP Databricks. The vendor's stated rationale is that accessing SAP application data has historically required building and maintaining custom extraction pipelines that copy data, lose business context and fragment governance.

Related coverage: Related research.

Available Today Versus What Is Planned

The source is explicit that SAP Databricks and SAP Business Data Cloud Connect for Databricks are available today. It also states that the expanded partnership plans to bring the full range of Databricks data and enterprise AI capabilities to SAP Databricks, embedded within SAP BDC. That distinction matters for buyers reading the announcement.

The planned capabilities include Genie, Lakeflow, Unity Gateway and Lakebase. The announcement also describes a planned bi-directional integration between Genie and Joule intended to bring answers and actions into SAP experiences. Databricks frames this integration as planned, not launched, so it should be treated as roadmap rather than delivered function.

Related coverage: Sector coverage.

Planned Genie, Lakeflow, Unity Gateway and Lakebase Functions

Databricks describes Genie as an AI coworker giving teams access to governed data and AI with enterprise context built in. Lakeflow is presented as a unified data engineering solution to ingest, transform and orchestrate data, so teams can build pipelines combining SAP data with IoT, CRM and third-party sources. Unity Gateway is described as multi-AI governance and cost control across agents, tools, models and MCPs, intended to help teams scale AI on SAP data with guardrails and spend controls.

Lakebase is described as a serverless, mission-critical Postgres database built for AI apps and agents, aimed at operational data apps on SAP and enterprise data. These are qualitative descriptions of planned functions. The announcement does not establish that all of them are generally available, and buyers should verify each capability's status directly with the vendors.

Related coverage: Further reporting.

Zero-Copy Access, Business Semantics and Vendor Claims

The source attributes to SAP data products shared with SAP BDC Connect a zero-copy, bi-directional OpenSharing approach. That concerns access to SAP data products rather than proof that all data everywhere are never moved. Databricks says data engineers can build models on a semantically rich foundation so analytics and AI reflect how the business actually runs. This business-semantics rationale is the vendor's framing.

The announcement also says SAP Application Data Foundation helps lower total cost of ownership and reduce time to value, and that joint go-to-market teams can help customers get value faster. These are vendor claims, not independently measured results. The announcement cites no independently verified efficiency, cost or financial figures for the new foundation, and none should be inferred.

Related coverage: More developments.

What This Means for Practitioners

OUR recommendation: buyers should separate functions available today, namely SAP Databricks and SAP BDC Connect for Databricks, from planned items such as the Genie and Joule integration, Lakeflow, Unity Gateway and Lakebase. Confirm each capability's availability and integration scope directly with SAP and Databricks before committing architecture or budget. Verify how business semantics and governance boundaries are enforced across SAP and non-SAP data. Test your own use case rather than assuming broad availability or a guaranteed financial return.