Open Mirroring connector

This article outlines how to configure the Open Mirroring connector to push data from CluedIn to Microsoft’s Fabric.

Prerequisites: Make sure you use a service principal to authenticate and access Open Mirroring.

• In PowerBI/Fabric, enable the following settings:

  • Service principals can use Fabric APIs

    

  • Users can access data stored in OneLake with apps external to Fabric

    

• In the workspace that you want to use in Open Mirroring connector, give at least Contributor access to the Open Mirroring service principal. To do that, in the workspace, select Manage access.

  

  Then, add the Open Mirroring service principal and assign it the Contributor role to the workspace.

  

To configure Open Mirroring connector

1. On the navigation pane, go to Consume > Export Targets. Then, select Add Export Target.

2. On the Choose Target tab, select Fabric Open Mirroring Connector. Then, select Next.

3. On the Configure tab, enter the connection details:

   1. Name – user-friendly name of the export target that will be displayed on the Export Target page in CluedIn.

   2. WorkspaceName – name of the workspace where you want to store the data from CluedIn.

      To find the workspace, sign in to Microsoft Fabric, and then select Workspaces from the left-hand menu. In the list of workspaces, find the needed workspace and select it.

      

   3. Create Mirrored Database – Automatically creates the Mirrored Database if it doesn’t exist. Requires ‘Admin’ permission in the workspace.

   4. Mirrored Database Name – name of the Mirrored Database if it already exists in Microsoft Fabric. Leaving this empty will create a new Mirrored Database.

      

   5. ClientID – unique identifier assigned to the Open Mirroring app when it was registered in the Microsoft identity platform. You can find this value in the Overview section of app registration.

      

   6. ClientSecret – confidential string used by your Open Mirroring app to authenticate itself to the Microsoft identity platform. You can find this value in the Certificates & secrets section of app registration.

      

   7. TenantID – unique identifier for your Microsoft Entra tenant. You can find this value in the Overview section of app registration.

      

   8. Output Format – file format for the exported data. You can choose between JSON, Parquet, and CSV. However, Parquet and CSV formats are available only if you enabled stream cache. If stream cache is not enabled, JSON is the default format.

   9. Export Schedule – schedule for sending the files from CluedIn to the export target. The files will be exported based on Coordinated Universal Time (UTC), which has an offset of 00:00. You can choose between the following options:

      • Hourly – files will be exported every hour (for example, at 1:00 AM, at 2:00 AM, and so on).

      • Daily – files will be exported every day at 12:00 AM.

      • Weekly – files will be exported every Monday at 12:00 AM.

      • Custom Cron – you can create a specific schedule for exporting files by entering the cron expression in the Custom Cron field. For example, the cron expression 0 18 * * * means that the files will be exported every day at 6:00 PM.

   10. (Optional) File Name Pattern – a file name pattern for the export file. For more information, see File name patterns.

       For example, in the {ContainerName}.{OutputFormat} pattern, {ContainerName} is the Target Name in the stream, and {OutputFormat} is the output format that you select in step 3j. In this case, every time the scheduled export occurs, it will generate the same file name, replacing the previously exported file.

       If you do not specify the file name pattern, CluedIn will use the default file name pattern: {StreamId:N}_{DataTime:yyyyMMddHHmmss}.{OutputFormat}.

4. Test the connection to make sure it works, and then select Add.

You can follow this video to see how it works and what settings to provide to CluedIn.