Change which events a tenant sends
Change the event types that a tenant collects, without creating the tenant again.
You need
Section titled “You need”- The admin role in the workspace. Members and viewers cannot open the Edit page.
- Any plan.
- For Okta: working credentials on the tenant. Identiguard updates the event hook in Okta when you save.
Open the event list
Section titled “Open the event list”These steps are the same for every provider.
- Open Tenants in the sidebar.
- In Tenant overview, choose the pencil icon (tooltip Edit) on the tenant’s row. The page Edit Tenant opens.
- Scroll to Event Subscriptions. The list is under Subscribed Event Types, with a counter N of M selected.
The controls:
| Control | What it does |
|---|---|
| Search event types… | Filters the list. Shown when the list has more than 10 types. |
| Select All | Ticks every type. While you search, it becomes Select All Visible and ticks only the types on screen. |
| Clear All | Unticks everything. You must tick at least one type before you save. |
| Select Recommended | Auth0 only. Replaces your whole selection with the recommended set. |
- Open the event list as above.
- Tick the types to add and untick the types to remove.
- Choose Save Changes.
Identiguard rewrites the event hook in the Okta org at once. The page says: “Updating this list changes the Okta event hook immediately.” Okta stops sending the types you removed and starts sending the types you added.
Identiguard only offers types that Okta accepts on an event hook.
- Open the event list as above. Each code shows as a description followed by the code in brackets.
- Tick or untick codes. To go back to the default, choose Select Recommended.
- Choose Save Changes.
The page says: “Updating this list changes which Auth0 log events are ingested. Takes effect immediately; no changes are made in Auth0.”
Select Recommended does not add to your selection. It replaces it. Auth0 publishes 185 log event codes. The recommended set leaves out per-session token exchanges and channel sends, codes superseded by another, and codes Auth0 does not document. If you ticked extra codes by hand, tick them again afterwards.
Entra ID
Section titled “Entra ID”For Entra ID the list holds five streams, not single event types.
- Open the event list as above.
- Tick or untick streams.
- Choose Save Changes.
Identiguard polls the new set of streams from the next poll. The page says: “Updating this list changes the Microsoft subscription immediately.”
Before you add a stream, check that the app registration has the permission and the licence the stream needs:
| Stream | Needs |
|---|---|
| Risky users | IdentityRiskyUser.Read.All |
| Risk detections | IdentityRiskEvent.Read.All |
| Directory audits | AuditLog.Read.All |
| Sign-ins | AuditLog.Read.All and Entra ID P1 |
| Workload identity risk | The Workload ID Premium licence, IdentityRiskyServicePrincipal.Read.All and IdentityRiskEvent.Read.All |
A stream without its permission or licence fails on every poll, and the tenant shows as unhealthy. See Connect Microsoft Entra ID.
You should see
Section titled “You should see”- You return to the Tenants page after Save Changes. There is no confirmation message.
- When you open the Edit page again, the counter N of M selected shows the new number.
- Okta: in the Okta Admin Console under Workflows → Event Hooks, the
IG_Tenant_hook lists the new set of events. - New events of the added types appear on the Dashboard. For Entra ID, wait for the next poll.
If it does not work
Section titled “If it does not work”Errors appear in a banner titled Error at the top of the Edit page.
| What you see | Why | What to do |
|---|---|---|
| A disabled pencil icon with “Admin access required to edit tenant” | Your role is member or viewer | Ask a workspace admin. |
| “At least one event type must be selected” | Nothing is ticked | Tick at least one type. |
| “Invalid Microsoft event type submitted” or “Invalid Auth0 event type submitted” | The page sent a type that is not on the allowed list | Reload the page and select again. |
| “Failed to update Okta event hook: <Okta message>” | Okta rejected the update. Common causes: the client secret has expired, or the integration lost a scope. | Rotate credentials, then save the list again. |
| “Okta event hook ID missing from configuration; recreate the event hook before updating.” | The tenant has no stored hook ID | Delete the tenant and create it again. See Managing tenants. |
| “Okta tenant configuration missing encrypted secrets; recreate the event hook before updating.” or “Failed to decrypt Okta credentials. Please recreate the event hook and try again.” | The stored credentials cannot be used | Delete the tenant and create it again. Escalate to the product team. |
| “Failed to update Auth0 tenant: <message>” or “Failed to update Microsoft tenant: <message>” | A server error | Try again, then escalate. |
| “Forbidden: Insufficient permissions. Admin role required to update tenant.” | You are not an admin | Ask a workspace admin. |
| Auth0 still sends the codes you unticked | The list is a filter in Identiguard only | Nothing is wrong. Change the stream in Auth0 if you want Auth0 to stop sending them. |
| After adding an Entra ID stream, a toast “<tenant name> connection unhealthy” with “Microsoft Graph rejected one or more enabled streams while others polled fine…” | The new stream lacks its permission or licence | Grant the permission and admin consent in Entra ID, or untick the stream again. |
| A detector stopped firing after you removed a type | The detector needs that event type | Tick the type again. See the detector reference. |