Mirroring provides a modern approach to accessing and ingesting data continuously and seamlessly from any database or data warehouse into the Data Warehousing experience within Microsoft Fabric. Here are the key points about Mirroring:

  1. Near Real-Time Data Access:
    • Mirroring allows users to access changes in the source data almost instantly.
    • It ensures that the data in Fabric’s OneLake remains up-to-date without complex setup or manual intervention.
  2. Unified Data Estate:
    • Fabric aims to be a “unified end-to-end analytics solution.”
    • With Mirroring, you can bring your databases into OneLake, eliminating data silos.
    • No need for cumbersome ETL (Extract, Transform, Load) pipelines.
  3. Continuous Data Replication:
    • Mirroring uses the source database’s Change Data Capture (CDC) technology.
    • It transforms the data into appropriate Delta tables and lands it in OneLake.
    • Data is updated continuously, ensuring that every transaction (insertion, update, deletion) is reflected in near real-time.
  4. Benefits:
    • Zero-ETL: No complex ETL processes required for data replication.
    • Immediate Insights: Users gain immediate access to changes in the source data.
    • Unlocking Warehousing, BI, AI, and More: Mirroring facilitates seamless integration with other analytical engines and tools.

Enabling Mirroring in your tenant:

  1. From the Fabric home page, open the settings, then Admin Portal.
  2. Navigate to Tenant Settings, then to Microsoft Fabric.
  3. Expand Mirroring (preview), enable the Mirroring (preview) 
  4. (Optional) Use the Specific security groups option to enable Mirroring for specific users. You can also use the Except specific security groups option, to enable Mirroring for the tenant, and exclude specific users.
  5. Select Apply.

Screenshot of tenant settings in Microsoft Fabric with Mirroring enabled

Enabling in Cosmos DB:

  1. Sign in to the Azure portal.
  2. Navigate to your Azure Cosmos DB account and open the Backup & Restore Select Backup Policies tab and select on change. Once you choose the target continuous mode, select on Save.


  1. When the migration is in progress, the popup shows Updating Backup polScreenshot of Cosmos DB settings in Microsoft Fabric with Continuous Backup policy enabledicy settings. If you select that notification, you might see Updating on the account level and Migrating for Backup policy on overview of the account.
  2. After it’s complete, the backup policy would have switched to chosen tier of Continuous Migration time depends on the size of data in your account.
  3. For mirroring in Fabric to work, backup policy MUST BE SET TO 7 DAYS OR 31 DAYS.

For further information on how to get connection strings and keys from Azure SQL DB, look at this guide from Microsoft.

Enabling in Azure SQL DB:

  1. Ensure that SAMI is enabled, go to the logical SQL Server in the Azure portal. Under Security in the resource menu, select Identity.
  2. Under System assigned managed identity, select Status to On.
  3. Connect to the Azure SQL using either SSMS or Azure Data Studio.
  4. Create a contained database user with password, and grant the necessary permissions on the server role with the following T-SQL script:
CREATE USER fabric_user WITH PASSWORD = '<strong password>'; 
ALTER SERVER ROLE [##MS_ServerStateReader##] ADD MEMBER fabric_login;

For further information on how to get connection strings and keys from Azure SQL DB, look at this guide from Microsoft.

Enabling in Snowflake:

Enabling Microsoft Fabric to mirror your snowflake, it is as simple as creating a user with the following permissions:

  2. SELECT table
  3. SHOW tables
  4. DESCRIBE tables

For further information on how to get connection strings and keys from Snowflake, look at this guide from Microsoft.

🚨 Remember that Mirroring is still in preview, so new updates will be released as it moves to General Availability.

Tags: ,