Microsoft Purview
Discover AI-related assets in your Microsoft Purview data catalog.
Airia connects to your Microsoft Purview account and discovers the AI-related assets in its data catalog, using Purview's catalog search (data map discovery query) API.
Authentication model
A Microsoft Entra ID service principal with a client secret. Airia acquires a token for the
Purview resource (https://purview.azure.net) via the client-credentials flow and queries
the account's catalog search endpoint.
Required permissions
The service principal needs data-plane read access to the Purview catalog: assign it the Data Reader role in the Purview governance portal (on the root collection, or on the collections you want in scope). An Azure control-plane role (like Reader on the Purview resource in the Azure portal) is not sufficient; the role must be assigned inside Purview's own collection permissions.
Customer-side setup steps
- In the Azure portal, open Microsoft Entra ID → App registrations → New registration
(for example
airia-purview-discovery). Create a client secret and copy it, along with the Application (client) ID and Directory (tenant) ID. - In the Microsoft Purview governance portal, open Data map → Collections, select the root collection (or the collection in scope), open Role assignments, and add the app to the Data readers role.
- Note your Purview account name (the name of the Purview account resource).
- In Airia, go to Discover → Connections → Microsoft Purview and create a new connection.
Form fields the Airia UI asks for
| Field | Required | Notes |
|---|---|---|
| Tenant ID | Yes | Entra tenant GUID |
| Client ID | Yes | App registration's client ID |
| Client secret | Yes | Stored encrypted, masked on edit |
| Account name | Yes | The Purview account name |
Connection test checks
The connection test validates configuration, authentication (token acquisition for the Purview resource), and catalog search access in order. An authentication failure with valid IDs usually means the secret is wrong or expired; a search failure after successful authentication means the Data Reader assignment is missing.
Multiple environments
Multiple Purview connections per tenant are supported: one per Purview account.