The 4 Power BI + D365 integration patterns
D365 + Power BI integration requires choosing the right data plane pattern, the right semantic model architecture, and the right governance operating model. EPC Group implements all 4 patterns end-to-end.
EPC Group · Power BI + D365 Services · 2026
Dataverse + Microsoft Fabric link + Power BI Direct Lake semantic models on D365 Customer Engagement, D365 Finance & Operations, D365 Customer Insights — pre-built Sales/Finance/Supply Chain/Service accelerator reports, Copilot for Sales + Service grounding, Microsoft Purview governance end-to-end.
Published June 25, 2026 · Updated continuously
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
EPC Group specializes in Power BI + Dynamics 365 integration across 4 architectural patterns: native Dataverse + Microsoft Fabric link replicating D365 Customer Engagement + Finance & Operations data into OneLake Delta Lake with sub-minute latency (recommended 2026 pattern, replaces TDS endpoint + Synapse Link); D365 Customer Insights Data integration for unified customer 360 profile + segments + predictive scores; pre-built accelerator semantic models + Power BI report packs for Finance (P&L + Balance Sheet + Budget Variance), Sales (Pipeline + Forecast + Win/Loss), Supply Chain (Inventory Turns + On-Time Delivery), Service (Case Volume + SLA + CSAT); Power Platform low-code extensions (Power Apps + Power Automate + Power Pages + Copilot Studio) with embedded Power BI inside D365 workflows + Microsoft Purview governance + Conditional Access + PIM. Compliance-native HIPAA + NYDFS Part 500 + SOX + GDPR + BIPA + MHMDA + CCPA. Engagements are fixed-fee, scoped after discovery. Founder Errin O'Connor co-authored Microsoft Press books on Power BI + Microsoft 365.
EPC Group integrates Power BI + Dynamics 365 across 4 patterns: Dataverse + Fabric link (recommended); D365 Customer Insights; pre-built Sales/Finance/Supply Chain/Service accelerators; Power Platform extensions + Microsoft Purview governance. Fixed-fee engagements scoped after discovery. Replaces Synapse Link + TDS endpoint.
D365 + Power BI integration requires choosing the right data plane pattern, the right semantic model architecture, and the right governance operating model. EPC Group implements all 4 patterns end-to-end.
EPC Group implements native Dataverse + Microsoft Fabric link (GA late 2024) — D365 Customer Engagement (Sales, Customer Service, Field Service, Marketing) + Finance & Operations data automatically replicated into Fabric OneLake without ETL pipelines. Delta Lake format ready for Direct Lake semantic models. Sub-minute latency from Dataverse write to Power BI report freshness. Replaces TDS endpoint + Common Data Model folder + Synapse Link patterns. The recommended 2026 architecture for D365-on-Fabric organizations.
Microsoft stack
Dataverse + Microsoft Fabric link + OneLake + Delta Lake + Power BI Direct Lake + D365 Customer Engagement + D365 Finance & Operations
EPC Group integrates D365 Customer Insights Data (formerly Customer Insights – Data) — unified customer profile across Dataverse + external sources + behavioral telemetry. Power BI semantic models read enriched profiles + segments + predictive scores. Combines first-party CRM data + clickstream + service interaction history + financial transactions into single customer 360 view. Marketing automation triggers from segments. Analytics models surface churn risk + LTV + next-best-action recommendations.
Microsoft stack
D365 Customer Insights Data + Power BI semantic models + Dataverse + Microsoft Fabric Data Engineering + Azure ML for predictive scoring
EPC Group ships accelerator semantic models + Power BI report packs for D365 Finance (P&L + Balance Sheet + Cash Flow + Budget Variance + GL Trial Balance), D365 Sales (Pipeline + Win/Loss + Forecast Accuracy + Sales Activity + Quota Attainment), D365 Supply Chain (Inventory Turns + On-Time Delivery + Procurement + Production Variance + Vendor Performance), D365 Service (Case Volume + SLA Performance + CSAT + Field Service Utilization). All semantic models use star schema + RLS + sensitivity labels + Microsoft Purview lineage.
Microsoft stack
Power BI accelerators + D365 Finance + D365 Sales + D365 Supply Chain Management + D365 Customer Service + Power BI Premium / Fabric F-SKU
EPC Group extends D365 + Power BI integration with Power Platform (Power Apps + Power Automate + Power Pages + Copilot Studio) for low-code business apps surfacing Power BI insights inside D365 workflows. Embedded Power BI reports inside D365 model-driven apps + Sales Hub + Customer Service workspace. Microsoft Purview governance + sensitivity labels + DLP policies enforced across the Power Platform + Dataverse + Power BI surface. Quarterly access recertification + lineage validation.
Microsoft stack
Power Apps + Power Automate + Power Pages + Copilot Studio + Embedded Power BI + Microsoft Purview + Microsoft Entra ID PIM
EPC Group chooses the path by what the reports need, not by habit.
Sources: Link to Microsoft Fabric, Dataverse connector, Azure Synapse Link for Dataverse (Microsoft Learn, accessed 2026-11-07).
Power BI Dynamics 365 integration is one part of ERP reporting. As a Power BI ERP reporting partner, EPC Group matches the source to the ERP:
For SAP to Power BI consulting, the decision is usually a live connector for operational reports versus mirroring into OneLake when SAP data has to be combined with other sources.
Sources: Business Central Power BI apps, Business Central and Power BI, SAP HANA connector, SAP BW Application Server, SAP BW Message Server, Fabric mirroring for SAP (Microsoft Learn, accessed 2026-11-07).
The SAP HANA database connector and the SAP BW Application Server and Message Server connectors, all generally available with Import and DirectQuery (version 1.0 of the SAP BW connectors is deprecated; new connections use Implementation 2.0), or Fabric mirroring for SAP, which lands data through an SAP Datasphere replication flow into OneLake with SAP Datasphere outbound pricing (Microsoft Learn, accessed 2026-11-07).
By what the reports need. Link to Microsoft Fabric makes Dynamics 365 and Power Apps data available in OneLake with no ETL pipelines to build; the Dataverse connector serves Import or DirectQuery reports; other line-of-business apps join through a certified connector or a Fabric landing zone, with shared dimensions so every system reports on the same definitions (Microsoft Learn, accessed 2026-11-07).
For new D365 + Power BI architectures in 2026: Dataverse + Microsoft Fabric link is the recommended pattern (GA late 2024). It automatically replicates Dataverse data into Fabric OneLake Delta Lake format with sub-minute latency, no ETL pipelines, and native Power BI Direct Lake compatibility. The older patterns: TDS endpoint (read-only T-SQL against Dataverse) is still useful for SSRS + paginated reports but not recommended for new analytical workloads; Common Data Model folder + Azure Data Lake Gen2 export is being replaced by Fabric link; Azure Synapse Link is being deprecated in favor of Fabric link. EPC Group migrates existing D365 + Synapse Link deployments to Fabric link as part of broader Fabric modernization engagements.
Standard 4-layer architecture: (1) Dataverse + Microsoft Fabric link replicates Sales/Service entities into OneLake; (2) Fabric Data Engineering Spark notebooks transform raw Dataverse tables into business-ready dimensional models (Account dim + Contact dim + Opportunity fact + Activity fact + Case fact + SLA fact); (3) Power BI semantic models on Direct Lake mode read Gold layer Delta tables with calculation groups + reusable metrics + RLS by Business Unit + Territory + Owner; (4) Pre-built EPC Group accelerator reports for Pipeline + Win/Loss + Forecast Accuracy + Sales Activity + Quota Attainment + Case Volume + SLA + CSAT + Field Service. Embedded in D365 Sales Hub + Customer Service workspace via Power BI embedded reports.
D365 F&O has additional complexity vs Customer Engagement because F&O uses Bring Your Own Database (BYOD) export to ADLS Gen2 + Synapse Link to Dataverse + Fabric link patterns. EPC Group typically designs hybrid architecture: F&O entities replicated to Dataverse via Synapse Link for D365, then Dataverse + Fabric link replicates to OneLake. Power BI semantic models include Finance accelerator (P&L by entity + cost center + business unit, Balance Sheet, Cash Flow Statement, Budget Variance, GL Trial Balance, AP/AR Aging), Supply Chain accelerator (Inventory Turns + On-Time Delivery + Procurement + Production Variance + Vendor Performance), Manufacturing accelerator (OEE + Work Order + Production Plan vs Actual). All accelerators tested against ISV common chart of accounts patterns.
Microsoft Purview Data Map automatically discovers + classifies Dataverse entities + columns. Information Protection sensitivity labels propagate from Dataverse → Power BI semantic models → reports → exports → emails. DLP policies enforced across Dataverse + Power BI + Office 365 + Teams + endpoint. Data Lineage tracks data flow Dataverse → Fabric link → Delta tables → Power BI semantic model → Power BI report → export. Compliance Manager pre-built templates for HIPAA + NYDFS + SOX + GDPR + BIPA + MHMDA + CCPA cover the Dataverse + Power BI surface. EPC Group ships the operating model with named roles (Data Steward + Data Owner + Information Security Officer + Privacy Officer).
Microsoft 365 Copilot for Sales reads Dataverse + Customer Insights + Power BI semantic models for next-best-action recommendations + meeting prep + email-thread summarization. Copilot for Service reads case history + KB articles + Customer Insights for case resolution recommendations + CSAT prediction. Copilot Studio extends both with custom topics + actions calling Dataverse + Power BI + external connectors. EPC Group implements Copilot governance through Microsoft Purview sensitivity-label-aware grounding (Copilot will not surface or use content the requesting user lacks rights to see), Conditional Access for Copilot tenant access, Audit Log integration for Copilot prompt monitoring + DLP-style content scanning.
EPC Group D365 + Power BI integration engagements are fixed-fee, quoted after discovery, based on: D365 modules in scope (Sales-only vs full F&O vs Customer Insights); Power BI accelerator count (5 reports vs 50+); data volume + history depth; regulated-industry compliance scope (HIPAA + NYDFS + SOX add 20-40%); ongoing Power BI Premium / Fabric F-SKU capacity sizing (separate operating cost typically $3K-$30K/month). 2-week Discovery + Architecture phase produces fixed-fee scope quote with milestone-based billing.
High-touch, senior-architect-led delivery without junior consultants learning on the engagement. Named EPC senior architect (founder Errin O'Connor co-authored Microsoft Press books on Power BI and SharePoint. 2-week Discovery + Architecture Design (fixed-fee), then 8-24 week Implementation (fixed-fee accelerator with milestone-based billing per module/report pack), then ongoing Microsoft Cloud Orchestrator Practice retainer for continuous architecture optimization + capacity rightsizing + business-hours (Central) incident response.
Reach EPC Group for a one-hour Power BI + Dynamics 365 integration call with a senior architect.
Named engagements come first; anonymized summaries follow under the anonymized-engagement rule — the client is not named and every statement is EPC-reported. Documents behind named engagements are in the Evidence Center.
More engagements: Power BI Tax Reporting on MySQL: Tax Services Firm (2024) · Power BI Ops Dashboard: Transit District (2023) · Power BI Report Server Refresh Fix: Agribusiness (2021) · Power BI, Data Warehouse and External Reports: Gaming (2021) · SAP Reports to Power BI in 90 Days: Aerospace (2021) · Power BI Governance Strategy: Global Insurer (2020) · Power BI on HR System Data: Construction Contractor (2020) · Power BI POC, Governance and Roadmap: Electronics (2020) · Power BI Assessment and Integration: Pharmacy (2019) · Power BI Proof of Concept: Global Technology Company (2019) · Power BI Best-Practice Review and Training: Insurer (2018) · Power BI Analytics Platform: State Government · Power BI Enterprise Deployment: Financial Institution