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.
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 usehttps. - 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:
- Navigate to Integrations.
- Click Add integration.
- Select Microsoft Purview.
- Enter a Name, and optionally a Description and the System this catalog belongs to.
- Enter the Purview endpoint, Tenant ID, Client ID, and Client Secret, then click Save.
- 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.