Business Central 2026: Power BI, Copilot & Real Costs
Every Business Central customer now has Power BI apps and Copilot sitting inside the product at no extra license cost. Few of them are using either one in a way that changes how decisions get made. That gap, between what shipped and what gets adopted, is the real story behind Microsoft's 2026 release wave 1, and it is worth understanding before your organization spends a single hour configuring anything.
Why This Matters Right Now
Microsoft's 2026 release wave 1 for Business Central, rolling out from April through September 2026, embedded four Power BI apps directly into the product, expanded the set of read-only APIs available to external reporting tools, and pushed Copilot further into transactional work such as sales order suggestions, bank reconciliation, and payables matching. Two of the more concrete additions were an enhanced Subscription Billing Power BI app and an enhanced Manufacturing Power BI app with subcontracting analysis, alongside new APIs built for auditors and IT staff to review approval workflows and user permissions.
None of that is marketing language. It is a real shift in how much reporting and automation capability ships with the base product rather than requiring a separate build. Wave 2 follows the same twice-a-year cadence Microsoft has used for several years, with new features generally rolling out from October through March, so organizations that treat wave 1 as a one-time event rather than the first half of an annual cycle will be behind again by winter.
For a Microsoft partner base competing on implementation quality rather than headline features, this is where the differentiation actually lives now. Everyone can point to the same release notes. Few firms can walk a CFO through what changes in their specific chart of accounts, their specific approval matrix, or their specific manufacturing cost structure.
The Decision in Front of You Is Not "Should We Turn This On"
Because the Power BI apps and most Copilot features ship inside the existing license at no additional cost, the temptation is to treat adoption as a switch to flip. That framing causes more failed rollouts than any technical limitation does. The actual decision a finance or operations leader faces is narrower and harder: which of these capabilities changes a decision your team already makes weekly, and which ones just generate another dashboard nobody opens after the first demo.
I have sat in enough post-implementation reviews to know the pattern. A company enables the default Power BI apps, gets excited about the initial visuals, and six months later the finance team is still exporting to Excel because the embedded reports do not reflect their dimension structure, their intercompany eliminations, or their regional VAT and sales tax handling. The tool was never the problem. Nobody mapped the reporting requirement to the feature before switching it on.
What Actually Happens Under the Hood
Two mechanisms explain both the opportunity and the risk here, and most partner-side content skips past them.
Power BI reads a replica, not your live ledger. Since February 2022, Power BI reports for Business Central online have pulled from a secondary, read-only database replica rather than the primary transactional database, a change Microsoft made to protect system performance during heavy reporting use. This is good news for performance and a source of confusion when someone asks why a report does not reflect a posting made ninety seconds ago. If your team is troubleshooting what looks like a sync delay, start here before opening a support ticket.
Copilot inherits the user's existing permissions, nothing more. When a Business Central user interacts with Copilot, it can only see data that user already has access to under their existing security setup. That sounds reassuring, and mostly it is, but it also means your Copilot rollout is only as clean as your permission sets already are. Organizations that have spent years granting broad SUPER or near-SUPER permissions to get people unblocked are about to discover that Copilot will happily surface whatever those permissions expose. Copilot did not create a new security risk. It exposed one that was already there.
The Trade-Off Nobody States Plainly: Included Versus Custom
The four embedded Power BI apps and the standard Copilot capabilities cost nothing beyond your existing Business Central license. The moment you need a custom Power BI report built in Power BI Desktop and published for sharing beyond what the built-in connector supports, you are potentially into Power BI Pro or Premium licensing territory, governed by Power BI's own licensing terms rather than Business Central's. This is a real cost line that gets missed in budget conversations because the word "Power BI" appears to be "already included."
The honest guidance here: confirm your specific reporting requirements against your current Power BI and Business Central licensing agreements before promising stakeholders anything is free. Terms and included entitlements can vary by region and by when your agreement was signed, and licensing guidance in this area changes often enough that a conversation with your Microsoft partner or your Microsoft account team should happen before, not after, you commit to a reporting roadmap. This is general guidance, not a substitute for reviewing your own contract.
What This Looks Like in a Real Rollout
On engagements where the embedded Power BI apps and Copilot actually stuck, three things were consistently true, and they had nothing to do with the software itself.
First, someone owned the semantic model before anyone opened Power BI Desktop. That meant agreeing, in writing, what "gross margin" or "on-time delivery" meant across departments before building a single visual. Skip this step and you get three versions of the same KPI circulating by the second month, each defensible, each different, and each undermining trust in the numbers faster than any technical bug would.
Second, Copilot's productivity features (sales line suggestions, bank reconciliation matching, autofill) were piloted with a single team for two to three weeks before wider rollout, to catch cases where the AI suggestion pattern did not match how that business actually classified transactions. Manufacturing and distribution businesses with unusual costing methods or non-standard chart of accounts structures saw the most mismatches. That is not a knock on Copilot. It is a reminder that AI-assisted suggestions are trained on general patterns and need a human checkpoint until your specific patterns are proven reliable.
Third, the finance team ran the new APIs for approval workflow and permissions auditing before, not after, expanding Copilot access. Those APIs exist so auditors and IT staff can see who can approve what and who has access to what. Running that audit first turns a compliance checkbox into the exact security cleanup that makes Copilot safer to deploy in the first place.
Where This Goes Wrong
The most common mistake is sequencing: enabling Copilot broadly before cleaning up permission sets, then discovering that AI-generated summaries and suggestions are surfacing data across departments that should have been walled off years ago. The second most common mistake is measuring adoption by feature activation rather than decision impact. A dashboard with monthly active users tells you people are looking. It does not tell you anyone changed a purchasing decision, a pricing decision, or a staffing decision because of what they saw.
A subtler mistake, and one worth naming honestly: treating the embedded Power BI apps as a replacement for a proper reporting strategy rather than a starting point. The four apps Microsoft ships cover common ground across finance, sales, supply chain, and subscription billing. They were not built around your specific dimension structure, your specific cost centers, or your specific board reporting format. Businesses that stop at the default apps get generic insight. Businesses that use the default apps as a foundation and extend them where the business genuinely differs get something closer to a real management reporting system.
What We Recommend, in Priority Order
Start with a permissions and approval workflow audit using the new 2026 wave 1 APIs, before expanding Copilot access to any team beyond a pilot group. This is the highest-impact, lowest-cost step available and it directly reduces the risk described above.
Next, assign explicit ownership of your core KPI definitions before any team starts building or consuming Power BI reports beyond the four embedded apps. This is a governance exercise, not a technical one, and it is the single most common gap we see in stalled reporting projects.
Then pilot Copilot's transactional features (sales suggestions, bank reconciliation, payables matching) with one team for two to three weeks, with someone assigned to check suggestion accuracy against your actual transaction patterns before wider rollout.
Finally, before committing to a custom Power BI build beyond the embedded apps, get a written confirmation of your licensing position from your Microsoft partner. Whether you need Power BI Pro, Premium, or nothing beyond your current Business Central entitlement depends on how the reports will be built, shared, and consumed, and that answer is specific to your setup, not a general rule.
What Comes Next
Wave 2 for 2026 will follow the same cadence Microsoft has used for years, with features generally arriving from October through March. Based on the trajectory of wave 1, expect continued investment in agent-based automation for sales and purchasing scenarios, further expansion of the read-only API surface for external reporting and compliance tools, and continued build-out of the embedded Power BI app catalog beyond the four functional areas covered so far. Organizations that used wave 1 to clean up their permission model and clarify their KPI ownership will be positioned to adopt wave 2 features quickly. Organizations that skipped that groundwork will be solving the same governance problem twice.
The Takeaway
The Power BI and Copilot updates in Business Central's 2026 release wave 1 are useful, and free within your existing license for the core capabilities. The value they deliver has almost nothing to do with how quickly you turn them on and almost everything to do with whether your permission model, your KPI definitions, and your rollout sequencing were solid before you did. Treat this release as a prompt to do that groundwork, not as a feature list to activate and move past.
If your team wants a second opinion on where your current Business Central setup stands against these updates, whether that is a permissions and reporting audit or a plan for adopting the embedded Power BI apps and Copilot features properly, that conversation is worth having before your next release wave arrives rather than after. Dynamics Square's Business Central consulting and implementation teams across the US, UK, and Canada run exactly this kind of readiness review, and our Dynamics 365 consulting practice can walk through your specific licensing position with you as part of it. You can also see how the platform itself is structured on our UK Business Central product page.
FAQ
Do I need to pay extra for the new Power BI apps in Business Central?
No. The four embedded Power BI apps introduced in the 2026 release wave 1, covering finance, sales, supply chain, and subscription billing, are included with your existing Business Central license. Custom Power BI reports built and shared beyond what the built-in connector supports may require separate Power BI licensing depending on how they are built and distributed. Confirm this against your specific agreement, since terms vary by region and contract.
Can Copilot in Business Central see data I am not supposed to see?
No. Copilot inherits the data permissions of the user interacting with it and cannot access more than that user's existing security setup already allows. This makes cleaning up overly broad permission sets a prerequisite for a safe Copilot rollout, not an optional follow-up step.
Why does my Power BI report look out of date compared to Business Central?
For Business Central online, Power BI reports are sourced from a secondary, read-only database replica rather than the live transactional database, a design Microsoft introduced in February 2022 to protect system performance. A short lag between a posting and its appearance in a report is expected behavior, not a fault.
When does 2026 release wave 2 arrive?
Microsoft's release waves generally follow an April through September (wave 1) and October through March (wave 2) cadence. Full details for 2026 release wave 2 typically become available closer to the rollout window, with early access opening several weeks ahead of general availability.
What is the biggest mistake companies make when adopting these features?
Turning on Copilot broadly before auditing existing user permissions, and treating the default Power BI apps as a complete reporting strategy rather than a starting point that still needs KPI governance and, in many cases, extension work specific to the business.