Forum Discussion
Post ProdigyMirrored Dataverse in Fabric
Hi pmscorca,
Interesting question honestly, because the Dataverse + Fabric integration story is getting richer very quickly… but also a bit confusing sometimes with all the different concepts around, Fabric Link, Mirroring, OneLake exposure, Shortcuts, SQL endpoints Lakehouses.
As far as I know today, there is not yet a dedicated native Fabric item whose only purpose is something like "browse/query mirrored Dataverse storage directly" in the same way you might expect a standalone connector or explorer experience. That said, Fabric can absolutely consume Dataverse data natively today through different integration paths, depending on the architecture and setup.In practice, the two main paths are :
- Fabric Link (via Azure Synapse Link for Dataverse), the most stable and production-ready option today, exposes Dataverse tables as Delta tables in a Lakehouse.
- Dataverse Mirroring, currently in preview, more native Fabric experience but still evolving.
From there, Dataverse data is usually consumed through Lakehouse tables, SQL analytics endpoints, shortcuts, notebooks, or semantic models rather than through a separate dedicated "Dataverse mirrored reader" item.
So I think your idea actually makes a lot of sense
A more explicit/native experience for exploring and governing mirrored Dataverse data inside Fabric would probably make things much clearer for many users. Right now, the ecosystem is evolving pretty fast, and Microsoft seems to be progressively converging operational and analytical workloads into the same platform experience.Useful references:
- 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/overview
- https://learn.microsoft.com/en-us/fabric/onelake/onelake-shortcuts
- https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-overview
- https://learn.microsoft.com/en-us/power-apps/maker/data-platform/fabric-link-faq
Hope this helps clarify the current landscape a little bit
And honestly, I would not be surprised if Microsoft expands the native Dataverse/Fabric experience further over time.
Community SupportHi pmscorca,
As an alternative approach, you can consider using Dataflows Gen2, Pipelines, notebooks to move only the required Dataverse tables/data into OneLake.
This can provide more control over the amount of data being ingested and stored.
For roadmap or future feature visibility, you can also monitor:
https://roadmap.fabric.microsoft.com/
And if a more storage-efficient native Dataverse integration in Fabric is important for your scenario, submitting an idea in the Ideas Forum may help increase visibility for the request:
https://ideas.fabric.microsoft.com/
Thank you.
Post ProdigyHi, I don't think it's necessary to create an idea: Microsoft is working on Dataverse Mirroring as a Fabric feature.
Instead, could you push for this feature to be released as soon as possible? Thanks
- v-abhinavmu
Hi pmscorca,
Thank you for your feedback and suggestion. As this is a community forum, we encourage users to submit feature ideas through the Ideas portal. Features that receive higher customer interest and votes are often prioritized for earlier consideration.
That said, feature planning is also based on overall customer requirements, business necessity, technical feasibility, and dependencies across multiple teams within the Fabric. The requested capability is being considered, and similar enhancements may become available in the future. However, at this time, we are unable to provide an ETA due to the various dependencies involved in feature development and release planning.
Thank you!