Microsoft Fabric and Dynamics 365
How Microsoft Fabric and OneLake change Dynamics 365 analytics — Synapse Link, lakehouses, and the migration from Export to Data Lake.
Microsoft Fabric is Microsoft's unified analytics platform — a single SaaS product covering lakehouse, data warehouse, real-time analytics, data science, and Power BI on top of a shared storage layer called OneLake. For Dynamics 365 customers, Fabric is becoming the destination for analytics that need cross-system data, large historical volumes, or complex transformations beyond what Power BI's own model can handle.
Synapse Link for Dataverse. A managed near-real-time pipe from Dataverse into a Fabric lakehouse (or, historically, a customer-owned Azure Data Lake). When enabled per environment, Dataverse continuously writes Delta-Parquet snapshots of selected tables to OneLake. Downstream Fabric workloads — notebooks, SQL endpoints, Power BI semantic models — read from OneLake without touching Dataverse.
Synapse Link for F&O. The equivalent for Finance and Supply Chain. Data entities or specific tables stream into OneLake. Replaces the older Export to Data Lake feature in F&O and the Bring Your Own Database (BYOD) pattern, both of which Microsoft is deprecating.
Business Central data lake export. Business Central also publishes its data into Fabric via a similar mechanism (still evolving as a generally-available feature). The end state is a single OneLake estate containing CRM (Dataverse), F&O, and BC tables side by side, queryable as one logical data set.
DirectLake. A new Power BI mode that reads parquet directly from OneLake without import or DirectQuery. Performance close to import, no refresh schedules. The right pattern for most Dynamics 365 reporting at scale.
Use cases.
- Cross-system reports. Sales pipeline (Dataverse) joined to finance actuals (F&O) joined to web analytics (Adobe Analytics) — all in one Fabric lakehouse, with one semantic model in Power BI.
- History beyond the source. Dataverse and F&O retain data per their own retention policies; OneLake retention is independent and cheap.
- Data science. Train ML models against the lakehouse rather than hitting the live ERP.
- Real-time analytics. Stream from operational events into Fabric's KQL database for dashboards.
Operational reality. Fabric capacity is sized in F-SKUs (or Power BI Premium capacity). Plan capacity for the actual workload — peak Power BI users, lakehouse compute, semantic model size. Capacity oversubscription is the most common Fabric pain point.
Governance. Microsoft Purview integrates with Fabric for cataloguing, classification, and lineage. Use it from day one if compliance matters.
Where it stops. Highly specialised analytics (statistical forecasting, complex MDX cubes, certain GIS workloads) sometimes still need a separate purpose-built platform. For mainstream BI and data integration on Dynamics 365, Fabric is now the recommended home.
Related guides
- Azure Data Factory with Dynamics 365How to use Azure Data Factory for Dynamics 365 data integration — connectors, common patterns, performance tuning, and when ADF is the right tool vs alternatives.
- Azure Functions for Dynamics 365 integrationsHow to use Azure Functions to extend and integrate Dynamics 365 — patterns, authentication, lifecycle, performance, and the trade-offs vs Power Automate.
- Azure Service Bus integration with DataverseHow Dataverse publishes change events to Azure Service Bus — registration, message format, queues vs topics, and resilient consumer patterns.
- Azure Synapse Link for DataverseHow Synapse Link replicates Dataverse data to Azure Data Lake Storage continuously — architecture, configuration, query patterns, and the path forward as Microsoft Fabric Link emerges.
- Logic Apps Standard vs ConsumptionThe two Logic Apps hosting models — Standard (single-tenant) vs Consumption (multi-tenant) — and how to choose between them for Dynamics 365 integrations.