Let’s flow your Business Central data into Microsoft Fabric

Let’s flow your Business Central data into Microsoft Fabric

On 23th of May Microsoft announced Microsoft Fabric:
Introducing Microsoft Fabric: The data platform for the era of AI | Azure Blog | Microsoft Azure

With Microsoft Fabric you have only one source for all your data. So you don’t have to move data to another data warehouse or data lake. It is based on OneLake.
But also there is a seamless integration with the core workloads.

So for analyze and report data this is a huge advantage!

But can you also pull your Business Central data into OneLake?

Luckely wel can! And therefor you have to create a Lakehouse inside MS Fabric.
A Lakehouse is more or less a place where you can store unstructured data of any source in folders and files, databases and tables.
Microsoft has created a good overview what the difference are to store data in MS Fabric:
Fabric decision guide – lakehouse or data warehouse – Microsoft Fabric | Microsoft Learn

In a Lakehouse you can get data from several places.
For Business Central you have to get your data from a Dataflow Gen2:

There you can choose from another source. And you can type in Business Central:

Then you will see the Business Central dataflow connector.
When you have clicked it you can fill in the “Environment”, “Company” and “API Category”.

But you can leave that empty and when you have verified the signin it will show you all the excisting environments and companies inside Business Central with all the API’s.

NB: Please set the UseReadOnlyReplica to true by the advanced features!

Here you can choose which tables you want to have in your OneLake.

NB: sometimes you get an error that you there are empty fields. Then you have to remove the extended columns in the table as show in picture below:

When you have published it you can set the refresh rate and you can see that all your data (in this case vendors) are stored in your OneLake:

So now you can work with Notebook on your data or let your data flow in the warehouse through a pipeline:

That will create a pipeline for you:

And that pipeline will import your lakehouse data into a structured table:

So in this case you store you BC data into a OneLake and can update it very frequent and analyze it from there without disturbing your Business Central Users!


Javier Sassen

This looks great! Is this also possible using a service principal as authentication, instead of a named user?

    Bert Verbeek

    Hi Javier, it is not possible to use a service principal as an authentication.

Leave a Reply

Your email address will not be published. Required fields are marked *

The reCAPTCHA verification period has expired. Please reload the page.