Skip to main content

SAP Business Data Cloud · Microsoft Fabric · Datasphere

Chemicals SAP BTP SAP Business Data Cloud SAP BW

Connecting SAP Business Data Cloud to Microsoft Fabric for a global specialty manufacturer

A Global Specialty Manufacturer Delivered 2025–2026

Mindset enabled SAP Business Data Cloud for a global specialty manufacturer and built the integration from Datasphere to Microsoft Fabric, turning years of Fiori and BTP advisory work into a live enterprise analytics connection.

By the numbers

  • 3 connection types

    Data-source connection types validated (table, CDS view, extractor)

  • 2 phases

    BDC setup and Fabric integration delivered in structured phases

  • 7 years

    Relationship span from Fiori advisory (2019) through BDC/Fabric delivery (2026)

Before

SAP data, no path to Fabric

  • A BDC environment that had been handed over but not yet validated or fully configured.
  • No live connection between SAP Datasphere and Microsoft Fabric for enterprise analytics.
  • Fiori and BTP strategy in place from prior advisory work, but no delivery against the data architecture.

After

SAP Business Data Cloud connected to Microsoft Fabric

  • BDC fully set up with ERP and BW connectivity, three data-source types validated.
  • SAP Datasphere premium outbound integration feeding Microsoft Fabric live.
  • Mindset's proprietary BTP/BDC cost-analysis tool running on the client's environment.

Why this matters

One of the first SAP Business Data Cloud to Microsoft Fabric integrations in the market, built on a seven-year relationship that started with Fiori workshops and grew into a technically distinctive data architecture. The advisory-to-delivery arc is the real story.

The challenge

The manufacturer wanted its SAP data in Microsoft Fabric for enterprise analytics. Getting there required standing up an SAP Business Data Cloud environment, validating it after handover, and connecting it to Fabric using SAP Datasphere's premium outbound integration.

The work built on a multi-year relationship. Mindset had run Fiori and embedded analytics strategy workshops with the company in 2019 and 2021, then a BTP advisory engagement in 2023. By 2025 the client was ready to move from advisory into a technically distinct data architecture that not many teams had built yet.

What we did

Mindset structured the work in two phases, led by a principal BTP and data architect.

Phase 1 ran three to five weeks. The team analyzed and validated the SAP BTP and BDC environment after its handover, then set up Business Data Cloud from the ground up: initial connectivity, platform security and user enablement, scalability configuration, in-scope ERP and BW system connectivity, Cloud Connector updates, and confirmation of three data-source connection types, covering table replication, CDS views, and extractors. Mindset deployed its own proprietary BTP/BDC cost-analysis tool on the environment and provided architecture guidance, training, and a knowledge-transfer program throughout.

Phase 2 moved into the SAP Datasphere premium outbound integration to Microsoft Fabric, delivered by a blended US and India team: an architect, two developers, and a delivery lead working through the full BDC-to-Fabric connection. The phase extended BDC enablement and brought the analytics integration live.

The outcomes

The manufacturer moved from Fiori strategy discussions in 2019 through a BTP advisory pod in 2023 to a live SAP Business Data Cloud environment connected to Microsoft Fabric in 2025 and 2026. The architecture, SAP Datasphere premium outbound integration feeding Microsoft Fabric, is technically distinctive and relatively rare in the market.

Mindset's proprietary BTP/BDC cost-analysis tool was deployed on the client's environment as part of the engagement, giving the team ongoing visibility into platform costs as the data footprint grows.

If we built this today

Concept · not delivered scope

Govern the data before it reaches Fabric.

This is a forward-looking concept, not the scope we delivered on this engagement. It is the build we would reach for now, grounded in SAP that ships today.

This manufacturer wanted its SAP data inside Microsoft Fabric for enterprise analytics, which meant standing up Business Data Cloud, validating it after handover, and connecting it to Fabric with the business meaning carried across, not just the rows.

The data product

Outbound data products on SAP Business Data Cloud

The curated, governed datasets BDC exposes through Datasphere premium outbound integration, plus the zero-copy share between Business Data Cloud and Microsoft Fabric that SAP and Microsoft have been building out, available now in parts and GA-ing in 2026. These data products are what land in Fabric with their business meaning intact instead of raw table dumps.

Data products on Business Data Cloud

The Joule agent

Knowledge Graph Navigator

Reads the governed business semantics that SAP Knowledge Graph lays over BW, Datasphere, and the new SAP Business Data Cloud foundation, then proposes which curated data products to publish outbound to Microsoft Fabric and flags where lineage or definitions drift between the SAP and Fabric sides. It drafts the share, a human confirms the scope.

SAP Business Data Cloud, SAP Datasphere, SAP BW, SAP BTP, SAP Knowledge Graph · PROPOSE · Time to a governed, business-ready data product live in Fabric

The Fiori app

SAP Business Data Cloud cockpit with embedded Joule

This is a BTP and Business Data Cloud surface, not an S/4HANA transactional Fiori app, so we will be honest about that. You manage connections, data products, and outbound sharing from the BDC cockpit, with Joule embedded to explain a data product and walk you through publishing it to Fabric.

Embedded in the Business Data Cloud cockpit, not the S/4HANA launchpad

We would still mine the actual reporting and data flows in SAP Signavio first, map the BW and Datasphere estate in SAP LeanIX so we know what is worth publishing, and let MIND accelerators carry the old extracts forward to governed BDC data products.

The Joule Agent Factory Process intelligence

What we built

  • Three data-source connection types confirmed (table, CDS view, extractor)

    SAP BDC environment setup and validation

    Full setup of the SAP Business Data Cloud environment after handover: connectivity, platform security, user enablement, scalability configuration, and in-scope ERP and BW system connectivity.

  • Connectivity validated across in-scope ERP and BW systems

    SAP Cloud Connector updates

    Cloud Connector configuration updated to support the BDC and Datasphere integration pattern.

  • SAP data flowing into Microsoft Fabric for enterprise analytics

    SAP Datasphere premium outbound integration to Microsoft Fabric

    The core Phase 2 deliverable: a live integration path from SAP Datasphere to Microsoft Fabric using the premium outbound integration capability.

  • Proprietary tooling deployed and transferred to the client team

    Mindset BTP/BDC cost-analysis tool

    Mindset deployed its proprietary BTP/BDC cost-analysis tool on the client's environment, giving the team ongoing visibility into platform costs.

  • Full knowledge transfer included in both Phase 1 and Phase 2

    Architecture guidance and knowledge transfer

    Architecture guidance, training, and a knowledge-transfer program delivered throughout both phases so the internal team could own the platform.

  • Scalability assessment delivered as part of Phase 1

    BTP scalability assessment

    A review of the BTP and BDC environment's scalability posture, ensuring the architecture supports the company's data growth path.

  • Seven years of consistent relationship, advisory to delivery

    Multi-year Fiori and BTP advisory foundation

    The analytics work built on Fiori and embedded analytics strategy workshops in 2019 and 2021 and a BTP advisory engagement in 2023, which established the technology direction that Phase 1 and 2 executed against.