Microsoft Purview

CluedIn integrates with your Microsoft Purview instance to synchronize your assets, glossaries, and lineage of your data journey in CluedIn.

We have the following assumptions about the customers’ Microsoft Azure setup:

Customers own only one Purview resource.
When ingesting data from ADF, the ADF pipeline should only do a one-to-one mapping from targeted file on Azure to API endpoint.

The following table lists the available Purview packages and versions.

Package name	Package version	Source code
Azure-Extensions	4.4.3	Contact CluedIn for details
Azure-Extensions	4.4.2	Contact CluedIn for details
Azure-Extensions	4.4.1	Contact CluedIn for details
Azure-Extensions	4.4.0	Contact CluedIn for details
Azure-Extensions	4.3.0	Contact CluedIn for details
Azure-Extensions	4.2.2	Contact CluedIn for details
Azure-Extensions	4.2.1	Contact CluedIn for details
Azure-Extensions	4.2.0	Contact CluedIn for details
Azure-Extensions	4.1.0	Contact CluedIn for details
Azure-Extensions	4.0.0	Contact CluedIn for details

In this section

Purview pre-configuration guide how-to
Purview configuration guide how-to
Sync data sources how-to
Data factory pipeline automation how-to
Data factory pipeline run schedule how-to
Sync manual data entry to Purview how-to
Sync processing rules to Purview how-to
Sync clean projects to Purview how-to
Sync deduplication projects to Purview how-to
Sync streams to Purview how-to
Sync Purview glossaries to CluedIn glossaries how-to
Sync Purview glossaries to CluedIn vocabularies how-to
Sync data products how-to

Table of contents