Skip to content

Correlate Okta and Entra ID

Many organisations run Okta and Entra ID side by side. By default Identiguard treats every tenant on its own. A correlation group tells it that a set of tenants belongs together, so one person’s activity in both is linked.

  • The admin role. Only admins can open Incident settings.
  • At least two tenants in the workspace that share the same people.
  • For incidents across the tenants: a workspace with automatic incidents (Super, or the add-on on Pro and Max).

There is no button to create a group. You create one from a tenant’s dropdown.

  1. Open Incident settings under Workspace.
  2. Go to the Correlation groups card. Each tenant is a row with a dropdown.
  3. On the first tenant’s row, open the dropdown. It shows Isolated (default). Choose New group….
  4. A text box appears with the placeholder Name this group. It is filled in with a name such as “Group A”. Type your own name, for example “Workforce”. The limit is 64 characters.
  5. On the second tenant’s row, open the dropdown and choose that group name.
  6. Read the preview box How these tenants will correlate. It should show a line such as Group "Workforce": Okta production, Entra production.
  7. Choose Save groups.

When it worked: you see the message “Groups saved”. After a reload, both dropdowns show the group name.

  • In Correlations, choose the group as the scope. The graph then shows identities and addresses across both tenants. See Run a correlation.
  • New incidents can include events from both tenants. The score gains 5 points when activity is seen in more than one tenant.
  • The detector One source address across tenants can fire for tenants in the same group.
  1. Open Incident settings and go to Correlation groups.
  2. Set the tenant’s dropdown to Isolated (default).
  3. Check the preview. The tenant should be listed on the line Isolated (default).
  4. Choose Save groups.

A group disappears when no tenant uses it. A group with one tenant behaves the same as an isolated tenant.

There is no rename control. Move the tenants to a group with the new name.

  1. On the first tenant in the group, open the dropdown and choose New group….
  2. Type the new name.
  3. On each other tenant in the group, open the dropdown and choose the new name.
  4. Check the preview, then choose Save groups.

The old group disappears because no tenant uses it.

  • Workforce tenants (Okta and Entra ID) and customer tenants (Auth0) are never correlated with each other, even in the same group.
  • Only group tenants that share the same people. Grouping two different clients’ tenants would link unrelated identities.
  • A tenant left out of every group stays isolated.
  • If you type the name of an existing group in Name this group, the tenant joins that group. Capital letters do not matter, and a space counts the same as a hyphen.
  • If you clear the name, the tenant stays isolated.

Keep each client in their own workspace. Use correlation groups inside a workspace, for one client’s own tenants.

What you see Why What to do
A 403 page: “Forbidden: only workspace admins can manage correlation groups.” You are not an admin Ask an admin
No tenants yet The workspace has no tenants Connect the tenants first
The dropdowns went back to Isolated (default) after a reload The change was not saved Make the change again and choose Save groups
Open incidents still cover one tenant only A change applies to new events only Wait for new events. Existing incidents keep their old grouping.
An Okta tenant and an Auth0 tenant in one group are not linked Workforce and customer identities never correlate This is by design
“Could not save correlation groups.” The save failed Try again
“A correlation group name may be at most 64 characters.” The name is too long Use a shorter name
“Every tenantId must belong to this workspace.” A tenant was deleted while the page was open Reload the page

More messages are listed under Incident settings.