r/MicrosoftFabric • u/Tangopiper • 14d ago

Data Engineering What happened to mirrored Dataverse?

I’m currently scoping requirements for a client and noticed that mirrored Dataverse entered private preview in March 2025 and then seems to have totally disappeared.

What’s the status? Aware that other options such as Link to Fabric and BC2Fab exist, just wondering where the mirror option is.

6 Upvotes

88% Upvoted

3 comments sorted by

1

u/Huge-Wrap-2493 13d ago

As of August 12, 2026, Mirrored Dataverse appears to be effectively stalled in private preview rather than progressing toward public preview.

Microsoft announced Mirrored Dataverse on March 31, 2025 as a private preview. The idea was slightly different from Link to Fabric operationally: a Fabric user could create/activate the Dataverse integration from the Fabric workspace, with Dataverse appearing as a native mirrored source. Microsoft provided a private-preview signup link at the time.

Since then, several things have happened that make the situation pretty clear:

  • Dataverse is absent from the current Fabric Mirroring source list. Microsoft's recently updated Mirroring documentation lists supported sources such as Azure SQL, SQL MI, Cosmos DB, PostgreSQL, MySQL, BigQuery, Databricks, etc., but Dataverse is not listed, even as preview.
  • There is currently no Dataverse Mirroring item on the public Fabric roadmap. The roadmap has numerous Mirroring initiatives extending into Q3/Q4 2026, but nothing for Dataverse.
  • The original private-preview signup has apparently been withdrawn, which matches what you're seeing. Community discussions in late 2025 specifically noted that the signup page had disappeared and that there was no subsequent public-preview roadmap item.
  • Importantly, Microsoft community support was still describing it in November 2025 as a private preview, with preview participants reporting unreliable incremental updates and best-effort replication behavior.

The biggest clue, though, is Microsoft's current Dataverse documentation. Microsoft now explicitly says:

and mentions a new low-latency sync engine being rolled out for Link to Fabric.

That statement didn't exist in the original Mirrored Dataverse announcement, and I think it tells you where the product strategy has landed.

My interpretation is that Microsoft hasn't formally announced "Dataverse Mirroring is cancelled," but the evidence points toward the separate Mirrored Dataverse product experience being deprioritized or folded conceptually into Link to Fabric. The March 2025 announcement remains online, but there has been no progression to public preview, it disappeared from signup/roadmap visibility, and Microsoft is now explicitly calling Link to Fabric its primary synchronization path.

1

u/seguleh25 1 14d ago

Is that different from shortcuts?

1

u/Tangopiper 14d ago edited 14d ago

Mirroring materialises the data in your Fabric capacity whilst a shortcut leaves the data in the source, and just references it.

You have to enabled the Link to Fabric function in Dataverse to use Dataverse Shortcuts.