HI Team
I would like to propose a feature request for Microsoft Fabric: Outbound Mirroring (Reverse Mirroring) from a Fabric Warehouse to external targets, specifically SQL Server.
Currently, Fabric Mirroring is a fantastic inbound feature that replicates data from external sources (like SQL Server, Azure SQL, and Snowflake) into OneLake. However, there is no native, low-latency way to mirror data out of a Fabric Warehouse back into an operational SQL Server instance.
Why this is needed:
While Fabric excels as a centralized analytical lakehouse, many organizations still rely on traditional SQL Server databases to power operational systems, legacy applications, and real-time transactional workflows. When analytical insights or aggregated data are generated inside a Fabric Warehouse, getting that data back into an operational SQL Server requires building and maintaining manual Data Factory pipelines, Dataflows, or custom PySpark notebooks.
Proposed Solution:
Introduce an outbound mirroring capability. This would allow users to select a Fabric Warehouse table (or view) and automatically stream or replicate changes down to a designated on-premises or cloud-based SQL Server instance with minimal configuration and latency.
I believe this would bridge the gap between operational databases and Fabric's analytical environment, making Fabric an even more flexible centerpiece for hybrid data architectures.
I would love to hear thoughts from the community or if others face similar architecture challenges!
