What Oleria discovers
Prerequisites
- A Microsoft Purview account in the commercial cloud. The free version of Microsoft Purview has no Purview account, so it can’t be connected.
- A Global Administrator or Privileged Role Administrator, to grant admin consent for Microsoft Graph application permissions. A Cloud Application Administrator or Application Administrator can’t grant them.
- A Collection administrator of the account’s root collection, or a domain admin, to assign the app its Data Map roles.
- The audit log turned on in your organization, for Data Map activity. Audit (Standard) is on by default for most Microsoft 365 organizations.
- Optional, for governance domains: a Data Governance Administrator or Governance Domain Creator, to assign the Governance Domain Owner role on each governance domain.
- Optional, for Azure role holders and the account’s managed identities: a User Access Administrator or Role Based Access Control Administrator on the Purview account, and its Azure subscription ID.
- Optional: Microsoft Entra ID P1 or P2, for last sign-in and MFA status. Without it, Oleria still syncs, and those fields show as unavailable.
Choose an authentication method
The connection form offers three methods. Pick one:- Authenticate via Microsoft (OAuth), the default. You grant admin consent to Oleria’s Microsoft app. You don’t register an app or manage a credential.
- Client Secret Authentication. You register your own app in Microsoft Entra ID and give Oleria a client secret.
- Client Certificate Authentication. You register your own app and give Oleria a certificate and its unencrypted private key.
1
Register an application
Sign in to the Microsoft Entra admin center as at least an Application Developer. Go to Entra ID -> App registrations -> New registration. Name the app (for example,
Oleria Purview) and select Register. On its Overview page, copy the Application (client) ID and Directory (tenant) ID.2
Create a credential
- Client secret
- Client certificate
Select Certificates & secrets -> Client secrets -> New client secret, add a description, choose an expiration, and select Add. Copy the secret’s Value. Microsoft never displays it again after you leave the page. A client secret lasts at most 24 months, so update the integration in Oleria before it expires.
3
Grant Microsoft Graph permissions
Select API permissions -> Add a permission -> Microsoft Graph -> Application permissions. Add these permissions, select Add permissions, then select Grant admin consent for your tenant:Optionally, also add:
Application.Read.All, for service principal details.AuditLog.Read.All, for last sign-in and MFA status. It also needs Microsoft Entra ID P1 or P2.Organization.Read.All, so Oleria matches sign-ins on your verified domains.Member.Read.Hidden, for the members of groups with hidden membership.RoleManagement.Read.Directory, for the members of the Microsoft Entra roles, such as Global Administrator, that Purview makes Collection administrators.
User.Read.All. Without one of the other permissions, Oleria still syncs, with less detail:
Assign Purview roles to the app
Purview doesn’t use Microsoft Graph permissions for its own data. The app reads Purview through roles that you assign to its service principal inside Purview. Do this for every authentication method. With OAuth, the app is Oleria’s Microsoft 365 app, the same app that the SharePoint & OneDrive integration without write actions, and the Microsoft Dynamics 365, Microsoft Fabric, and Microsoft Power Platform integrations, use with OAuth. If you’ve already connected one of them with OAuth, the app is already in your tenant: find it under Entra ID -> Enterprise apps -> All applications in the Microsoft Entra admin center, and assign the roles before you connect. Otherwise, it’s added to your tenant when an administrator grants admin consent in Connect Microsoft Purview to Oleria. Note the app name that Microsoft shows on the consent screen. The roles you assign belong to that app, not to this connection alone. To keep Purview access separate, use your own app registration.1
Assign the Data Map roles on the root collection
Sign in to the Microsoft Purview portal as a Collection administrator of the root collection. When the account is your tenant’s primary account in the new Microsoft Purview portal, its root collection is the default domain: open Data Map, select Domains, then select the default domain. Other accounts in the tenant use the classic portal: select Data Map -> Collections, then select the root collection, which has the same name as your Purview account.Select the Role assignments tab. For each of these roles, select Edit role assignments or the person icon, search for the app, and select OK:
- Collection administrator, which Oleria needs to read collections and their role assignments.
- Data source administrator, which Oleria needs to read data sources and scans. Without it, the sync still reads collections and access, without data sources and scans. With your own app registration, Oleria doesn’t connect until the app holds both roles.
2
Optional: assign Unified Catalog roles
Skip this step if you don’t need governance domains. The Unified Catalog is available only with the tenant-level account of the new Microsoft Purview portal.For each governance domain, go to Unified Catalog -> Catalog management -> Governance domains and select the domain. On the Roles tab, select + next to Governance Domain Owner, search for the app, select it, and select Save. Purview can take a few hours to let the app read the domain after you assign the role.Governance Domain Owner lets the app read the domain and its role holders, but Purview refuses it the domain’s data products. Oleria skips data products it can’t read, and the sync continues.
Governance Domain Owner can delegate domain permissions and set domain-level access policies. Oleria only reads the Unified Catalog. It doesn’t change it.
3
Optional: assign the Azure Reader role
Skip this step if you don’t need the Azure role holders and managed identities of the Purview account. In the Azure portal, open the Purview account. Select Access control (IAM) -> Add -> Add role assignment, and select the Reader role. On the Members tab, select User, group, or service principal, select Select members, choose the app, and select Review + assign. Reader lets the app view the account, but not change it.To find the subscription ID, go to Subscriptions in the Azure portal, select the subscription that holds the Purview account, and copy the Subscription ID from the Essentials section.
Connect Microsoft Purview to Oleria
1
Open the integration
Sign in to your Oleria workspace, go to Integrations, and find Microsoft Purview. Select the + icon (Add Integration for Microsoft Purview), or Connect in the list view.
2
Complete the connection form
3
Authenticate
Select Authenticate. With OAuth, Microsoft asks an administrator to grant consent, then returns you to Oleria. Before it saves the connection, Oleria checks that it can read users from Microsoft Graph, and role assignments and data sources from the Purview account.With OAuth, consent adds the app to your tenant, so it can’t hold a Purview role yet. When Purview answers that the app holds no role (status
403), Oleria saves the connection so that you can assign the roles after consent. Assign the Purview roles next. Until the app holds Collection administrator, the sync of resources and access fails. Activity still syncs, without links to collections. If Oleria shows that Microsoft Purview refused the app instead, assign the roles and select Authenticate again.Verify the integration
Confirm that the connection appears on the Connected tab of the Integrations page with a status of Healthy. After the first sync, review users, non-human identities, groups, and collections in your Oleria workspace. If the first sync fails, check that the app holds Collection administrator on the root collection. If data sources or scans are missing, check that it holds Data source administrator there too. Both are in Assign Purview roles to the app. The integration’s Capabilities and operation readiness section lists the permissions each capability needs. It names the Data Map rolesMicrosoft Purview Data Map role: Collection administrator and Microsoft Purview Data Map role: Data source administrator.
Remediation actions
Oleria offers Revoke permission to resource instance for collections when I authorize Oleria to perform write actions in Microsoft Purview is selected. It needs the Collection administrator role that the sync uses, plus theUser.Read.All and GroupMember.Read.All permissions, so that Oleria can check group memberships before it removes a role. Capabilities and operation readiness lists all three as the action’s required permissions.
Oleria refuses to revoke:
- Access to the account, a data source, a scan, or a Unified Catalog item. Only collection roles can be removed.
- The app’s own role on a collection.
- The last Collection administrator of a root collection. Oleria counts a Microsoft Entra directory role named there, such as Global Administrator, as another Collection administrator.
- A group that is the app’s only path to Collection administrator on the collection, because Oleria couldn’t revert the change.
- A role that the principal also holds on a parent collection that this collection inherits from. Remove it on the parent collection.
- A role that the principal also holds through a group. Oleria names the group, the role, and the collection. Remove the principal from the group, or remove the group’s role in Purview.
- A role that the principal also holds through a Microsoft Entra directory role named on the collection or a parent collection, directly or through a role-assignable group. Remove the principal’s directory role assignment in Microsoft Entra ID.
RoleManagement.Read.Directory, Oleria can’t read who holds those directory roles. It removes the principal’s direct role without checking them, so a principal who also holds one of those directory roles keeps the access.
Purview doesn’t let you remove a Collection administrator that a collection inherits from its parent collection.
Known limitations
- Commercial cloud only. Purview accounts in the US Government and China clouds can’t be connected.
- One Purview account per connection. To connect several accounts in one tenant, add one Oleria integration per account. The Unified Catalog belongs to the whole tenant, so each of those integrations shows it.
- Last activity is the last Microsoft Entra sign-in, not the last use of Purview. It needs
AuditLog.Read.Alland Microsoft Entra ID P1 or P2. - Activity looks back up to 180 days on the first sync. After that, Oleria reads new events with a two-hour delay. Microsoft doesn’t guarantee how soon an event reaches the audit log, and an event that reaches it more than two hours late isn’t collected.
- Activity covers the whole tenant. Data Map events from every Purview account in the tenant are collected. Only events that name one of this account’s collections, data sources, or scans are linked to it.
- Some Data Map events show Purview’s own operation name. Creating a collection, data source, or scan appears as a created object, on the collection, data source, or scan it names. Other collection, role assignment, data source, and scan events appear as custom activity, with the operation name that Purview records.
- Data source and scan creation events name no user. Purview records the client software that made the change, not who made it.
- Inherited collection roles appear once, on the collection where they’re assigned, not on each subcollection.
- Deleted principals are skipped when the app has
Application.Read.All. A role assignment that names a user or app that no longer exists in Microsoft Entra ID isn’t shown. Without that permission, a deleted user or app that still holds a Purview role appears as an enabled non-human identity, named by its object ID. - The free version of Microsoft Purview can’t be connected. It has no Purview account.
- Not synced: Microsoft Purview portal role groups and compliance role groups and their members, Microsoft Entra roles that no Purview policy names, data loss prevention (DLP) policies, and sensitivity labels and their policies.
- Unified Catalog roles can’t be removed from Oleria, and disabling non-human identities isn’t offered from this integration.
Troubleshooting
When Oleria can’t connect, it shows Error creating integration, followed byreceived invalid inputs. actual error: and one of these messages:

