SQL 2025 Fabric Mirroring

We have setup fabric mirroring in SQL 2025 on top of a replicated subscriber using azure arc, this is just for a proof of concept, the mirroring seems to work but there is a microsoft document

https://learn.microsoft.com/en-us/fabric/mirroring/sql-server-limitations#database-level-limitations

advising CDC and replication is not supported in 2025 for fabric mirroring, We observed with CDC enabled it did not allow fabric mirroring to be configured, but with replication it still allowed, we noticed change feed doesnt seem to work as there was a latecy of atleast 30 secs to mirror data to fabric. Is this something to do with replication being enabled we dont know, we still havent tested a plain database (without replication and/or cdc enabled) Following details are shared to our BI team about the current situation in an email 

Current Observations

When executing the following command on the source database:

EXEC sp_help_change_feed;

the engine returns:

Change Feed or Fabric Link is not enabled on database 'ourdb'.

Additionally:

SELECT [name], is_data_lake_replication_enabled

FROM sys.databases

WHERE [name] = 'ourdb';

returns: 0

Based on these results, the SQL Server 2025 Change Feed engine does not appear to be enabled for the database under test.

Mirroring Behavior

Despite the Change Feed status indicating disabled, data continues to be synchronized successfully to Fabric.

This suggests that Fabric Mirroring is currently obtaining changes through an alternative mechanism rather than through the native SQL Server 2025 Change Feed feature. We also observed an approximate latency of 30 seconds, even for single-row insert or update operations.

Further clarification from Microsoft may be required to determine the exact mechanism being used and whether this behavior is expected when SQL Server Replication is present.

Production Considerations

While the functionality appears to work in a test environment, several questions remain regarding production suitability:

If the native SQL Server 2025 Change Feed engine cannot be enabled alongside replication, it is unclear how Fabric guarantees change retention and recovery during periods of high transaction volume.

Additional validation is required to determine whether transaction log truncation, checkpoints, or backup activity could affect Fabric's ability to capture all changes consistently.

Fabric Mirroring may introduce additional background workload against the source database, resulting in increased read I/O and resource consumption on a server already processing replication activity.

Conclusion

At present, data is successfully reaching Fabric; however, the native SQL Server 2025 Change Feed functionality does not appear to be active.

The key question requiring clarification is whether SQL Server Replication prevents or alters Change Feed operation, and whether the current mirroring behavior is a fully supported production configuration.

Until this is confirmed, we should treat the current implementation as a successful proof of concept rather than confirmation of a supported production architecture.

Next Step: test a plain database with some rapid data insertion mechanism to see if change feed kicks in to push data to fabric at near real time speed.

--Can someone from the community comment on this.