Blog / Fabric

How to Set Up Business Central Mirroring to Microsoft Fabric, Step by Step

Tharanga Chandrasekara
Tharanga Chandrasekara
Head of Technology ·
How to Set Up Business Central Mirroring to Microsoft Fabric, Step by Step

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

  1. Open your Fabric workspace and select New item.
  2. Choose Mirrored database, the generic open mirroring item.
  3. 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.

An empty open mirrored database in Fabric, ready for Business Central

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.

The Dynamics 365 Business Central Fabric Export enterprise app in Entra, with its Object ID

Step 3: Give it Contributor on the workspace

  1. In Fabric, open the workspace and select Manage access.
  2. Select Add people or groups and search for Dynamics 365 Business Central Fabric Export.
  3. 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.

The service principal listed as Contributor on the Fabric workspace

Step 4: Run the setup guide in Business Central

Search for Assisted Setup and open Connect to Microsoft Fabric (Preview).

  1. Enter the Principal ID from Step 2.
  2. Pick the Fabric workspace from the lookup.
  3. Skip Add to workspace if you already granted access in Step 3.
  4. Pick the open mirrored database from the lookup.
  5. 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.

The Authentication step of the setup guide with the Principal ID entered

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.

Selecting G/L Entry, Customer, Vendor and Item in the table lookup

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.

  1. Open Microsoft Fabric Mirroring Setup (Preview).
  2. Select Refresh page until Setup Complete is on.
  3. Select Start synchronization.

Export Enabled then switches on. It is a status, not a switch you can set yourself.

The setup page with Setup Complete and Export Enabled both on

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.

The mirrored database in Fabric with four Business Central tables replicating

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.

business-central microsoft-fabric mirroring onelake dynamics-365 data-analytics 2026-release-wave-2
Tharanga Chandrasekara

About Tharanga Chandrasekara

Head of Technology at Equerra

View full profile

Want to discuss this topic?

Our team is always happy to talk through the details.

Book a call

Related posts

Fabric 1 Oct 2026

Business Central now mirrors straight into Microsoft Fabric

Business Central now mirrors directly into Microsoft Fabric, with no pipelines to maintain. Learn the three-step setup, how your data lands in OneLake, and how multi-company Power BI reporting works. It's in public preview now, so it's a good time to run a pilot with Equerra.

Tharanga Chandrasekara Head of Technology
Dynamics 365 8 Nov 2026

Directions EMEA 2026: The Week Copilot Started Doing the Work

Directions EMEA 2026 in Paris was the week Copilot in Business Central started doing the work. With Edit with Copilot it can now create, edit and delete records as the signed-in user, business skills let a customer tell it how their business runs, and the Expense Agent is available in every country where Business Central is offered. In this post I cover the announcements that will matter on real projects, from multiple Sales Order Agents and Payables Agent improvements to report themes, Shopify B2B and the migration voucher. I also explain why agents are still not integration, which parts of Microsoft's direction we already work to at Equerra, and what I brought home about the market and about security.

Tharanga Chandrasekara Head of Technology
AI in Enterprise Technology 8 Nov 2026

Your Best People Are Copy-Pasting Between Systems. That Is About to End

At Directions EMEA 2026 in Paris, Microsoft gave a name to work most of us see every day: people as middleware. A person sits between the ERP, the CRM and every other app, copying numbers from one screen to another and holding the systems together by hand. Microsoft’s answer is to make Dynamics 365 a set of headless business services on MCP. Business Central becomes the trusted layer behind Copilot, agents and portals, with the same posting rules, approvals and permissions applied every time. In this post I cover why the ERP becomes a service, and why the rules behind the screens now matter more than knowing the screens. I explain why agents are not integration, and the message patterns that still need a proper pipeline. I look at where partners fit when customers can build simple agents and apps themselves. Finally, I show how we already work this way at Equerra, with Elevate Integrations and our Frontier platform for building apps, portals and agents safely. People stop holding the systems together and start deciding what the systems should do. That is a much better job.

Tharanga Chandrasekara Head of Technology