Business Central to Microsoft Fabric: when it is worth it

Moving your Business Central data into Microsoft Fabric is not an upgrade, it is a shift in what becomes possible. When your operational ERP data sits inside Fabric alongside everything else, the questions you can ask and the speed at which you can answer them change considerably.

Microsoft is keen for you to connect Business Central to Microsoft Fabric, and there is now a built-in link that makes it easy to do. Easy to do is not the same as worth doing, and the fact that the roadmap points somewhere is not a reason to follow it today. For some businesses the link is a real step forward. For many, Power BI on a simpler warehouse does the same job for less. Here is how to tell which you are.

In practice, this is where our Business Central analytics work comes in, and whether you actually need Fabric yet covers useful related ground.

What the Business Central and Fabric link does.

The link copies your Business Central data into Fabric, into Microsoft's OneLake storage, kept up to date without anyone building and maintaining custom pipelines. From there the data is available to Power BI, to other Fabric tools, and to be combined with other sources, all on one platform and one bill. It removes a chunk of the plumbing that used to sit between Business Central and good reporting, and it keeps the data close to current. As a piece of engineering it is a clear improvement on hand-built extracts.

When it is worth it.

The link earns its keep when you have outgrown simple reporting. When Business Central is one of several sources you need in one place. When you have real volume, or want history well beyond what Business Central keeps. When you are serving a large reporting audience, where a Fabric capacity starts to make sense on its own terms. Or when you are heading towards the wider Fabric workloads, data engineering, machine learning, real-time, and want Business Central data sitting alongside everything else. If two or three of those are true, the link is a sensible foundation.

When it is not, yet.

It is not worth it when Business Central is your only source, your volumes are modest, and your needs are finance and operational reporting for a normal-sized audience. In that case a Fabric capacity is paying for scale you do not have, and Power BI on a tidy Azure SQL warehouse, or even the built-in connections to start, will serve you just as well for a fraction of the cost. Adopting Fabric because it is where Microsoft is heading, rather than because your work needs it, is a common and expensive mistake.

Do it for a reason, not the roadmap.

The principle is the same one that governs every platform decision: size it to the business, not to the brochure. The Business Central and Fabric link is a good thing when there is a real reason to reach for it, and an unnecessary cost when there is not. The roadmap will still be there when your work catches up with it, and you lose nothing by waiting until it does, while you can lose a good deal by going early.

So this week, ask one question: is Business Central your only real source of data, with modest volumes and a normal audience. If it is, you probably do not need Fabric yet, and Power BI on a simple warehouse will do nicely. If it is not, the link is worth a serious look. Working out which side of that line you sit on is the heart of our Microsoft Fabric and data platform work, and our Do You Actually Need Fabric guide takes it further. Easy to switch on was never the question. Worth switching on is.

If any of this sounds familiar, talk to us about your data.

Related reading

• The end of the visual hack
• Power BI or Business Central’s built-in reporting?
• Getting your Business Central data into Power BI: the options