Quick Answer 

Business Central connects to Power BI through a native OData/API connector: a live Direct Query, a scheduled Import refresh, or reports embedded inside Business Central itself. For large data volumes, many teams add Microsoft Fabric or Azure Data Lake as a middle layer. The right method depends on data volume, refresh needs, and who is building the reports. 

If you run finance, sales, or operations on Business Central, you already know the reporting problem. Native reports cover the basics, but the moment someone needs a three-year trend or a dashboard that updates on its own, you are back in Excel, exporting data and rebuilding the same pivot table next month. That cycle costs time and creates errors the moment two people pull the same numbers on different days. 

Power BI fixes this by connecting directly to Business Central data, so reports update automatically instead of by hand. But there are several valid ways to connect the two systems, and the right one depends on your data volume, how current the numbers need to be, and who will build and maintain the reports. This post covers the real options, a step-by-step setup for the most common one, and where the standard connector hits its limits. 

Why Businesses Struggle to Connect Business Central Data to Power BI 

Business Central was built to run transactions, not answer executive-level questions. Its native reports are fine for operational checks, but were not designed for cross-functional analysis, historical trends, or the dashboards leadership expects, especially once you add multiple companies or currencies. 

Most teams fill the gap manually: someone exports data, pastes it into Excel, and rebuilds the same pivot tables every reporting cycle. It works until the business grows or two departments report different numbers from the same source, at which point it becomes a credibility problem, not just wasted hours. Power BI is the natural fix, and Microsoft was named a Leader in Gartner’s 2026 Magic Quadrant for Analytics and Business Intelligence Platforms for the 19th consecutive year, with more than 35 million monthly active users across Power BI and Fabric. The part that actually trips teams up is choosing the right method and keeping the data accurate once it is connected. 

By the Numbers 

Microsoft was named a Leader in Gartner’s 2026 Magic Quadrant for Analytics and Business Intelligence Platforms for the 19th consecutive year, with 35 million-plus monthly active users across Power BI and Fabric. 

Source: Microsoft (Power BI Blog, Microsoft Fabric Community) 

Still rebuilding the same Excel report every month?  Talk to Addend Analytics 

Three Ways to Connect Business Central to Power BI 

There are three practical paths into Power BI, and most Business Central users end up using more than one as they mature. 

1. The Native Power BI Connector (OData and API) 

This is the standard route, and the one most teams start with. In Power BI Desktop, connect through Get Data, Online Services, Dynamics 365 Business Central, using the same account you use to sign into Business Central. The connector reads from API pages or OData web services that Business Central publishes, and since February 2022, Business Central online has served these reports from a secondary, read-only database replica so reporting does not compete with transactional performance. It is free to start and good enough for most single or few-company deployments, though it strains with very large data volumes or long history. 

2. Embedding Power BI Reports Inside Business Central 

Instead of asking users to leave the ERP, you can embed a finished Power BI report, page, or visual directly onto a Role Center or list page, configured by an administrator or added programmatically in AL by a developer. This keeps day-to-day users looking at live, governed reports without a second login. It is a distribution layer, not a replacement for building the reports themselves. 

3. Microsoft Fabric or Azure Data Lake for Scale 

Once you are dealing with several companies, years of history, or a need to blend in data from other platforms, the native connector starts to strain. Many teams add a middle layer instead, most commonly the open-source bc2adls extension, which exports Business Central data incrementally into Azure Data Lake Storage or Microsoft Fabric’s OneLake. Power BI then queries that governed copy rather than hitting Business Central directly, and Fabric’s newer Direct Lake mode can serve near real-time reports without a separate import step. This path takes more setup and usually needs data engineering and integration expertise, but it is the most realistic way to get near real-time dashboards at scale. 

Here is how the three approaches compare: 

Step-by-Step: Connecting Business Central to Power BI 

For most organizations, the native connector is the right starting point. Here is the setup, from licensing to a working report. 

1. Confirm licensing. Business Central includes a free Power BI license for core viewing and personal reports; sharing reports broadly needs Power BI Pro or a Fabric capacity. 

2. Open Power BI Desktop and go to Get Data, then Online Services, then Dynamics 365 Business Central, and sign in with your Business Central account. 

3. Choose your environment and company. Business Central’s Web Services page shows exactly which API pages, queries, and OData services are available. 

4. Decide between Import, which caches a scheduled snapshot for faster performance, and Direct Query, which pulls live data but adds load to Business Central. 

5. Build the semantic model: set relationships, write your core measures, and add row-level security if more than one company will share a workspace. 

6. Publish to the Power BI service, set a refresh schedule that matches real decision-making, and share the report through a workspace or app. 

7. Optionally, embed the finished report back into Business Central so day-to-day users see it without leaving the ERP. 

Want this set up right the first time?  Get help from our Power BI team 

Building Business Central Power BI Reports and Dashboards People Actually Use 

Connecting the data is the easy half. Reports that actually get used share a few habits. 

• Start with a KPI summary page, with drillthrough into detail, instead of five separate reports for five departments. 

• Build around decisions, not departments: one sales-and-inventory view beats two reports nobody cross-references. 

• Use row-level security instead of copies, filtering one governed dataset by company or region. 

• Reconcile against Business Central regularly, not just at go-live. 

The most common reports cover accounts receivable aging, cash flow and general ledger trends, sales performance, and inventory exposure. Start with whichever is currently costing the most manual hours, prove it out, and expand from there. 

Is Business Central to Power BI Integration Actually Real-Time? 

This is the question that catches teams off guard. The standard connector is not a live stream: practitioners on the Dynamics 365 community forums describe the typical refresh cadence as every 15 to 60 minutes on a scheduled job, not continuous (Dynamics 365 Community). Direct Query narrows that gap by querying Business Central live on every interaction, but it adds load and does not scale well to large datasets or many concurrent users. 

For most finance and operations reporting, a 15 to 60 minute refresh is fine, since decisions about pricing or cash position are rarely made minute to minute. Where near real-time genuinely matters, such as manufacturing floor visibility, Microsoft Fabric’s Direct Lake mode gets closer by serving reports directly from OneLake, though that is a meaningfully bigger project worth confirming you actually need. 

Solving the Data Accuracy and Synchronization Challenge 

Accuracy problems in Business Central Power BI reports rarely come from the connector itself. They come from governance gaps: refresh timing users do not understand, and overlapping reports built from different filtered exports of the same data. 

• Put a visible refresh timestamp on every report. 

• Map company, currency, and dimension structures once, in a shared semantic model. 

• Use row-level security instead of exporting filtered subsets that drift out of sync. 

• Assign clear ownership of the semantic model, so changes go through one place. 

None of this is unique to Business Central. It is the same governance discipline any connected BI environment needs, but it matters more here because finance and operations depend on the same ledger. 

Why Addend Analytics Is the Right Call 

A single-company Business Central setup with a handful of standard reports is genuinely a do-it-yourself project. The native connector, a few hours in Power BI Desktop, and some patience with measures will get most teams a working report. The calculation changes with multiple entities, multiple currencies, large data volumes, or a Fabric layer in the mix, where a wrong call on semantic model design or security is expensive to unwind later. 

This is where Power BI consulting services and data engineering and integration expertise earn their cost. Addend Analytics works inside the Microsoft ecosystem full time, not as a generalist add-on, and has taken Business Central, Dynamics, and Fabric integrations live across manufacturing and distribution environments; our client results reflect what that looks like in practice. As covered above, most projects run into trouble on governance rather than the connection itself, and that is where we spend the most design time before a single dashboard gets built. If the goal is a broader analytics roadmap rather than one dashboard, that is worth scoping first. 

Most Business Central to Power BI projects do not fail on the technology. They fail on governance: who owns the semantic model, how refresh timing matches the pace of real decisions, and how row-level security maps to the way the company is actually structured. Get that right first and the reports take care of themselves. 

Kamal [Surname to confirm], Data & Analytics Lead, Addend Analytics 

Business Central and Power BI are built to work together, and the native connector gets most teams a working report in an afternoon. The real decisions are about freshness, governance, and scale, and getting those right is what turns Power BI from another export people double-check into the number the business actually trusts. 

Ready to Turn Business Central Data Into Reports Your Team Trusts? 

Addend Analytics helps Business Central users design the connection method, semantic model, and dashboards that fit how their business actually runs, not a generic template. 

Talk to our Power BI team 

Author By

Rajeshwari Sharma

rajeshwari.s@addendanalytics.com

Rajeshwari is an experienced data professional with a track record of using data-driven insights to improve business performance. She has successfully managed multiple projects, utilising her expertise in data analysis and database administration. As a Microsoft-certified Data Analyst and Azure Database Administrator, she has cultivated a deep understanding of data management best practices and advanced analytics techniques. Her MBA in Business Analytics has equipped her with a solid foundation for integrating business strategy with data insights.