Business Intelligence for Manufacturing: Using Power BI with Dynamics 365
Most manufacturers don't have a data problem. They have a visibility problem. Production orders, capacity entries, scrap postings, purchase receipts and cost variances all sit in Microsoft Dynamics 365. Yet when a COO asks why margins slipped last quarter, or a plant manager wants to know which work center will bottleneck next week, the answer still tends to come from exported spreadsheets and a lot of manual effort.
Business intelligence closes that gap. For manufacturers running Dynamics 365, Power BI is the natural BI layer. It connects natively to the ERP, it can be embedded directly into the screens people already use, and it shares security and licensing with Microsoft 365.
But "use Power BI" is where most advice stops. The decisions that determine success are more specific:
- Which Dynamics 365 product you run, and what reporting it already includes
- How you connect to the data
- Which KPIs you model
- How you license the people who consume the reports
This article walks through each of those decisions for senior analysts and IT leaders responsible for manufacturing reporting.
What Is Business Intelligence for Manufacturing?
Business intelligence for manufacturing turns production, inventory, quality, supply chain and financial data into dashboards and reports. Those dashboards help plant managers, operations leaders and finance teams make faster, better-informed decisions about capacity, cost and delivery performance.
In a Microsoft environment, the roles are clearly divided. Dynamics 365 is the system of record that captures every transaction. Power BI is the analytical layer that models, aggregates and visualizes that data.
The difference between the two is important. A standard ERP report tells you what happened on a single production order. Business intelligence answers broader questions:
- Which work centers consistently run over capacity?
- Which items drive the most scrap cost?
- Is the plant on track to meet next month's delivery commitments?
Why Power BI Is the Default Choice for Dynamics 365 Manufacturers
Manufacturers already on Dynamics 365 rarely run an open-ended BI tool selection, and for good reason:
- Power BI has native connectors for both Dynamics 365 Business Central and Dynamics 365 Finance and Supply Chain Management.
- Microsoft ships prebuilt Power BI content for both products.
- Reports can be embedded inside Dynamics 365 workspaces, so a supervisor can see utilization data without leaving the ERP.
- Identity, governance and licensing run through the same Microsoft tenant.
So the more useful question isn't whether to use Power BI. It's how to build a reporting architecture that plant teams will trust and that scales from one site to many. That starts with understanding which Dynamics 365 product you run.
What Power BI Reporting Comes with Your Dynamics 365 Product?
Dynamics 365 Business Central
For small and mid-sized manufacturers on Dynamics 365 Business Central, Microsoft provides a dedicated Manufacturing Power BI app. It became generally available in the 2024 release wave 2 and has since been expanded with additional reports.
The app is organized around roles:
- Leadership: current and historical work center utilization, to see how efficiently the plant is running.
- Manufacturing managers: finished production order breakdowns, average production times and allocated hours, to keep orders on time and within budget.
- Supervisors: live utilization and work center load views, to spot bottlenecks during the shift.
Beyond utilization, the app covers:
- Machine center load
- Expected capacity need
- Consumption variance and capacity variance
- Production scrap
- Released production orders
- Production order work-in-progress valuation
- A routing Gantt view for sequencing operations
The app also handles subcontracting thoughtfully. Subcontracted costs are included by default, and each report page has a filter to exclude them or isolate them.
For most Business Central manufacturers, this app is the right starting point. Install it, validate the numbers against your standard ERP reports, and document where it falls short. The gaps you find become the brief for any custom development.
Dynamics 365 Supply Chain Management
Enterprise manufacturers running Dynamics 365 Supply Chain Management encounter Power BI differently. Here, analytics are largely embedded in operational workspaces built on Power BI Embedded, so reports appear in context within production control, procurement and inventory areas.
On the supply side, for example, SCM includes:
- An integrated risk and performance report
- Embedded supplier performance analysis in the Supply risk assessment workspace
- Embedded risk assessment analysis in the same workspace
These embedded reports provide a useful operational baseline. Larger manufacturers almost always need more than that: a governed, cross-plant semantic model that combines production data with finance, sales and external sources. Building that model depends on the connection method you choose.
How Do You Connect Power BI to Dynamics 365?
There are four main ways to get Dynamics 365 data into Power BI. The right choice depends on data volume, how fresh the data needs to be, and whether you need to combine ERP data with sources such as manufacturing execution systems (MES), IoT sensors or CRM.
1. Business Central connector and APIs. This is the most direct route for Business Central tenants. It works well for departmental dashboards and moderate data volumes. As transaction volumes grow, performance needs careful attention.
2. OData feeds (Finance and Supply Chain Management). OData provides near-real-time access through public data entities, which suits lightweight, interactive reporting. The limitation is scope: you can only reach what is exposed through the data entity framework.
3. Bring Your Own Database (BYOD). BYOD exports entity data to a separate SQL database for reporting. Many established F&O estates still rely on it, but it adds infrastructure to manage and is being superseded by Fabric-based patterns.
4. Microsoft Fabric Link. This is the direction Microsoft is clearly heading. Link to Fabric makes Dynamics 365 data, including finance and operations apps, available in OneLake through shortcuts, so the data stays in Dataverse without custom ETL pipelines.
Compared with OData and BYOD, Fabric Link also gives access to the underlying application tables rather than only data entities. It syncs in near real time with minimal impact on the live ERP environment. Business Central is moving the same way: Microsoft now documents Fabric as a supported way to analyze Business Central data, alongside Power BI apps and APIs.
For manufacturers who want to combine ERP transactions with machine telemetry, quality systems or multi-entity history, Fabric is usually the right foundation. Folio3's Microsoft Fabric services focus on exactly this kind of architecture.
Which Manufacturing KPIs Should a Power BI Dashboard Track?
A manufacturing dashboard is only as credible as its definitions. Every KPI should map to a clear data source in Dynamics 365 and have a named owner. Most manufacturers should start with three groups.
Capacity and throughput
- Capacity utilization shows how fully work centers and machine centers are used. It comes from capacity ledger entries and routing data.
- Schedule adherence compares production order due dates with actual finish dates. It is the earliest warning sign of delivery risk.
- Average production time by item feeds directly into more realistic planning.
Cost and waste
- Scrap rate by item, production order and work center shows where waste is happening.
- Consumption variance compares the material actually used with what the bill of materials expected.
- Capacity variance compares actual run and setup time with the routing standard.
- Production cost variance compares actual cost with standard or expected cost. Finance teams care about this most at period close.
- Work-in-progress value shows how much capital is tied up on the shop floor.
Customer and supply performance
- On-time in-full (OTIF) measures whether customer commitments are met.
- Supplier performance measures whether inbound materials arrive when production needs them.
These two metrics connect the plant to the rest of the business, and they are often where executive attention lands first.
A note on OEE
Overall Equipment Effectiveness (OEE) deserves special mention because it is the most requested manufacturing metric and the most frequently misrepresented. OEE combines availability, performance and quality:
- Dynamics 365 can supply planned production time, output quantities and scrap, which cover performance and quality reasonably well.
- True availability means actual machine downtime by cause, captured at short intervals. That rarely lives in an ERP. It usually comes from MES, PLC or IoT sources.
Any claim of complete OEE "straight out of the ERP" deserves scrutiny. A credible OEE dashboard combines ERP and machine data, which is one of the strongest practical arguments for a Fabric-based analytics model.
How Should Manufacturing Dashboards Be Designed by Role?
The most common reason manufacturing BI projects fail isn't technical. It's the attempt to build one dashboard for everyone. A better approach is to design around the decisions each role makes and how often they make them.
Executives (COO, CFO). They need a weekly view of plant-level margin, OTIF, cost variance trends and the capacity outlook for the coming months, with drill-through into individual plants when something looks wrong.
Plant and operations managers. They work on a daily cycle. They need utilization, schedule adherence, bottleneck work centers and WIP in one place.
Production supervisors. They need something close to real time: current utilization, released orders, scrap by shift and allocated hours. These views work best embedded in Dynamics 365 or displayed on the shop floor, not in a separate portal.
Finance and cost accountants. They need consumption, capacity and cost variances by item and order, aligned with the period-close calendar.
Supply chain and procurement. They need supplier performance, material shortages against released production orders, and inventory coverage.
A six-step roadmap for Power BI and Dynamics 365 in manufacturing
Manufacturers that succeed with BI tend to follow a similar sequence.
1. Start from decisions, not tables. List the 10 to 15 decisions leadership and plant teams make every week, then work backward to the KPIs and data those decisions need.
2. Deploy what Microsoft already provides. Install the Business Central Manufacturing app or enable the embedded SCM workspaces, validate them against your data, and record where they fall short.
3. Choose the connection pattern. Use APIs and OData for departmental scope. Move to Fabric Link when you need full tables, longer history or data from outside the ERP.
4. Build a governed semantic model. Define each KPI once (scrap rate, utilization, OTIF and the rest) so every report uses the same logic and every number reconciles with the ERP.
5. Design role-based dashboards and embed them where people already work, especially for supervisors on the floor.
6. Operationalize. Set refresh schedules, apply row-level security by plant, add data-quality alerts, and assign a named owner to each KPI.
Teams that want to shorten this timeline often bring in an experienced partner. Folio3's Power BI consulting and implementation services include a packaged Manufacturing Analytics suite. It brings ERP, warehouse, CRM and IoT data together into a single source of truth.
Common Pitfalls to Avoid
Treating BI as a report backlog. Dashboards built one ticket at a time accumulate into hundreds of disconnected reports with conflicting definitions. A semantic model built around agreed KPIs prevents that drift.
Skipping reconciliation. If the scrap figure in Power BI doesn't match the scrap figure in Dynamics 365, plant managers will stop trusting both. Reconcile before you roll out.
Overlooking posting discipline. Utilization and variance KPIs are only as accurate as the output and capacity postings recorded on the floor. BI often exposes data-entry gaps, and those need operational fixes, not only technical ones.
Underestimating licensing at scale. A pilot that runs comfortably on a few Pro licenses can become expensive when it expands to every supervisor across several plants. Plan the licensing model before the rollout, not after.
What About Process, Food and Agricultural Manufacturers?
Process manufacturers face analytical requirements that discrete-manufacturing content tends to overlook:
- Batch and lot genealogy
- Yield by input lot
- Quality holds
- Variability in raw materials from growers and suppliers
In these environments, better analytics depends on capturing the right data at the source. A shop-floor production tracking app that records each run from raw intake to finished goods gives Power BI accurate yield and throughput data. A lot-level quality control app that ties inspection results to specific lots lets quality KPIs be traced back to their inputs, turning dashboards from descriptive into diagnostic.
Turn Your Dynamics 365 Data into Production Decisions
Power BI and Dynamics 365 give manufacturers everything needed for strong production analytics. Results depend on the architecture, the KPI definitions and the discipline of the rollout.
Folio3 is a Microsoft Solutions Partner with more than 20 years of Dynamics delivery experience. We help manufacturers design and implement BI reporting on Business Central and Supply Chain Management, from a first Manufacturing app deployment to enterprise analytics models built on Microsoft Fabric.
Book a free one-hour Power BI reporting consultation to review your current reporting and leave with a clear roadmap for your implementation.
Frequently Asked Questions
Does Dynamics 365 Business Central include Power BI reports for manufacturing?
Yes. Business Central has a Manufacturing Power BI app, generally available since the 2024 release wave 2. It covers work center utilization, capacity load, consumption and capacity variance, scrap, production times and work-in-progress.
Can Power BI show real-time production data from Dynamics 365?
Near-real-time reporting is achievable through API and OData connections or through Microsoft Fabric Link. True real-time machine data, such as live downtime, usually comes from MES or IoT systems combined with ERP data in Fabric.
What is the best way to connect Power BI to Dynamics 365 Supply Chain Management?
For enterprise-scale analytics, Microsoft Fabric Link is the recommended pattern because it gives access to full application tables with near-real-time synchronization. OData remains useful for lighter reporting but is limited to exposed data entities.
Can Power BI calculate OEE from Dynamics 365 data?
Partially. Dynamics 365 supplies planned time, output and scrap, but accurate availability data usually comes from MES, PLC or IoT systems. A complete OEE dashboard combines ERP and machine data.
Does every plant user need a Power BI Pro license?
Not necessarily. On Microsoft Fabric capacity at F64 or above, users with a free license and a viewer role can view Power BI content. Report authors still need paid licenses.