Skip to content
Integrations
Catalogs
Microsoft Purview

Microsoft Purview

Microsoft Purview (opens in a new tab) is Azure's data governance service. Its Data Map holds a catalog of the assets scanned across your Azure estate. The Purview monitor reads that Data Map and surfaces the databases, tables, and fields it describes in the Action Center for classification and review.

How the Purview monitor works

The monitor authenticates to your Purview account endpoint and sweeps the Data Map for the relational assets it holds: Azure SQL tables and columns, and Azure Cosmos DB (SQL API) collections. For each asset it captures the name, data type, row count, description, and the time Purview last saw it change.

A Data Map made up mostly of non-relational assets returns few or no results.

Discovered resources appear in the Action Center for review. See the Catalogs overview for the review workflow.

For executing data subject access and erasure requests, see the Microsoft Purview eDiscovery integration.

Prerequisites

To integrate with Purview you'll need an Azure app registration and the account endpoint:

  • Name: a name for the integration in Astralis. Description and System are optional — set System to associate the catalog with an existing system in your inventory.
  • Purview endpoint: your Purview account endpoint, for example https://your-account.purview.azure.com. Endpoints in the Azure Government (.purview.azure.us) and Azure China (.purview.azure.cn) clouds are also accepted. The endpoint must use https.
  • Tenant ID: the Azure AD tenant, or directory, ID from the Azure portal. This is a UUID.
  • Client ID: the Application (client) ID from your app registration. This is also a UUID.
  • Client Secret: the client secret Value from your app registration, under Certificates & secrets.
  • Permissions: the registered application needs a role in the Microsoft Purview governance portal that permits reading the Data Map on each collection you want swept. Without it, the credentials authenticate but the catalog returns nothing.

Set up a Purview monitor

To integrate with Microsoft Purview:

  1. In the Azure portal, create an app registration and note its Application (client) ID and Directory (tenant) ID. Docs (opens in a new tab)
  2. Under Certificates & secrets, add a client secret and copy its Value — not the Secret ID. Docs (opens in a new tab)
  3. In the Microsoft Purview governance portal, assign the application a role that can read the Data Map on the collections you want to sweep. Docs (opens in a new tab)
  4. In Astralis, navigate to Integrations.
  5. Click Add integration.
  6. Select Microsoft Purview.
  7. Enter a Name, and optionally a Description and the System this catalog belongs to.
  8. Enter the Purview endpoint, Tenant ID, Client ID, and Client Secret, then click Save.
  9. Add a monitor and set the execution schedule, or leave it unset to run manually.

You may confirm your connection is working using the Test connection button — Astralis runs a single-result catalog query to verify that the account endpoint is reachable and the credentials are accepted. The same check runs automatically before each scheduled execution.

To learn more, please see our guide for Managing integrations.

For details on reviewing discovered resources, see the Catalogs overview.

OverviewOverview