AI & Analytics Legends The knowledge platform for SAP Analytics
Guide

SAP BDC Connect consultant: zero-copy sharing, governance and partner dates

SAP BDC Connect consultant: zero-copy sharing, governance and partner dates — Analytics Legends section illustration for SAP analytics market intelligence (Datasphere, BDC, SAC, BW/4HANA)

As of 2026-10-09

Edited by , sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

A SAP BDC Connect consultant connects an external data platform to SAP Business Data Cloud without copying data: registering the partner endpoint, publishing and consuming data products in both directions, checking that access rules and lineage survive the crossing, and telling the client which partner integration is actually available on which date. Only the Databricks integration is generally available in the sources we hold, since 6 October 2025. In the corpus generated on 8 October 2026, no live posting names BDC Connect, while 276 of 1,698 name Business Data Cloud, so the skill is bought under BDC and Databricks titles.

What BDC Connect is, and what it is not

BDC Connect is a standard technical service that replaces what used to be a bespoke connector project per partner and per customer. A partner platform registers once as an endpoint and gains governed, bidirectional access to SAP data products. Four controls are enforced at the boundary whichever partner sits on the other side: authentication through SAP's identity service, schema conformance checked at the gateway so that drift is rejected rather than discovered in a report, lineage propagated back to SAP's semantic layer, and inheritance of the access controls defined in Datasphere.

It is not a commercial bundle. A Solution Extension is SAP reselling a partner platform under one purchase order; BDC Connect leaves the customer with separate contracts and the freedom to connect the platform it already runs. A customer can hold both at once, and a client asking whether BDC Connect can replace a Solution Extension is usually asking a support and liability question that deserves a separate answer.

Databricks: the integration that is live

BDC Connect for Databricks reached general availability on 6 October 2025. It reuses the open Delta Sharing protocol unmodified. In one direction, a governed BDC data product is exposed as a share that Unity Catalog registers with a share URL and a bearer token scoped per BDC tenant, and a notebook queries it with ordinary Spark SQL. In the other, a Databricks Delta table is registered as an external data product and consumed from SAP Analytics Cloud or a BDC application while the data stays in Databricks storage.

Three prerequisites decide the first week. The consuming workspace must run Unity Catalog; a workspace still on the classic Hive metastore cannot consume a share until it is migrated. The token expires and must be rotated on a schedule, because a share that stops refreshing looks like a live connection while serving stale data. And reads happen on demand at query time; sub-second needs call for change data capture and streaming instead. Since 29 September 2026 the SDK can also publish SAP Databricks views, not only tables, as custom data products, which makes each view and each type cast a contract to version.

Fabric, AWS and Snowflake: check the date before the proposal

The rollout is staggered, and its dates have already moved once. For Microsoft Fabric, early access was announced in November 2025; the general-availability target moved from Q2 2026 to the second half of 2026 at SAP Sapphire in May 2026, and our last review on 27 September 2026 found no confirmation that it had shipped. It relies on OneLake mirroring to give Power BI near-real-time, read-only SAP data. Native AWS services were targeted for Q3 2026, a roadmap commitment we have not seen confirmed. Snowflake remains a partner-connected architecture with its own commercial relationship and credit-based pricing, and its integration paths did not ship on the same day.

The consultant's first deliverable is therefore a dated availability check for the client's hyperscaler, with every non-GA date labelled as such in the plan and a contingency for slippage.

Governance: what the boundary inherits, and what it does not

Policy inheritance is the strongest argument for the service: a user without rights to a cost centre in Datasphere cannot see it through Databricks or Fabric either. It also replicates a badly designed access model faithfully, so an engagement often starts with an audit of the existing access controls rather than with the connection.

Two gaps recur. Restricting access in the BDC catalogue does nothing if the same users can still query the source platform directly with their own credentials; both layers are closed together. And a Databricks-originated data product does not automatically become something SAP's knowledge graph can reason over: someone has to model it as a proper Datasphere entity before a Joule agent can ground on it with the same confidence as native data. BDC Connect is a data bridge, not a model bridge; it does not route generative AI inference, and masking or content filtering remain controls of the orchestration service.

Federate or replicate: the trade-off to walk through

The claim that nothing has to move is true but incomplete. Keeping data in place avoids a second copy, replication lag and a reconciliation workload, but every query still consumes compute on the reading side, billed by the partner platform rather than in BDC capacity units, so it rarely appears in the BDC cost conversation. Query latency is also bounded by the source system. The working rule from our cards: share or federate for exploratory, lower-frequency or governance-driven access, and replicate data that is queried at high frequency or feeds a latency-sensitive dashboard. Heavy transformation still needs a pipeline somewhere, downstream of the zero-copy read.

Decision table: which route for which case

Existing Databricks workspace under its own contract — Route: BDC Connect for Databricks · Check: Unity Catalog, token rotation · Risk: unbudgeted Databricks compute.

No Databricks contract, single purchase order wanted — Route: SAP Databricks Solution Extension · Check: support model · Risk: lock-in to the packaged platform.

Power BI is the main analytics surface — Route: BDC Connect for Fabric once generally available · Check: release status on the proposal date · Risk: a delivery date built on a roadmap quarter.

AWS-anchored estate — Route: plan the endpoint, do not commit before GA · Check: whether a replication flow to the lake covers the need meanwhile · Risk: promising parity that does not exist.

Access rules needed on the partner side — Route: inherit Datasphere access controls · Check: a restricted user test on the partner platform · Risk: dual governance that fails the audit.

Who writes this guide

Cédric Mary, editor of Analytics Legends, is a freelance SAP AI & Analytics architect whose delivery focus is the data layer these services run on (Datasphere, Business Data Cloud, Databricks). This guide is written from that vantage point and from the corpus cards listed below, not from a BDC Connect project of his own.

What we cannot assert

We hold no dated SAP statement that BDC Connect for Microsoft Fabric or for native AWS services is generally available; the quarters on this page are targets. One of our cards also describes Iceberg and Snowflake federation patterns under the BDC Connect name without a dated release source, so this page does not present them as available. No source we hold publishes a day rate for the role, and posting counts depend on how skills are tagged.

Frequently asked

Is BDC Connect the same as the SAP Databricks inside Business Data Cloud?

No. SAP Databricks is the commercial offer bundled with BDC; BDC Connect links a Databricks workspace the customer already runs under its own contract.

Does BDC Connect copy SAP data into Databricks?

No. It uses Delta Sharing: the data stays in its authoritative store and is read at query time, which still consumes Databricks compute.

Is BDC Connect for Microsoft Fabric available?

Its target moved to the second half of 2026; at our 27 September 2026 review we held no confirmation that it had shipped. Check SAP's release notes on the day.

Engage the editor

This guide is written by . 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA. Available from 19 October 2026.

Profile and contact

What this page is built on

External sources

Read next