Browse connector-style experiences for bringing non-Microsoft signals and governance metadata into Microsoft Purview. In this simulation, LineageAdvisor appears as the planned entry point for Databricks lineage and Power BI impact publishing.
| Connector name | Subscription | Description | Published by | Category |
|---|---|---|---|---|
Bloomberg Message |
Popular | Imports Bloomberg Message data for Microsoft 365 compliance workflows. | Microsoft | |
Generic EHR healthcare |
Imports healthcare data for insider risk management scenarios. | Microsoft | Healthcare | |
|
LineageAdvisor
|
Planned | Publishes selected lineage sources, such as Databricks and/or Power BI metadata, into Microsoft Purview Data Map. | LineageAdvisor | Data Governance |
Power BI |
Native | Microsoft BI metadata and lineage surfaced through Purview/Fabric governance experiences. | Microsoft | Analytics |
Start here and say: “Imagine the customer searches Purview connectors and sees LineageAdvisor listed. This is the planned connector-style entry point. The working integration behind it is our Purview export/Data Map publish path.”
This wizard simulates the install path: source selection, Microsoft Entra consent, Purview target selection, optional Databricks and/or Power BI scopes, schedule, and review.
After setup, the customer sees an operational connector status page: last crawl, next schedule, Purview publish status, run logs, and the ability to trigger a manual run.
Click “Run now” during the demo. The simulated run should show the customer that the connector is operational: crawl, transform, publish, verify. Then click “Open in Purview” to show the Data Map result.
This is the payoff screen. The customer sees the published collection, created assets, and lineage path connecting Databricks source assets to Power BI consumption.
This screen answers the client’s practical question: “After setup, what do I get in Purview?” Keep repeating that this is metadata lineage and governance evidence, not business data movement.
This page is for Q&A. It separates the Microsoft connector/gallery route from the working Data Map API route, so the demo stays credible.
“The screens you saw simulate the connector-style install experience we want customers to have inside Purview. The underlying mechanics are already aligned with Purview’s extensibility model: Entra authorization, service-principal-style setup, Data Map asset publishing, custom type definitions, and lineage relationships. For today’s pilot, we can run this through LineageAdvisor and export into Purview; for long-term parity, we pursue the Microsoft connector/listing route.”