Mirroring Business Central data to Microsoft Fabric: how it works

Until now, analysing Business Central figures in Power BI meant building your own connection through APIs or an intermediate solution. That is changing. At FabCon Europe in Barcelona on 29 September 2026, Microsoft announced data mirroring for Business Central in Microsoft Fabric. It lets you mirror your Business Central data directly to Fabric. In this article you read what it is, what you need, what it costs and when it makes sense.

What is Business Central mirroring to Fabric?

With mirroring you create a mirrored copy of Business Central tables in Microsoft Fabric. That copy lands in OneLake, Fabric’s central data lake, and stays up to date automatically. From there you use the data in Power BI, in a lakehouse or data warehouse, or with Copilot.

The big difference from your own connection: you build nothing. No API development is needed and there are no export jobs to maintain.

What do you need?

• Business Central online, version 29 (2026 release wave 2);
• Microsoft Fabric capacity (F SKU starting at F2) or an existing Power BI Premium capacity;
• permissions to create a mirrored database in Fabric and connect Business Central to it.

At the time of writing, Microsoft is still updating its documentation. Check the current status and conditions before using it in production.

How to set it up

1. Create a mirrored database in Fabric. Business Central is not listed among the regular sources in Fabric; you select Business Central mirroring as a separate option.
2. Connect Business Central. You link your Business Central environment to the mirrored database.
3. Choose companies and tables. You select which companies and tables to mirror. The first synchronisation then starts.

The first synchronisation takes longest, because all existing data is transferred. After that only changes come across, with a delay of a few minutes.

What it can and cannot (yet) do

• Multiple companies: you can mirror tables from several companies at once;
• All fields: you choose tables, not individual fields. All fields of a table are included;
• Deletions: records deleted in Business Central also disappear from the mirror;
• No API load: mirroring uses an internal Microsoft replication service rather than the Business Central APIs. It does not count against the API limits and has no noticeable impact on your production environment.

What does it cost?

On the Business Central side, mirroring costs nothing extra. You only pay for capacity and storage in Fabric. Microsoft also offers an F0 capacity in public preview where you pay only for what you use; it is mainly suited for experimenting, not for production.

Mirroring or your own connection: which to choose?

For analysis and reporting on Business Central tables, mirroring is the simplest route: quick to set up, little maintenance and no load on your APIs. Your own API connection still makes sense if you run an older version of Business Central, want to transform data at the source or need to write data back to Business Central. Often the best solution is a combination, with Fabric also bringing in data from other systems.

How Bluace uses this

Bluace delivers Microsoft Fabric and Power BI as the data layer of the Business Central solution. At customers such as ESNW we use Fabric for insight into large volumes of data: item usage, contract trends, resolution times and employee performance. Mirroring makes that foundation simpler and faster to set up.

Read more on our page about Microsoft Fabric for Business Central or see what Business Central can do for your business.

Frequently asked questions about Business Central and Fabric