BC Observatoryunofficial, made by waldo
community postIntegration & APIscommunity - not Microsoftreviewed - checked by Opus

Native connection with Fabric in Business Central

Business Central introduces native integration with Microsoft Fabric for data synchronization, replacing the need for APIs or bc2adls tools. The sync operates directly from the SQL database using change logs, supporting all tables with minute-level latency and no impact on Business Central performance.

Open in Claude1318.md

post Discover Microsoft Business Central - The wonderful world of Business Central

Bert Verbeek · 2026-09-30 · 511 words · about 2 min

"No API calls or endpoints needed. No bc2adls is needed. No impact on the NST."
Show the post hereRead on Discover Microsoft Business Central - The wonderful world of Business Central

Key points

  • Native Fabric integration is built on Open Mirroring and syncs from the SQL change log instead of APIs or bc2adls
  • The sync has no NST impact, sends only committed records, supports deletions and arrives within minutes
  • Setup is done in Business Central (workspace, companies, tables) and can be fully managed through APIs
  • The BC environment and the Fabric workspace must be in the same tenant; a Fabric SKU is needed (F2 is usually enough), and the limit is 500 tables
  • bc2adls moves to maintenance mode (until about BC30 or BC31), and BC29 users are advised to test and migrate gradually

Quotes

  • “No API calls or endpoints needed. No bc2adls is needed. No impact on the NST.” (Establishes the core advantages: simplified architecture without external tools and no performance degradation)

Context

  • Features: Native Fabric connection, Open Mirroring technology, Change log-based sync, Deletion support, API-based management, Company selection, Log table support
  • Versions: BC29, BC30, BC31

Source: Discover MS BC - Bert Verbeek, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.