Microsoft Entra ID connector

Important

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Microsoft Entra ID from the Previews page. See Manage Azure Databricks previews.

The managed Microsoft Entra ID connector in Lakeflow Connect ingests directory objects, role assignments, identity configuration, and audit and sign-in logs from Microsoft Entra ID into Azure Databricks.

Feature availability

Feature	Availability
UI-based pipeline authoring	Supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Supported
Unity Catalog governance	Supported
Orchestration using Databricks Workflows	Supported
API-based column selection and deselection	Supported
API-based row filtering	Not supported
SCD Type 2	Supported Tables with VARIANT columns (users, serviceprincipals) do not support SCD type 2.
Automated schema evolution: New and deleted columns	Supported
Automated schema evolution: Data type changes	Not supported
Automated schema evolution: Column renames	Not supported Requires a full refresh.

Authentication methods

Authentication method	Availability
OAuth U2M	Not supported
OAuth M2M	Supported Application (client) ID and client secret from a Microsoft Entra ID app registration.
Basic authentication (username/password)	Not supported

Ingest from Microsoft Entra ID in 3 steps

Note

Before starting, review the Azure Databricks user persona, supported interfaces, ingestion frequency, and common patterns.

1. Configure Microsoft Entra ID for ingestion (Admins): Set up Microsoft Entra ID to authenticate with Azure Databricks.
2. Create a Unity Catalog connection (Admins): Create a connection in Catalog Explorer to store credentials for Databricks to authenticate with Microsoft Entra ID.
3. Create an ingestion pipeline (Admins or non-admins): Select any supported interface and create a pipeline from an existing connection.