Forum Discussion
Post ProdigyOpen mirroring versus Dynamics 365 CRM
Hi,
is it possible to implement an open mirroring to read/get data from a Dynamics 365 CRM solution?
Many thanks
Hello pmscorca,
Thank you for the clarification.Open Mirroring in Microsoft Fabric is designed to ingest data by allowing applications or external data providers to write change data directly into a mirrored database in OneLake, typically in supported formats such as Parquet or Delta. It relies on sources that can expose or produce this type of change data feed.
In the case of Dynamics 365 CRM (Dataverse), the data is managed within a platform-controlled service layer, and it does not expose its data as a direct change data stream or allow writing into the Open Mirroring landing zone. Because of this architectural limitation, Open Mirroring cannot be used as a direct alternative to Dataverse Mirroring or Fabric Link.
To work with Dynamics 365 / Dataverse data in Fabric, the supported approaches remain Dataverse integration methods such as Fabric Link or Synapse Link–based experiences, which are specifically designed to expose Dataverse data for analytics scenarios.
Thanks, Tamanchu for sharingf valuable insights.
4 Replies
- Tamanchu
Super User
Hi pmscorca,
As far as I know today, not directly through Open Mirroring itself.
Open Mirroring in Fabric is currently designed more for supported mirrored database scenarios and external databases exposing compatible replication/change feeds, rather than directly mirroring a Dynamics 365 CRM application layer natively.
For Dynamics 365 CRM / Dataverse data, the usual Microsoft-supported approaches today are more along the lines of :
- Dataverse integration with Fabric
- Fabric Link / OneLake exposure
- Synapse Link–style integration paths
- Lakehouse ingestion
- SQL endpoint consumption
- Notebooks / semantic models
rather than "Open Mirroring" in the strict sense.
So technically, you can absolutely bring Dynamics 365 CRM data into Fabric and work with it very efficiently there.
But the ingestion/integration mechanism is usually not the same as the newer Open Mirroring architecture.I think the confusion comes from the fact that Dynamics 365 CRM sits on top of Dataverse and Microsoft is progressively converging Dataverse + Fabric experiences, while Open Mirroring is evolving in parallel as another ingestion/replication capability.
So the ecosystems are getting closer, but they are not fully the same thing yet.
Useful references:
- https://learn.microsoft.com/en-us/fabric/mirroring/overview
- https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-view-in-fabric
- https://learn.microsoft.com/en-us/fabric/mirroring/open-mirroring
- https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-overview
Hope this helps clarify the distinction a bit.
The Dataverse / Dynamics / Mirroring landscape is evolving pretty fast right now, so I would expect these integration experiences to continue getting closer over time. 
v-ssriganeshCommunity Support
Hi pmscorca,
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to Tamanchu for sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.
Thank you for being part of the Microsoft Fabric Community.
pmscorcaHi,
I've opened this post to ask about using Open Mirroring versus Dynamics 365 CRM, having Dataverse as a storage; I'm not talking about the expensive Link to Fabric feature in Dataverse or the expected Dataverse Mirroring in Fabric.
I'm searching a valid alternative in Fabric to Dataverse Mirroring and I've thought to Open Mirroring: why is it not possible to use this feature?Thanks
- v-ssriganesh
Hello pmscorca,
Thank you for the clarification.Open Mirroring in Microsoft Fabric is designed to ingest data by allowing applications or external data providers to write change data directly into a mirrored database in OneLake, typically in supported formats such as Parquet or Delta. It relies on sources that can expose or produce this type of change data feed.
In the case of Dynamics 365 CRM (Dataverse), the data is managed within a platform-controlled service layer, and it does not expose its data as a direct change data stream or allow writing into the Open Mirroring landing zone. Because of this architectural limitation, Open Mirroring cannot be used as a direct alternative to Dataverse Mirroring or Fabric Link.
To work with Dynamics 365 / Dataverse data in Fabric, the supported approaches remain Dataverse integration methods such as Fabric Link or Synapse Link–based experiences, which are specifically designed to expose Dataverse data for analytics scenarios.
Thanks, Tamanchu for sharingf valuable insights.
