If you haven’t already, check out Arun Ulag’s hero blog “FabCon and SQLCon 2026: Unifying databases and Fabric on a single, complete platform” for a complete look at all of our FabCon and SQLCon announcements across both Fabric and our database offerings.
Overview
Integrating Dynamics 365 Business Central with Microsoft Fabric is a common requirement as organizations modernize their analytics platforms. The primary challenge is not connectivity, but establishing an architecture that scales predictably, protects the ERP system, and enables analytics teams to focus on insights rather than maintaining ingestion pipelines.
In this post, we'll cover how the BC2Fab Fabric Workload from Navida can be used to replicate Business Central data into Fabric using an Open Mirroring architecture.
Problem statement
Business Central and Fabric are designed for different types of workloads. Business Central supports transactional processes such as accounting, purchasing, inventory, and order management. Fabric is designed for analytical workloads such as reporting, data science, and AI.
When organizations use traditional ingestion patterns between these systems, several challenges often appear:
- Fabric capacity usage increases when ingestion pipelines perform heavy transformations.
- Refresh times grow as data volumes and customizations increase.
- Production ERP environments experience additional load from analytical queries.
- Data teams spend time maintaining pipelines instead of building analytics solutions.
These challenges often appear when solutions move from pilot environments into production. Organizations therefore benefit from an architecture that keeps ingestion predictable and allows analytics workloads to run independently.
Architecture overview
The
BC2Fab Fabric Workload provides an integration layer between Dynamics 365 Business Central and Microsoft Fabric. Business Central data is replicated into Microsoft OneLake, the unified storage layer in Fabric. Once the data is stored in OneLake, it can be accessed through Fabric experiences without creating additional copies. The architecture separates data replication from analytics workloads so that ERP systems remain focused on transactional operations while analytics runs in Fabric.
Architecture_diagram_showing_Business_Central_data_replicated_by_the_BC2Fab_FabrFigure: BC2Fab Fabric Workload Architecture
The architecture consists of four main layers:
- Business Central (source system): Business Central stores operational and financial data used by the organization. Data is retrieved through APIs or read-only replicas to avoid impact on transactional workloads.
- BC2Fab Fabric Workload (replication layer): The BC2Fab Fabric Workload from Navida synchronizes Business Central data into Fabric using incremental change detection. It manages table replication, metadata configuration, and schema updates.
- OneLake storage (data layer): Replicated data is stored in OneLake using open storage formats. Because OneLake is shared across Fabric workloads, the same dataset can support multiple analytical scenarios.
- Fabric engines (analytics layer): Once the data is available in OneLake, teams can build analytics solutions using Fabric experiences such as Data Engineering, Data Warehouse, and Microsoft Power BI for reporting and AI/Copilot scenarios built on ERP data.
Using Business Central data in Fabric
Once
Dynamics 365 Business Central data is available in
Microsoft Fabric, analytics teams can begin building reporting and analytical solutions on top of the replicated datasets. Common scenarios include:
- Financial reporting and profitability analysis
- Sales and revenue performance tracking
- Inventory and supply chain monitoring
- Customer and product analytics
Because the data is stored in
Microsoft OneLake, it can also be combined with other datasets already present in Fabric. This allows organizations to extend ERP reporting with additional operational or analytical data sources.
What clients say
Organizations using the
BC2Fab Fabric Workload have shared their experiences after implementing the solution in Microsoft Fabric environments. The following perspectives highlight how teams are using Business Central data in Fabric for analytics and reporting.
“BC2Fab deployed to a production workspace in Fabric—no more time spent wrangling data into tables or managing multiple Gen2 dataflows. I can now focus on using Fabric, trusting my Business Central data is already there. Even large Business Central tables—including custom extension fields and tables with 165M rows were available far earlier than planned thanks to metadata-driven configuration. Within the first week, this translated into real, measurable improvements across both daily operations and month-end processes."
- Richard Swift, Finance Systems Manager, Enable Networks Limited (New Zealand)
“Getting Business Central data into Fabric used to be a headache. After the 2023 SQL Server Konferenz we searched everywhere for a reliable approach—until the BC2Fab Workload for Fabric finally solved it. Fast setup, no oversized capacity, and most importantly: it just works. Stable, low‑maintenance, and exactly what a critical data pipeline need. Now our engineers can focus on modeling, analytics, and insights instead of fighting ingestion and sync issues”
- Steffen Genz, Head of Business Analytics at AXRO GmbH (Germany)
“I have been using Business Central for years, but BC2Fab allows me to become data driven. I can get all the insights I need to make the right decisions.”
- Frank Glockzin, Managing Director, Glockzin (Germany)
Now available
The
BC2Fab Fabric Workload from Navida is available for organizations that want to replicate Dynamics 365 Business Central data into Microsoft Fabric.
Organizations adopting Fabric for analytics can use the workload to bring ERP data into OneLake and begin building reporting and analytical solutions on top of Business Central data.