Supported Technologies
Lineage connectors
Connection to lineage sources is separate from Data Catalog sources described in Connect to a Source.
Lineage connectors for individual scan plans are set up directly in the plan definition and are only supported in the scope described here.
| Technology | Supported scope | Connector type | Authentication |
|---|---|---|---|
Design-time lineage for:
|
API integration using the Microsoft Azure SDK |
Azure Service Principal |
|
Runtime lineage for:
Using OpenLineage. |
|||
Runtime lineage for:
|
JDBC |
Service Account Key |
|
Databricks Unity Catalog runtime lineage |
JDBC and Unity Catalog REST API |
Personal Access Token (PAT) File folder extraction is also supported. |
|
Design-time lineage for the underlying database technology scanner. See the specific database technology scanner to determine the supported scope. |
API |
Service Account Token File folder extraction is also supported. |
|
Design-time lineage for:
|
JDBC |
Username and password |
|
Design-time lineage for:
|
JDBC |
SQL Server Authentication using SQL login and password |
|
Runtime lineage. The scope depends on the producer. See the relevant documentation. |
API |
||
Design-time lineage for:
|
JDBC |
Username and password |
|
Design-time lineage for:
For limitations on specific PowerQuery constructs and sources, see the scanner documentation. |
REST API |
OAuth 2.0 Client Credentials Flow (Service Principal) |
|
Runtime lineage for:
|
JDBC |
Key Pair Authentication |
|
Design-time lineage for:
|
JDBC |
Username and password |
|
Design-time lineage for:
|
REST API and Metadata API (GraphQL) |
Username and Personal Access Token (PAT) |
Was this page useful?