You need to be an admin of your Xenovia organization to connect any of them. Each keeps its secret encrypted and never shows it again, and uses it only to get short-lived tokens. Choose Sync now on an integration’s page to sync right away; Recent syncs shows how the last ones went. To change its details, choose Settings on the integration page: a field you leave empty keeps its saved value, and Xenovia checks the new values before saving them.
Okta
Before you start
In Okta, create one of these:- An API token from a read-only admin. Xenovia sends it as an
SSWStoken. - An API service app that uses a public and private key pair. Grant it the scopes
okta.apps.read,okta.logs.readandokta.appGrants.read.
okta.appGrants.read lets Xenovia see the scopes each AI app was granted. To let Xenovia block an app, also grant okta.apps.manage.
Connect Okta
1
Open the integration
In Settings › Integrations, find Okta under Identity providers and choose Connect.
2
Enter your details
Give either the API token, or the client id and private key.
3
Connect and check
Choose Connect. Xenovia checks that it can read your apps and your system log. If a check fails, Xenovia shows why and saves nothing.
What Xenovia reads
The first sync reads the last 30 days of sign-ins. Later syncs continue from where the last one stopped. Xenovia keeps only the apps its AI app catalog recognizes and skips the rest. It only reads; it changes nothing in Okta unless you ask it to block an app.
Block an app
Open the app in Discovery and choose Plan a fix. When nothing else can govern the app, the plan can propose Block it in Okta. Applying it deactivates the application in Okta, so nobody can sign in to it. To undo it, activate the application again in Okta. Xenovia only blocks apps that Okta itself reported for that entry. If Okta lists the app more than once, choose which Okta app id to block.Disconnect
Choose Disconnect on the Okta integration page. Xenovia stops syncing and deletes the stored credentials. Open findings from Okta are resolved, and apps only Okta reported leave Discovery. Your reviews of those apps are kept. To cut off access on Okta’s side too, revoke the token or deactivate the service app in Okta.Troubleshooting
Troubleshooting
Microsoft Entra ID
Before you start
In Entra, register an application and give it these Microsoft Graph application permissions, with admin consent:
Then create a client secret for the application.
Connect Entra ID
1
Open the integration
In Settings › Integrations, find Microsoft Entra ID under Identity providers and choose Connect.
2
Enter your details
3
Connect and check
Choose Connect. Xenovia gets a token for the application and checks that it can list service principals, sign-ins and permission grants. If a check fails, Xenovia shows why and saves nothing.
What Xenovia reads
The first sync reads the last 30 days of sign-ins. Later syncs continue from where the last one stopped. Xenovia keeps only the apps its AI app catalog recognizes and skips the rest. It only reads; it changes nothing in Entra unless you ask it to block an app.
Block an app
Open the app in Discovery and choose Plan a fix. When nothing else can govern the app, the plan can propose Block it in Entra. Applying it turns off sign-in for the enterprise application, so nobody can sign in to it. To undo it, enable sign-in for the application again in Entra. Xenovia only blocks service principals that Entra itself reported for that entry. If Entra lists the app more than once, choose which Service principal id to block.Disconnect
Choose Disconnect on the integration page. Xenovia stops syncing and deletes the stored client secret. Open findings from Entra ID are resolved, and apps only Entra ID reported leave Discovery. Your reviews of those apps are kept. To cut off access on Microsoft’s side too, delete the client secret or the app registration in Entra.Troubleshooting
Troubleshooting
Google Workspace
Before you start
You need to be an admin of your Xenovia organization, and a Google Workspace super administrator to set up access.1
Create a service account
In Google Cloud, create a service account and a JSON key for it.
2
Delegate it
In the Google Admin console, open Security › API controls › Domain-wide delegation. Add the service account’s client id with these three scopes:Google refuses the whole token if any one of them is missing.
Connect Google Workspace
1
Open the integration
In Settings › Integrations, find Google Workspace under Identity providers and choose Connect.
2
Enter your details
3
Connect and check
Choose Connect. Xenovia checks that it can read your users, your sign-in reports and your app access policies. If a check fails, Xenovia shows why and saves nothing.
What Xenovia reads
The first sync reads the last 30 days. Later syncs continue from where the last one stopped. Google’s reports can lag by hours, so a sign-in can take that long to appear. Xenovia keeps only the apps its AI app catalog recognizes and skips the rest. It only reads.
When your API controls let unconfigured third-party apps through, an AI app you haven’t configured there gets a finding that says whether it can sign people in or reach your Workspace data. Where unconfigured apps are blocked by default, there is nothing to report.
Disconnect
Choose Disconnect on the integration page. Xenovia stops syncing and deletes the stored private key. Open findings from Google Workspace are resolved, and apps only Google Workspace reported leave Discovery. Your reviews of those apps are kept. To cut off access on Google’s side too, remove the service account’s domain-wide delegation, or delete its key.Troubleshooting
Troubleshooting
Jamf
Before you start
In Jamf Pro, create an API role and an API client that uses it. Give the role:
Then create a client secret for the API client.
Connect Jamf
1
Open the integration
In Settings › Integrations, find Jamf under Device management and choose Connect.
2
Enter your details
3
Connect and check
Choose Connect. Xenovia gets a token and checks that it can read your Jamf Pro version and computer inventory, and the smart group if you named one. If a required check fails, Xenovia shows why and saves nothing.
What Xenovia reads
Every 6 hours, Xenovia reads each managed Mac’s general, hardware, user and application details. It keeps only the installed apps its AI app catalog recognizes, with the bundle id and process name. It only reads; it changes nothing in Jamf unless you ask it to remove an app.Remove an app
Open the app in Discovery and choose Plan a fix. When nothing else can govern the app, the plan can propose Remove it with Jamf. Applying it creates a Restricted Software record in Jamf Pro for the app’s process, scoped to all computers. Jamf then quits the app on every managed Mac and shows people “This app is not allowed by your organization.” The method’s Delete the app, not only quit it setting decides whether Jamf also deletes the app. To stop enforcing it, delete the Restricted Software record in Jamf Pro. A deleted app isn’t restored. Xenovia only uses process names that Jamf itself reported for that entry.Disconnect
Choose Disconnect on the integration page. Xenovia stops syncing and deletes the stored client secret. Its Macs leave Discovery, open findings from Jamf are resolved, and apps only Jamf reported leave Discovery. Your reviews of those apps are kept. Restricted Software records Xenovia created stay in Jamf Pro until you delete them. To cut off access on Jamf’s side too, disable or delete the API client.Troubleshooting
Troubleshooting
Microsoft Intune
Before you start
In Entra, register an application and give it these Microsoft Graph application permissions, with admin consent:
Then create a client secret for the application. You can use the same app registration as Microsoft Entra ID if it has all the permissions both need.
Connect Intune
1
Open the integration
In Settings › Integrations, find Microsoft Intune under Device management and choose Connect.
2
Enter your details
3
Connect and check
Choose Connect. Xenovia gets a token for the application and checks that it can read managed devices, detected apps and compliance settings. If it can’t read devices or apps, Xenovia shows why and saves nothing.
DeviceManagementConfiguration.Read.All the connection still works. The check names the missing permission, and only the compliance details stop.
Xenovia keeps the client secret encrypted and never shows it again. It uses the secret only to get short-lived Graph tokens.
What Xenovia reads
Xenovia keeps only the apps its AI app catalog recognizes and skips the rest. When devices running an AI app fail a compliance setting, the app gets a finding that names the setting. Xenovia only reads; it changes nothing in Intune unless you ask it to remove an app.
Remove an app
Open the app in Discovery and choose Plan a fix. When nothing else can govern the app, the plan can propose Remove it with Intune. Applying it finds the app’s record in Intune by name and adds an uninstall assignment for all devices. Xenovia keeps the app’s existing assignments, so a deliberate deployment to a group isn’t undone. Where the assignments disagree about a device, Intune’s own precedence decides. Intune can only uninstall an app it deploys. An app that Intune only detects has no such record, and Xenovia refuses to remove it. To undo it, remove the uninstall assignment from the app in Intune.Disconnect
Choose Disconnect on the integration page. Xenovia stops syncing and deletes the stored client secret. Its devices leave Discovery, open findings from Intune are resolved, and apps only Intune reported leave Discovery. Your reviews of those apps are kept. Uninstall assignments Xenovia added stay in Intune until you remove them. To cut off access on Microsoft’s side too, delete the client secret or the app registration.Troubleshooting
Troubleshooting
What next?
Discovery
Review what the integrations found.
GitHub
Find the agents in your code too.
AI platforms
Govern Claude and OpenAI platforms your teams use.