A CFO asks whether the company should invest in Power BI, and the honest answer is that they're already paying for it — it's embedded in the Business Central license they hold today. What they don't have is anyone who's gone past the default report tiles to actually build something specific to how their business needs to see its own numbers.
This confusion is common, and it runs in a specific, predictable direction: companies either assume Power BI is a separate, expensive add-on they haven't purchased, or they assume the default embedded reports are "Power BI" in the fullest sense and stop looking further. Neither assumption is quite right.
What's Genuinely Native
Business Central includes embedded Power BI reporting directly in the product — pre-built report pages and dashboard tiles pulling live data from your environment, viewable inside Business Central itself without needing a separate Power BI license or license tier upgrade for basic viewing. This native layer covers standard financial and operational summaries reasonably well, and for a company with straightforward reporting needs, it can be genuinely sufficient without further investment.
The distinction worth understanding clearly: native embedded reports are built against Microsoft's own predefined data model and visual layout. They're not something a business user can meaningfully reshape without moving into actual Power BI development — a different skill set and a different tool, even though both carry the same "Power BI" name.
Where Native Reporting Stops
The moment a reporting need goes beyond what Microsoft's predefined report pages show — a custom visual combining data from multiple areas of Business Central in a way the default reports don't anticipate, a dashboard built around metrics specific to your industry, or genuinely interactive drill-down analysis a static tile can't provide — native embedded reporting stops being sufficient, and real Power BI report development, connecting to Business Central data through its published data connector, becomes the actual path forward.
This is a meaningfully different undertaking than viewing a default tile. It requires someone who understands both the underlying Business Central data structure and Power BI's report-building tools — measures, relationships, DAX calculations — to construct something genuinely custom rather than consuming what Microsoft pre-built.
Why This Confusion Persists
Microsoft's own product marketing understandably leans on the fact that Power BI is "included" — which is true for the embedded, native layer, and creates a reasonable expectation that everything under the Power BI name is similarly included and ready to use. In practice, moving from consuming default tiles to building genuinely custom reports crosses into a different kind of work — one that typically does require either a Power BI Pro license for whoever's building and sharing custom reports, and someone with real report-building capability, not just Business Central administration knowledge.
Companies that discover this gap late in the process — after assuming "we already have Power BI" meant custom dashboards were simply a configuration toggle away — tend to be more frustrated by the mismatch in expectation than by the actual cost of building something real.
A Practical Way to Frame the Decision
Before assuming either extreme — that Power BI requires a large new investment, or that it's already fully covered — it's worth mapping your actual reporting gaps against what the native embedded layer genuinely provides. If the default report pages already answer the questions your team asks regularly, there may be nothing further to build. If leadership routinely asks for a specific cross-functional view that no default tile shows, that's a signal real Power BI development work — grounded in a clean underlying data model — is the actual next step, not a settings change inside Business Central.
Where to Start
The most useful first step is usually a short audit: list the specific reports or dashboards your leadership team currently wants but doesn't have, and check each one against what Business Central's native embedded reporting already covers. What's left over after that comparison is the real scope of custom Power BI work — often smaller and more targeted than assumed, once it's separated clearly from what's already sitting in the license unused.