Skip to main content

​
What is the Microsoft Purview integration?

The Purview integration connects Prizm to your Microsoft Purview catalog. Prizm pushes data quality results to Purview assets and attributes, so catalog users see quality next to the governance metadata they already use. Prizm also pulls domains, tags, products, and glossary terms from Purview into its semantics layer.

​
What this integration enables

​
Authentication

Prizm authenticates to Purview with a Microsoft Entra ID service principal, using the OAuth 2.0 client credentials flow. You provide the Purview account, the Tenant ID, the Client ID, and a Client Secret. Prizm requests tokens against the Purview scope https://purview.azure.net/.default and refreshes them automatically.

​
Out of scope

  • Editing Purview assets directly from Prizm
  • Running scans in Purview
  • Pushing standalone measure-level metrics

​
Prerequisites

  • A Microsoft Purview account that Prizm can reach over HTTPS
  • A Microsoft Entra ID app registration (service principal) with a client secret, and an Azure subscription that contains the Purview account
  • The service principal assigned the Data Reader role to pull, and the Data Curator role to push, on the Purview collections you want to include. A Collection Admin role is needed only if Prizm must create custom metadata types
  • A configured vault, if you want Prizm to fetch the client secret from one
  • Admin or privileged user access in Prizm

Setup

Connect Purview to Prizm, configure push and pull, and schedule syncs.

Atlan integration

Another catalog integration with the same push and pull model.