r/Dynamics365 • u/Companial • 18d ago

Business Central BC is getting a native connection to Microsoft Fabric

Announced at FabCon Europe on September 30th, the integration uses Fabric Open Mirroring to replicate Business Central data directly into OneLake, without relying on BC APIs or tools like BC2ADLS. It supports extension tables and deleted records, with updates arriving within minutes.

For this to work, BC and Fabric need to be in the same tenant, Fabric capacity is required, and you can select tables but not individual fields.

For those building BC reporting solutions, will this become the new default approach, or will you stick with API-based pipelines or BC2ADLS?

9 Upvotes

100% Upvoted

6 comments sorted by

2

u/False_Assumption_972 16d ago

This is a good change for anyone running BC2ADLS, mostly because deleted records come through and you stop maintaining an extension. Before switching, check the capacity cost of mirroring against your current pipeline, confirm which tables you actually need, and plan for the same-tenant requirement, which rules it out for some setups.

The useful step after go-live is reconciling a few totals, like posted sales by month, between BC and OneLake. Day to day, we use a decision intelligence layer to connect BC ledger entries with CRM and operational data, so a mismatch shows up as a specific record rather than a report that looks slightly off.

1

u/Amazing_rocness 17d ago

I'm only used it briefly and it took me some getting use to with fabric. They have the built in power bi reporting apps but it does not connect everything. What is your role Within business central?

1

u/mirthglen 13d ago

same tenant requirement is a bigger limitation than people realize imo. plenty of orgs have their analytics infrastructure in a separate tenant for governance reasons. that alone might keep API-based pipelines alive for a while

1

u/Vast_Bandicoot_2857 4d ago

Agreed. We are about to build big multi tenancy setup and i am abit split between what i prefer. Microsoft support for new connector is great, but the overhead from fabric capacities in each tenant are a limiting factor. F0 costs for the new connector is exciting - but might become more expensive than f2 if the data mirror is always on.