Dynamics 365 Sales reports on itself well: system and personal dashboards, charts on every view, the sales pipeline funnel, activity summaries, and (on the higher licences) forecasting with quota tracking. Because the data lives in Dataverse, Power BI connects to it through the native Dataverse connector with no third-party subscription, and Power BI reports can be embedded back into Dynamics dashboards so sales users never leave the CRM. That makes it the easiest CRM in the Microsoft stack to report on. The things to know before you start: every viewer of an embedded Power BI report needs a Power BI Pro licence (or the workspace on capacity), the Dataverse connector reads current state so pipeline history needs the audit log or stored snapshots, and joining sales to your accounts system needs a shared customer key, which Dynamics doesn't create for you unless Business Central is integrated.
What does Dynamics 365 Sales report on its own?
- Dashboards. System dashboards ship with the app (sales activity, pipeline, performance); users build personal ones from charts and views. Good enough for a sales team's daily use.
- Charts on views. Any list (opportunities, leads, accounts) can show a chart beside it, filtered with the list. This covers "open opportunities by stage for my team" without any setup.
- Forecasting. On Sales Enterprise and above: forecast by territory or owner against quota, with adjustments and snapshots. If you have the licence, use it before building a forecast elsewhere.
- Sales Insights / Copilot features. Relationship analytics, who-knows-whom, deal health scores, on the premium tiers.
- Advanced Find and views. Ad hoc questions answered by filtering and exporting.
- Reports (SSRS). The older reporting layer: a set of standard reports and the ability to build more with the report authoring extension. Still there; mostly superseded by Power BI for anything new.
For a sales team asking sales questions inside Dynamics, that's complete.
How does Power BI connect to Dynamics 365 Sales?
Through Dataverse, which is the database Dynamics 365 Sales runs on. In Power BI Desktop: Get Data, Dataverse, sign in with a user who has read access, pick the tables (account, contact, lead, opportunity, and the activity tables). There's no connector to buy and no gateway needed; it's cloud to cloud.
Two modes: Import (Power BI copies the data on a refresh schedule, up to eight times a day in a Pro workspace) or DirectQuery (Power BI queries Dataverse live, with the row and performance limits that implies). For sales reporting, import is almost always right.
Then embedding: a Power BI report or tile can be added to a Dynamics 365 Sales dashboard, or as a system dashboard, so users see it inside the CRM. This is the nice part of the Microsoft stack. The catch is licensing, below.
If you also run Business Central with the Dynamics 365 Sales integration, customers and orders sync between them, and the shared IDs make the CRM-to-accounts join much easier than it is with any other pairing.
The licence facts that catch people out
| Item | What it costs / needs | Source |
|---|---|---|
| Dataverse connector in Power BI | No extra cost; needs a Dynamics user with read access | Microsoft Learn, Dataverse connector docs |
| Power BI Pro (author and view in a Pro workspace) | £10.80 per user per month, paid yearly, excl VAT | Microsoft UK Power BI pricing page, September 2026 |
| Power BI Premium Per User | £18.50 per user per month | Same page |
| Viewing an embedded Power BI report inside Dynamics | Every viewer needs Pro, PPU, or the workspace on Fabric/Premium capacity; a Dynamics licence alone isn't enough | Microsoft licensing guidance and Dynamics community answers, read 21 September 2026 |
| Forecasting in Dynamics | Sales Enterprise or Premium licence | Dynamics 365 Sales licensing guide |
| Scheduled refresh | 8/day in a Pro workspace; 48/day on capacity | Power BI documentation |
The one that surprises people: putting a Power BI report on a Dynamics dashboard doesn't make it free to view. Twenty sales users looking at an embedded Power BI page is twenty Pro licences, or a capacity. Budget for it before embedding.
When do you need a custom model?
The built-in dashboards and the Dataverse connector get you a long way. A custom model earns its place in the same three situations as every other system:
History. The Dataverse connector reads what's in the tables now. "What did the pipeline look like on the first of each month" needs either the audit log (which can be switched on for opportunity fields and read for stage and close-date changes) or a scheduled snapshot into a table the model reads. Slippage and stage age, the two numbers that stop a forecast flattering you (see Sales Pipeline Report), both need this.
The join to the accounts. Won opportunities against invoices, margin and cash. Unless Business Central is integrated, Dynamics has no accounts data, and the join needs a customer key both systems hold. That's the sixth question in CRM Reporting, and it's the one the MD asks.
Definitions and audience. Your stage probabilities set from measured win rate rather than the defaults; a weighted pipeline your finance director agrees with; one page per manager with row-level security; a report read on a phone by a board member who'll never open Dynamics.
What does it cost, and where do you start?
Start with the built-in dashboards and the forecasting feature if your licence has it. Then connect Power BI through Dataverse and build the one report the built-in dashboards can't: usually the pipeline page with slippage and stage age, or the manager's page.
That single-source report is what the First Report is for: one system, one report answering one written question, the headline figure reconciled back to Dynamics to the penny, published to your workspace, embedded in Dynamics if you want, £1,950 fixed, ten working days. Dynamics 365 Sales is one of the named systems at the First Report. Dynamics plus your accounts (without the Business Central integration) is two sources and a Reporting Sprint.
Common questions
Does Dynamics 365 Sales have built-in reporting?
Yes: system and personal dashboards, charts on every view, forecasting on the Enterprise and Premium licences, Sales Insights on the premium tiers, and the older SSRS report layer. For a sales team's own questions it's usually enough.
How does Power BI connect to Dynamics 365 Sales?
Through the native Dataverse connector, cloud to cloud, with a Dynamics user that has read access. No third-party connector or gateway is needed. Import mode with scheduled refresh is the usual choice.
Do Dynamics users need a Power BI licence to see embedded reports?
Yes. A Power BI report embedded in a Dynamics dashboard is still served by Power BI, so every viewer needs Pro (£10.80 per user per month on Microsoft's UK page as of September 2026), Premium Per User, or the workspace on Fabric or Premium capacity.
Can Power BI show pipeline history from Dynamics?
Only if the history is captured: switch on auditing for the opportunity fields you care about (stage, close date, amount) and read the audit history, or store scheduled snapshots of open opportunities. The Dataverse tables themselves hold the current state.
Can I report on Dynamics 365 Sales and Business Central together?
Yes, and it's the easiest CRM-to-accounts join there is if the standard integration is set up, because customers and orders carry shared IDs. Without the integration, you need a customer key held in both systems.
Is DirectQuery or Import better for Dynamics data?
Import, for almost all sales reporting. It's faster for users, supports the full modelling features, and eight refreshes a day is plenty for pipeline data. DirectQuery is for the rare case where the numbers must be live to the minute.
What should the first Power BI report on Dynamics be?
The pipeline page the built-in dashboards can't do: weighted pipeline against target, coverage, slippage this month, and stuck deals by stage age, with each manager seeing their own team. It's one system, one question, and it changes the pipeline meeting within a fortnight.