diff --git a/integration-overview.md b/integration-overview.md
index 240eff7150664..67dc1f5d10ff4 100644
--- a/integration-overview.md
+++ b/integration-overview.md
@@ -13,4 +13,10 @@ You can use TiCDC to replicate incremental data from TiDB to Confluent Cloud, an
 
 ## Integrate with Apache Kafka and Apache Flink
 
-You can use TiCDC to replicate incremental data from TiDB to Apache Kafka, and consume the data using Apache Flink. For details, see [Integrate with Apache Kafka and Apache Flink](/replicate-data-to-kafka.md).
\ No newline at end of file
+You can use TiCDC to replicate incremental data from TiDB to Apache Kafka, and consume the data using Apache Flink. For details, see [Integrate with Apache Kafka and Apache Flink](/replicate-data-to-kafka.md).
+
+## Integrate with Microsoft Fabric
+
+You can use TiCDC to replicate incremental data from TiDB to Microsoft Fabric. With [open mirroring](https://learn.microsoft.com/en-us/fabric/mirroring/open-mirroring), TiCDC writes change data directly to a mirrored database in Fabric. This enables continuous, near real-time data replication from any TiDB deployment to Microsoft Fabric OneLake, making your data readily available for AI and analytics workloads.
+
+For details, see this blog post [How to Replicate TiDB to a Mirrored Database in Microsoft Fabric with TiCDC](https://www.pingcap.com/blog/replicate-tidb-mirrored-database-microsoft-fabric-ticdc/).