What Oleria discovers
- Users and their profiles, including their authentication methods.
- Groups and group membership.
- Applications registered in your tenant.
- Directory roles and role assignments.
- Policies - conditional access policies, and entitlement management role assignments.
- Non-human identities - service principals and AI agents, with their credentials and permission grants.
- Identity risk events and audit log activity.
- SharePoint and OneDrive sites and the items in them, when you connect M365 SharePoint.
Prerequisites
- A Microsoft Entra ID account with the Global Administrator role, to grant the permissions below.
- Admin access on the Oleria platform to add a new integration.
Integration approaches
Choose one of three ways to connect:- Connect with Microsoft OAuth - automated configuration. Oleria creates the app and requests consent for you.
- Connect with a client secret - manual configuration with an app registration and client secret.
- Connect with a client certificate - manual configuration with an app registration and certificate, for security policies that require certificate-based authentication.
Connect with Microsoft OAuth
Open the integration
- Select Microsoft Entra ID to integrate Entra ID, or
-
Select Microsoft SharePoint and OneDrive to integrate Entra ID, SharePoint, and OneDrive.


Choose permission scope

Select your Microsoft account
Complete the initial consent form

Complete the application consent form
-
Standard read-only permissions for Entra ID integration (without optional remediations)

-
Standard read-only permissions for SharePoint and OneDrive integration (without optional remediation)

-
Permissions for Entra ID integration with optional remediation capabilities (includes some write permissions)

-
Permissions for SharePoint and OneDrive integration with optional remediation capabilities (includes some write permissions)

Connect with a client secret
Create an app registration in Entra ID

Configure the registration

Open API permissions

Add Microsoft Graph permissions

- Standard read-only permissions for Entra ID integration (without optional remediations)
- Standard read-only permissions for SharePoint and OneDrive integration (without optional remediation)
- Permissions for Entra ID integration with optional remediation capabilities (includes some write permissions)
- Permissions for SharePoint and OneDrive integration with optional remediation capabilities (includes some write permissions)
Grant admin consent

Confirm admin consent

Create a client secret

Copy the client secret value

Copy the client ID and tenant ID

Open the integration in Oleria

Authenticate with a client secret

Connect with a client certificate
Client certificate authentication uses a certificate uploaded to your Oleria app registration in Entra ID and a base64-encoded private key stored by Oleria. Use this method when your security policy requires certificate-based service principal authentication instead of a client secret.Prepare your certificate files
certificate.pem- the public certificate in PEM formatprivate_key.txt- the matching unencrypted private key in PEM formatcertificate_chain.txt- the intermediate certificate chain in PEM format
New-SelfSignedCertificate on Windows) and export it in the formats above.private_key.txt is passphrase-protected, decrypt it to a new file with openssl rsa -in private_key.txt -out private_key_unencrypted.txt (or the equivalent for your key type). Keep the encrypted original, and use private_key_unencrypted.txt wherever the commands below reference private_key.txt.Generate the base64-encoded private key
- macOS or Linux
- Windows (PowerShell)
base64_generate_cert.pem is the value you will paste into Oleria in the final step.Upload the certificate to Entra ID
certificate.pem.
Open the integration in Oleria
- For a new integration, select Microsoft Entra ID or Microsoft SharePoint and OneDrive to open the side panel.
- To migrate an existing integration from client secret to client certificate, select Connected, then select the edit icon on your Entra ID integration to open the side panel.
Authenticate with the client certificate

Clean up generated files
generated_cert.pem and base64_generate_cert.pem both contain the unencrypted private key inline, as does private_key_unencrypted.txt if you decrypted a passphrase-protected key. Delete them from the working directory now that the integration is connected. Your original certificate.pem, certificate_chain.txt, and private_key.txt files are unchanged and can stay in your existing key store.- macOS or Linux
- Windows (PowerShell)
history -c on Bash or Zsh, Clear-History on PowerShell.How Oleria handles the private key
The Private Key field in the integration form is masked while you enter it. Oleria receives the value over TLS and stores it encrypted at rest. Only the Oleria service that authenticates to Entra ID can read it, and Oleria doesn’t write the private key to logs.Verify the integration
Whichever approach you used, confirm the Entra ID and M365 SharePoint instances appear on the Connected tab of your Oleria Integrations page with a status of Healthy. After the first sync completes, you can review the discovered users, groups, applications, directory roles, and SharePoint sites in your Oleria workspace.
Remediation actions
If you granted the optional remediation permissions, Oleria can take these actions in Microsoft Entra ID. Each action needs the permission listed in the Add Microsoft Graph permissions step.- Enable or disable a user
- Add or remove a user from a group
- Add or remove a user from a directory role
- Assign or unassign a user to an application
- Assign or remove a group’s access to an application
- Disable a non-human identity (service principal)
- Create a user
- Delete a user
- Revoke a user’s sign-in sessions
Check the Oleria app in your Entra ID instance
Find the Oleria app in Enterprise applications

View granted permissions


