Analytics Legends The knowledge platform for SAP Analytics
Guide

SAP Business Data Cloud partner: which kind do you mean

As of 2026-08-14

Ask about an SAP Business Data Cloud partner and you get two answers to two different questions. One is the technology partner — Databricks, Snowflake, Microsoft Fabric, AWS — a platform inside the architecture that can be bought through SAP or connected to it. The other is the delivery partner, the firm that implements it. The confusion is expensive: the first question has a commercial answer with a contract shape attached, the second an evidence answer with a staffing shape attached.

Technology partners: two commercial models

A platform enters the architecture through one of two arrangements, and conflating them in presales creates a real commercial surprise.

A solution extension is commercial. SAP resells the partner's platform under a single purchase order, which simplifies procurement, gives one support escalation path and one security review, and puts one vendor on the hook. The trade is that the customer takes SAP's packaging and pricing rather than negotiating directly at scale.

BDC Connect is technical interoperability, not a commercial bundle. The customer holds separate contracts with SAP and with the platform, and can connect whichever platform the organisation already runs — including one with no solution extension at all.

The two are not exclusive. A customer can hold a solution extension for a managed instance of one platform and use BDC Connect for a second they run independently: the choice is per data flow, not per account.

What the connection service enforces

Whichever platform sits on the other side, four things happen at the integration boundary — which is why the service exists instead of a per-partner connector project.

Authentication runs through SAP's identity service, so the partner platform needs no separate credential store for SAP data. Schema conformance is checked at the gateway, so drift is rejected at the boundary rather than breaking a report days later inside the partner tool. Lineage propagates both ways, so a transformation applied on the partner side feeds its lineage back and an auditor can trace the full chain. And access policy inherits: a user without rights to a cost centre in the semantic layer cannot see it through the partner platform either.

That last control has a precondition nobody advertises. Inheritance replicates whatever access model was designed upstream, including a bad one.

Which platform partner is live when

The rollout is staggered, which matters when a delivery date is promised. Databricks Enterprise was the first partner live: a customer registers an existing workspace as an endpoint, consumes SAP data products natively, and pushes enriched outputs back. Microsoft Fabric follows in Q2 2026, bringing Fabric Lakehouse and OneLake in as endpoints so Power BI can consume BDC-governed SAP semantics without an intermediate load layer. Native AWS services are targeted for Q3 2026.

On the Snowflake side there are two offers announced together on two tracks: the solution extension, where capacity is bought through SAP, and BDC Connect for Snowflake, the technical channel. A scoping document merging them misstates both timelines. The greenfield extension is available; the brownfield path arrives in Q2 2026.

The rule: check which integration is actually available for the client's hyperscaler before promising a date.

Delivery partners: what to ask for

Here the useful screen is evidence rather than badge. Certification alone reads as trainee-level exposure; the signal that separates delivery capability from interest is a completed tenant build with a named reference customer. The nearest adjacent talent pool — experienced BW consultants — typically needs six to eighteen months of reskilling before delivering an engagement independently, which is why the specialist gap does not close quickly.

Three further questions separate partners who have done this from partners who have read about it. Who on the proposed team operates the lakehouse day to day, given that the packaged model changes who bills for it and not who runs it. Who owns schema evolution when two platforms can each write the same shared tables. And what the partner's position is on preserving versus rebuilding existing warehouse logic, because a commercial incentive favouring the larger greenfield engagement will find reasons to recommend it.

The firm directory on this site carries analytics practice profiles you can screen against.

The selection decision, condensed

An existing platform contract you want to keep, plus a requirement to interoperate. BDC Connect — separate contracts, preserved negotiating position.

No existing contract, and vendor count is itself a procurement problem. The solution extension — one purchase order, one support path, one security review, priced on SAP's terms.

Both conditions on different platforms. Both models at once. Common in estates already running more than one lakehouse, and the intended shape rather than an edge case.

A delivery partner with certifications and no completed build. Ask for the reference before the rate.

A delivery partner recommending greenfield before assessing the existing model. Ask which diagnostic produced that recommendation — experienced buyers now screen for this specifically.

What we cannot assert

We do not rank implementation partners on Business Data Cloud capability. SAP's partner competency levels are not a published measure of delivered BDC work, and we hold no verified inventory of completed tenant builds per firm — so this page names what a buyer should ask for, not who should win.

Frequently asked

Solution extension or BDC Connect — what is the difference?

A solution extension is commercial: SAP resells the partner platform under one purchase order with one support path. BDC Connect is technical: the customer keeps separate contracts and connects whichever platform they already run. A customer can hold both at once on different platforms — the choice is per data flow, not per account.

Which technology partners are live on BDC Connect?

Databricks Enterprise was the first live. Microsoft Fabric is targeted for Q2 2026 and native AWS services for Q3 2026, and Snowflake runs on its own two tracks — an available greenfield solution extension with the brownfield path in Q2 2026, plus the BDC Connect channel.

How do I screen an implementation partner?

Ask for a completed tenant build with a reference customer rather than a certification count, name the person who operates Spark, Delta and Unity Catalog day to day, and ask who owns schema evolution across the two platforms. Certification alone reads as exposure rather than delivery on a platform this young.

Does connecting a partner platform mean moving data into SAP?

No. Raw data stays in the partner platform; SAP data products flow in and enriched outputs flow back, with lineage propagating both ways. A project plan including a data-migration workstream for this has been scoped against the wrong mechanism.

What this page is built on

Read next