Edit

Share via


Extended capabilities in mirroring for Fabric

Note

Billing for extended capabilities starts on April 1, 2026. UX support for enabling CDF or views is also available starting on April 1, 2026. In the meantime, you can enable or disable extended capabilities via APIs.

Extended capabilities in mirroring for Microsoft Fabric are optional, paid features that build on the core mirroring experience. While core mirroring keeps operational data continuously available in OneLake at no cost for compute, extended capabilities provide more granular change tracking, fresher data, and richer replication options for advanced analytics scenarios.

Today, extended capabilities include:

  • Delta change data feed: Tracks row-level inserts, updates, and deletes so only changed data is processed.
  • Mirroring views: Replicates logical views from the source system instead of only physical tables.

Both capabilities run on the same managed mirroring foundation: secure source connectivity, near real-time replication, Delta Lake storage in OneLake, and seamless use across Fabric workloads like SQL analytics, Spark, and Direct Lake.

What's included by default vs. extended capabilities

Core mirroring (free compute and storage) Extended capabilities (paid)
Continuous replication of source tables into OneLake with near real-time freshness, Delta Lake format, and Fabric integration. Optional features like Delta change data feed and Mirroring views that add incremental change processing and view replication on top of core mirroring.

Delta change data feed (preview)

Delta change data feedcaptures inserts, updates, and deletes, then applies them to Delta Lake tables in OneLake. This flow supports near real-time analytics without full reloads or heavy ETL pipelines.

  • Continuously processes incremental changes (delta-based).
  • Uses change-only processing.
  • Supports downstream incremental processing.
  • Is available for all mirroring sources, including open mirroring partners.

Enable delta change data feed via UX

Delta change data feed is enabled per mirrored database.

  1. For any mirrored source, select the gear icon to open the configuration dashboard.
  2. Under Delta table management, select the check box to Enable delta change data feed.

Screenshot of the Oracle Database mirroring configuration dashboard showing delta change data feed settings, OneLake data access options, and replication status.

Enable delta change data feed via APIs

To enable delta change data feed using APIs, follow the steps outlined in the mirrored database REST API documentation.

Mirroring views (preview)

Mirroring views replicate logical views from your source system instead of full physical tables. You can bring source filters, joins, and transformations into OneLake without building separate engineering pipelines.

  • Replicates view logic from the source system.
  • Reduces extra processing in Fabric.
  • Helps downstream users query shaped data.

Note

Currently, views are only supported in preview in mirroring for Snowflake.

Enable views

You can enable views two ways:

  • During the creation experience for a new mirrored database.
  • For an existing mirrored database, through the configuration dashboard on the mirroring monitoring page.

Once you establish a connection to your Snowflake database, you see Views as part of the table selection screen. (In this example, we're enabling views for a Snowflake source by selecting them.)

Screenshot of the Snowflake mirroring configuration dashboard showing the option to select (and therefore enable) views.

After you select the views that you want to replicate, a dialog box appears asking you to agree enabling extended capabilities, and billing charges, before you proceed.

Screenshot of the extended capabilities in mirroring dialog to enable extended capabilities and acknowledge billing implications.

Pricing for extended capabilities

Note

Billing for extended capabilities starts on April 1, 2026. UX support for enabling CDF or views is also available starting on April 1, 2026. In the meantime, you can enable or disable extended capabilities via APIs.

Features like delta change data feed and mirroring views require extra compute to continuously track, process, and apply incremental changes at fine granularity. These capabilities go beyond basic replication and are priced based on the actual work performed, so customers pay only for the added value they use.

For the pricing model, metering details, and billing scope, see pricing for extended capabilities in mirroring.

When to use extended capabilities

Extended capabilities are useful when you need:

  • Row-level change visibility.
  • Near real-time freshness.
  • Incremental (change-only) data processing.
  • Replication of source view logic.
  • Low-latency analytics on operational systems.

These scenarios often benefit from delta change data feed and mirroring views because both features reduce full refreshes and complex ETL workflows.