Problem Statement
Today, Microsoft Dataverse does not support first‑class incremental or CDC‑based ingestion when used as a source in Microsoft Fabric Copy Data / Data Factory Pipelines / CRM Dynamics.
Customers are forced to rely on:
- Full reloads
- Custom watermark logic
- Fabric Link as a workaround (when available)
This creates operational risk, unnecessary load on Dataverse, and limits enterprise adoption of Fabric as the analytics platform for Dataverse‑backed systems (Dynamics 365, Power Platform).
Why This Is a Gap
Dataverse is a core Microsoft operational data platform, yet Fabric currently treats it as a basic extract source, unlike Azure SQL, SQL Server, or other CDC‑enabled systems.
Key limitations today:
- No native change tracking / CDC toggle in Copy Data for Dataverse
- No built‑in handling of inserts, updates, and deletes
- No standardized way to maintain incremental sync state
- Inconsistent architectures across customers (watermarks, custom APIs, Fabric Link dependency)
This is misaligned with Fabric’s stated goal of being the single analytics platform for Microsoft‑first data estates.
Proposal / Requested Capability
Introduce native incremental + CDC‑style support for Dataverse within Fabric Copy Data and Pipelines, comparable to SQL‑based sources.
