Business Central data in Fabric: the way it should be
Business Central now supports native data mirroring to Microsoft Fabric, allowing users to replicate their tables as Delta Parquet files in OneLake with SQL query access. The feature enters public preview in release wave 2 (likely version 29.1) and requires only workspace setup and table selection with no impact on BC performance or API limits.
"getting the data in is free, using it costs capacity"
Key points
- Native mirroring to Fabric via a new Fabric integration app removes the need for custom data extraction solutions
- Mirror runs a few minutes behind BC, deletes are replicated, and whole tables are copied rather than selected fields
- New BC monitoring pages show sync runs and per-table details, with logs also pushed to Fabric
- No extra BC license cost; Fabric needs a running capacity, replication compute is free, 1 TB storage per capacity unit is free, and querying consumes capacity
- All nine Power BI apps get Fabric-based and multi-company versions
Quotes
- “getting the data in is free, using it costs capacity” (Explains the cost structure, showing BC incurs no licensing expense while Fabric consumption applies separately)
AL objects mentioned
As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.
- other “Fabric integration app”
- page “Synchronization overview”
- page “Synchronization details”
Not found in BC28-30: page “Synchronization overview”, page “Synchronization details”.
Context
- Features: Native Fabric mirroring, Delta Parquet format, SQL endpoint queries, Sync monitoring pages, Configuration packages, Multi-company Power BI apps, OneLake storage integration
- Versions: 29.x, 29.1, 2026 release wave 2
Source: waldo’s blog, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.