In October we wrote about how Business Central now mirrors straight into Microsoft Fabric. Since then Microsoft has released the app and published the setup documentation, and we have set it up end to end on a Business Central 29.1 sandbox.
This is the step-by-step version, including the parts that are easy to get wrong. If you want to see every screen, I have written a screen-by-screen walkthrough on my personal blog.
Before you start
Check these first. They save more time than any step below.
- Business Central online with the Microsoft Fabric Mirroring app. On our 29.1 sandbox, the Business Central Mirroring to Fabric app was already installed.
- A Fabric workspace on an active Fabric capacity. A trial capacity is fine for a pilot. A paused capacity stops replication.
- The same Microsoft Entra tenant for Business Central and Fabric.
- The right roles. At least Member on the Fabric workspace, Application Administrator or Cloud Application Administrator in Entra, and the MS Fabric Mirroring - Admin permission set in Business Central.
Step 1: Create an open mirrored database in Fabric
- Open your Fabric workspace and select New item.
- Choose Mirrored database, the generic open mirroring item.
- Give it a name, such as
BC_Production_Mirror, and select Create.
Leave it empty. Business Central fills it later, and there is nothing to copy across, because Business Central finds the workspace and database through its own lookups.

Step 2: Create the service principal for Microsoft's app
You do not need your own app registration or client secret. Business Central authenticates with a Microsoft-provided app called Dynamics 365 Business Central Fabric Export, application ID dcc80069-ba40-4ad9-ba8c-60001cea3497. You only create its service principal in your tenant.
Microsoft documents four ways to do it: Azure Cloud Shell, Azure CLI, Microsoft Graph PowerShell or Graph Explorer. Whichever you use, keep the Object ID it returns. Business Central calls it the Principal ID.
If you use Graph Explorer, consent to Application.ReadWrite.All first. In our test the request returned 403 without it, even with Directory.ReadWrite.All already granted.

Step 3: Give it Contributor on the workspace
- In Fabric, open the workspace and select Manage access.
- Select Add people or groups and search for Dynamics 365 Business Central Fabric Export.
- Choose Contributor and select Add.
The Business Central setup guide also has an Add to workspace action that does this for you. In our test it failed with a Fabric token error, so we recommend granting access in Fabric directly. Microsoft documents this as the fallback.

Step 4: Run the setup guide in Business Central
Search for Assisted Setup and open Connect to Microsoft Fabric (Preview).
- Enter the Principal ID from Step 2.
- Pick the Fabric workspace from the lookup.
- Skip Add to workspace if you already granted access in Step 3.
- Pick the open mirrored database from the lookup.
- Select Connect to Fabric and approve the privacy notice. Business Central may also ask whether it can call an external service.
Connect to Fabric runs in the background. Select it once. A second request within 15 minutes is blocked while the first one is still running.

Step 5: Choose companies and tables
Still in the guide, add at least one company and at least one table. The table lookup only shows tables that are eligible for export, and you can select up to 1,000 tables in total. You choose whole tables, not individual fields.
For a quicker start, the app includes the Microsoft Standard configuration package, which lists 256 standard tables chosen for analytics.

Step 6: Start synchronization
This is the step most people miss. Finishing the guide does not start synchronization, even though the last page suggests it does.
- Open Microsoft Fabric Mirroring Setup (Preview).
- Select Refresh page until Setup Complete is on.
- Select Start synchronization.
Export Enabled then switches on. It is a status, not a switch you can set yourself.

Step 7: Check the first run
Open Monitoring > Fabric Synchronization Overview in Business Central to see each run and its state, and Monitor replication on the mirrored database in Fabric to see the rows arriving. In our test, the first export of four tables took about six minutes, with 4,214 rows in G/L Entry.

If something does not work
- Lookups come back empty. Check that the service principal exists, and ask your Fabric administrator whether the tenant setting Service principals can call Fabric public APIs is on.
- Add to workspace fails. Grant Contributor in Fabric through Manage access, as in Step 3.
- The guide finished but no data arrived. Select Start synchronization on the setup page.
- Synchronization stopped on its own. Max Consecutive Failed Runs (default 2) stops synchronization after repeated failures. Fix the cause, then start it again.
- Data stopped arriving in Fabric. Check whether the Fabric capacity has been paused.
Get started with Equerra
Setting up mirroring takes an afternoon. Choosing the right tables, sizing the Fabric capacity, securing the workspace and building reports your team trusts takes more thought, and that is where we help.
Book a Fabric readiness session with Equerra and we will help you run a pilot on your own Business Central data.


