Catalogs, governance and metadata management
Microsoft Purview
Get the best of both. Solidatus does the deep lineage discovery, then pushes assets and column-level lineage into Purview so your Microsoft-centric governance stack is populated automatically.
What it is
Two-way transfer of asset and lineage information between Solidatus and Microsoft Purview.
What Solidatus captures
Database hosts and servers, tables, views, columns and stored procedures created in and matched against Purview, plus view and stored-procedure column-level lineage. Coming back the other way, Purview asset classifications, glossary terms and asset properties are added to the Solidatus model.
What you need
- Solidatus 5.1 or later, network access from the connector to both Solidatus and Purview, and a server with Java 17 and at least 1 CPU core and 8 GB RAM.
- A Solidatus API token with View Model. Create Model is additionally needed if you want Purview identifiers written back into the source Solidatus model.
- An Azure Purview account endpoint, and an Azure service principal with the Data Curator role on the relevant Purview domains and collections. The connector needs the Purview endpoint, tenant ID, client ID, client secret, API token scope and, optionally, a target collection ID.
Good to know
A genuine two-way integration. Today it pushes assets and column-level lineage from Solidatus Snowflake and Oracle models into Purview, and brings Purview classifications, glossary terms and properties back the other way. Purview is moving quickly and so are we, so tell us what you need and we will confirm the current position.
