Secure Fabric mirrored databases from Azure Databricks
This article helps you establish data security in your mirrored Azure Databricks in Microsoft Fabric.
Unity Catalog
Users must reconfigure Unity Catalog policies and permissions in Fabric.
To allow Azure Databricks Catalogs to be available in Fabric, see Control external access to data in Unity Catalog.
Unity Catalog policies and permission aren't mirrored in Fabric. Users can't reuse Unity Catalog policies and permissions in Fabric. Permissions set on catalogs, schemas, and tables inside Azure Databricks doesn't carry over to Fabrics workspaces. You need to use Fabric's permission model to set access control on objects in Fabric.
The credential used to create the connection to Unity Catalog of this catalog mirroring is used for all data queries.
Permissions
Permissions set on catalogs, schemas, and tables in your Azure Databricks workspace can't be replicated to your Fabric workspace. Use Fabric's permissions model to set access controls for catalogs, schemas, and tables in Fabric.
When selecting objects to mirror, you can only see the catalogs/schemas/tables that you have access to as per the privileges that are granted to them as per the privilege model described at Unity Catalog privileges and securable objects.
For more information on setting up Fabric Workspace security, see the Permission model and Roles in workspaces in Microsoft Fabric.