What Oleria discovers
Prerequisites
- A Microsoft Power Platform tenant in the commercial cloud.
- 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 it.
- A Global Administrator or Power Platform Administrator, to register the app as a Power Platform management application.
- For activity: audit logging turned on in Microsoft Purview, which needs the Audit Logs role in Exchange Online, and in each production environment, which needs the system administrator or system customizer role there.
- Optional: Microsoft Entra ID P1 or P2, for last sign-in, MFA status, and authentication methods. Without it, Oleria still syncs, without those details.
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 create your own app registration 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 private key.
Register an application
Oleria Power Platform) and select Register. On its Overview page, copy the Application (client) ID and Directory (tenant) ID.Create a credential
- Client secret
- Client certificate
Grant API permissions
ActivityFeed.Read, and select Add permissions.Optionally, also add these Microsoft Graph application permissions:Application.Read.All, for the details of service principals with access.AuditLog.Read.All, for last sign-in, MFA status, and authentication methods. It also needs Microsoft Entra ID P1 or P2.Organization.Read.All, so Oleria names the connection after your organization instead of your tenant ID, and matches sign-ins on your verified domains.
User.Read.All. Without one of the other permissions, Oleria still syncs, with less detail:
Register the app as a Power Platform management application
Power Platform admin APIs accept an app only after an administrator registers it with Power Platform as a management application. Do this for every authentication method. You can’t do it in the Power Platform admin center, and the app can’t register itself. An administrator must run the registration while signed in interactively as themselves, not as an app. You need the app’s Application (client) ID:- Your own app: the Application (client) ID from its Overview page.
- OAuth: Oleria’s app is added to your tenant when an administrator first grants admin consent to it. Follow Connect Microsoft Power Platform to Oleria and grant consent first. Oleria then shows a registration error, which is expected at this point. The error includes the app’s client ID (see Troubleshooting). After you register it, select Authenticate again.
Install the Power Apps admin PowerShell module
Register the app
Add-PowerAppsAccount signs you in interactively. With OAuth, find your tenant ID in the Microsoft Entra admin center under Entra ID -> Overview -> Properties -> Tenant ID.pac admin application register --application-id <client-id>.Remove-PowerAppManagementApp -ApplicationId <client-id>, or pac admin application unregister --application-id <client-id>.
Turn on audit logging
Oleria reads Power Platform activity from the Microsoft Purview audit log. Microsoft records Power Platform administrator activity by default. Power Apps and Power Automate user activity needs audit logging turned on in Purview and in each environment.Confirm that auditing is on in Microsoft Purview
Turn on auditing for each production environment
Send each environment's logs to Purview
https://*.api.powerplatformusercontent.com domain to your allow list before you turn on this setting. Otherwise, most Shared Access Signature (SAS) features don’t work.Connect Microsoft Power Platform to Oleria
Open the integration
Complete the connection form
Authenticate
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 environments in your Oleria workspace. The integration’s Capabilities and operation readiness section lists the permissions each capability needs. Power Platform access appears there as Power Platform management application registration. The first activity can take up to 12 hours to appear, because Microsoft starts delivering audit records up to 12 hours after Oleria subscribes to them. If the first sync fails, check that the app is still registered as a Power Platform management application in the tenant you connected. A missing registration stops the sync.Remediation actions
Oleria offers Revoke permission to resource instance when I authorize Oleria to perform write actions in Microsoft Power Platform is selected. It needs the management application registration. Revoking a service principal’s access also needs the optionalApplication.Read.All permission.
- The owner of a canvas app, cloud flow, connection, or custom connector. Microsoft documents these ways to change an owner:
- Canvas app: an administrator runs
Set-AdminPowerAppOwner. The previous owner keeps view access. - Cloud flow: only a solution-aware flow’s owner can be changed, in Power Automate. The previous and new owners both become co-owners.
- Connection: its owner can only be removed by deleting the connection.
- Custom connector: Microsoft documents no way to change its owner.
- Canvas app: an administrator runs
- Environment roles in an environment with Dataverse. Its roles are Dataverse security roles, which the Microsoft Dynamics 365 integration manages.
- Access that an account has only through a group, or only through a share with everyone in your organization. The error gives the group’s object ID and role, or Entire organization. Remove the account from the group, or remove that share in Power Platform.
- The Oleria app’s own access.
- Access that includes a role Oleria couldn’t add back on revert. The error names the role, and Oleria removes nothing. Remove that access in Power Platform.
GroupMember.Read.All, the action still succeeds, and its result doesn’t list access through a group.
Known limitations
- Commercial cloud only. Oleria reads only the commercial-cloud Power Platform APIs, so tenants in the US Government (GCC, GCC High, DoD) and China clouds aren’t supported.
- Model-driven apps aren’t inventoried by this integration or the Microsoft Dynamics 365 integration. Their access is governed by Dataverse security roles, which the Microsoft Dynamics 365 integration collects for the environment it’s connected to. To see those roles, connect each Dataverse environment to the Microsoft Dynamics 365 integration. For the same reason, Oleria reads environment roles only in environments without Dataverse.
- Only custom connectors are collected. Microsoft’s own connectors aren’t shown as resources.
- A refused request skips only that part of an environment. If Power Platform rejects or denies the request for an environment’s roles, canvas apps, connections, or custom connectors, Oleria skips them for that sync and continues. If it rejects the request for one app’s, connection’s, or custom connector’s sharing, Oleria skips only that item. If Power Platform denies the request to list canvas apps, connections, or custom connectors in every environment, the sync fails, because that means the management application registration was removed. A denied request for one item’s sharing, or for an environment’s roles, doesn’t count toward this, because Power Platform denies role requests for environments with Dataverse. A timeout, throttling, or a list that stops partway through also fails the sync.
- Cloud flows come from an API Microsoft doesn’t support. If Microsoft’s flow admin API rejects the request for an environment’s flows, or answers in a form Oleria can’t read, Oleria skips them for that sync. If it can’t read one flow’s permissions, Oleria skips that flow. A timeout, throttling, or a server error fails the sync instead.
- Last activity is the last Microsoft Entra sign-in, not the last use of Power Platform. It needs
AuditLog.Read.Alland Microsoft Entra ID P1 or P2. - Activity looks back up to 7 days on the first sync. After that, Oleria reads new events with a two-hour delay.
- Groups with hidden membership appear without members. Reading them needs
Member.Read.Hidden, which Oleria doesn’t request. - Eligible role assignments aren’t shown. Oleria reads active, directory-wide assignments of the Global, Power Platform, and Dynamics 365 Administrator roles, not Privileged Identity Management (PIM) eligibilities.
- Not synced: Copilot Studio agents, Power Platform licenses, desktop flows, gateways, Power Pages, and data policies.
- 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:

