Tenant health
A tenant that has stopped sending events looks quiet, and quiet can be mistaken for safe. Check tenant health before trusting an empty feed.
Where to look
Section titled “Where to look”There is no single “credentials status” field. Health shows in these places:
| Place | What it shows | Who sees it |
|---|---|---|
| The toast <tenant name> connection unhealthy | A tenant whose monitor is in a critical state | Admins, on any page of the workspace |
| Dashboard → Tenant status | Every tenant, grouped by platform, with All clear or a count of active events. Okta cards also show the AD and LDAP agent rows. | Everyone |
| The tenant’s Edit page, Credentials card | The alert Monitoring paused when monitoring has stopped itself | Admins |
| The tenant’s Edit page, Agent Monitoring (Okta) | Status: and Last check: for each agent monitor | Admins |
| Tenants → Tenant topology | Average events per minute for each tenant over the last 24 hours. This is a traffic view, not a health view. | Everyone |
To open a tenant’s Edit page, go to Tenants and choose the pencil icon (Edit) on its row in Tenant overview. See Managing tenants.
The connection unhealthy toast
Section titled “The connection unhealthy toast”When a tenant’s monitor is in a critical state, each workspace admin sees a warning toast:
- Title: <tenant name> connection unhealthy.
- Text: the monitor’s summary, for example “Okta credentials rejected. Re-check the client ID and secret.”
- Button: Review settings. It opens that tenant’s Edit page.
The toast does not close by itself. It shows once per tenant each time you load the application, on any page of the workspace. It stops appearing after you rotate the credentials successfully. Members and viewers do not see it.
The toast covers Okta tenants with agent monitoring and Entra ID tenants. Auth0 tenants have no stored credentials, so they do not raise it.
Automatic pause
Section titled “Automatic pause”Identiguard switches a monitor off by itself when it keeps failing.
- This applies to each Okta AD or LDAP agent monitor, and to the Entra ID poll.
- A monitor is paused after 5 consecutive failed checks.
- Before that, the monitor’s summary gains a counter, such as “(3 consecutive failures)”.
- For Entra ID, rate-limit responses and server errors from Microsoft do not count as failures.
- After the pause, the summary reads “Monitoring disabled after 5 consecutive failures. Update the connection credentials to resume.”
- Identiguard sends each workspace admin one email with the subject Monitoring disabled for <tenant name>. The email has an Update credentials button that opens the Edit page.
A paused monitor runs no checks. For Okta, events still arrive, because the event hook does not depend on the agent monitors. For Entra ID, no new events arrive while the poll is paused.
How a pause shows
Section titled “How a pause shows”| Where | What you see |
|---|---|
| Any page (admins) | The toast <tenant name> connection unhealthy |
| Edit page, Credentials card | Alert Monitoring paused: “Monitoring for this connection was disabled automatically after repeated failures. Rotate the credentials below to resume checks - monitoring restarts as soon as the new credentials are verified.” |
| Edit page, Agent Monitoring (Okta only) | Status: Paused after repeated failures. The Monitor AD Agents or Monitor LDAP Agents checkbox is locked. The helper text reads “Monitoring paused after repeated failures - rotate the credentials below to resume.” |
For an Entra ID tenant, the only sign on the Edit page is the Monitoring paused alert.
How to resume
Section titled “How to resume”There is one way to resume: a successful credential rotation. There is no resume or re-verify button.
- Open the tenant’s Edit page. The Review settings button on the toast takes you there.
- In the Credentials card, enter the Client Secret. Enter Client ID (optional) only if it changed.
- Choose Validate & save credentials.
- Wait for the alert Verified.
Monitoring restarts at once. The monitor’s state reads “Credentials updated. Awaiting next check.” until the next check runs.
Entering the same secret again also works, because Identiguard verifies it again. Use this when the cause was on the platform side and is now fixed. For the full steps see Rotate credentials.
Entra ID: slow retry and partial failures
Section titled “Entra ID: slow retry and partial failures”- When Microsoft rejects the credentials for every stream, Identiguard slows down to one attempt every 30 minutes. If you fix the problem in Entra ID only, Identiguard can take up to 30 minutes to notice. Rotating the credentials in Identiguard is faster.
- When Microsoft rejects some streams and accepts others, Identiguard keeps polling the streams that work. The toast reads “Microsoft Graph rejected one or more enabled streams while others polled fine. Re-check the app registration permissions/licence for the subscribed event types.” A new secret does not fix this. Grant the missing permission or licence, or untick the stream. See Change which events a tenant sends.
Okta directory agents
Section titled “Okta directory agents”Agent monitoring checks the health of the Okta AD and LDAP agents on a schedule. It needs the Okta scope okta.agentPools.read. You switch it on at creation or on the Edit page. See Managing tenants.
On the dashboard card
Section titled “On the dashboard card”Each Okta card under Tenant status shows the rows AD Agents and LDAP Agents.
- A status pill shows the overall state. Hover over it to read the summary.
- Pending… means monitoring is on and no check has finished yet.
- Not Monitoring means that monitor is off.
- Expand the row to list each agent: its name, version (
v<version>), status, whether an upgrade is needed and when it was last seen.
On the Edit page
Section titled “On the Edit page”Under Agent Monitoring, each monitor shows Status: and Last check:. Opening the Edit page runs a fresh check of each monitor that is on. Last check: reads Never when the monitor is off.
| Status | Meaning |
|---|---|
| Healthy | Every agent reports healthy |
| Warning | At least one agent is degraded |
| Critical | At least one agent is in a critical state |
| Disrupted | At least one agent is disrupted |
| Offline | At least one agent is offline |
| Update Required | At least one agent needs an update |
| No Agents Installed | The org has no agents of this kind |
| Unknown | The check could not work out the state |
| Not Monitoring | The monitor is off |
| Paused after repeated failures | The monitor paused itself. See Automatic pause. |
Provider status banner
Section titled “Provider status banner”When the platform itself has reported an incident, a status banner appears on the tenant card on the Dashboard. Select the banner to open that provider’s status page. See Status and advisories.
Tenant topology
Section titled “Tenant topology”The Tenant topology card on the Tenants page draws each tenant around the Identiguard control plane with an “X req/min” label. A tenant at “0 req/min” has sent no events in the last 24 hours. A broken tenant otherwise looks the same as a working one, so do not use the topology as a health check. See Managing tenants.
Trial workspaces
Section titled “Trial workspaces”On a trial, one identity tenant can be used for one trial only. What happens depends on the provider.
| Provider | What happens when the tenant was already used in another trial |
|---|---|
| Okta | Creation is refused: “This Okta org has already been used in another Identiguard trial, so it cannot be added to a new one. Choose a plan on the Billing page to add it, or contact Identiguard support.” |
| Entra ID | Creation is refused: “This Microsoft Entra tenant has already been used in another Identiguard trial, so it cannot be added to a new one. Choose a plan on the Billing page to add it, or contact Identiguard support.” |
| Auth0 | The tenant is created, but Identiguard does not accept its events. The Tenants page shows a banner. |
The Auth0 banner reads:
- Title: Some tenants are not being monitored on this trial.
- Text: “Identiguard is not accepting events from these Auth0 tenants, because each has already been used in another Identiguard trial. Choose a plan on the Billing page to monitor them, or contact Identiguard support.”
- A list of the affected tenant names.
- A link: Go to the Billing page.
The banner shows only while the workspace is on a trial, and lists Auth0 tenants only. To clear it, choose a plan. See Plans and billing.
On a trial, Identiguard also proves that you control an Okta org or Entra directory before it adds it, by signing in with the client ID and secret you enter.
Removing a tenant
Section titled “Removing a tenant”Only an admin can delete a tenant. Choose the bin icon (Delete tenant) on its row in Tenant overview. See Managing tenants for what is removed and for Force delete tenant.
Troubleshooting
Section titled “Troubleshooting”Connection health
Section titled “Connection health”| What you see | Why | What to do |
|---|---|---|
| Toast “<tenant name> connection unhealthy” with “Okta credentials rejected. Re-check the client ID and secret.” | Okta refused an agent check | Choose Review settings and rotate the credentials. Check that the integration grants okta.agentPools.read. |
| Toast with “Microsoft Graph credentials rejected. Re-check the client ID and secret.” | Microsoft refused every stream. The secret has expired or was revoked. | Rotate the credentials. Until then Identiguard retries only every 30 minutes. |
| Toast with “Microsoft Graph rejected one or more enabled streams while others polled fine. Re-check the app registration permissions/licence for the subscribed event types.” | One subscribed stream lacks its permission or licence. Typical causes: sign-ins without P1, workload identity risk without Workload ID Premium, or AuditLog.Read.All not granted. |
Grant the permission and admin consent, or untick that stream under Event Subscriptions. A new secret does not help. |
| “(N consecutive failures)” at the end of a summary | The monitor has failed N checks in a row | Fix the cause before the count reaches 5. |
| “Monitoring disabled after 5 consecutive failures. Update the connection credentials to resume.” | The monitor paused itself | Choose Validate & save credentials with a working secret. |
| Alert Monitoring paused in the Credentials card | The same | The same. |
| Status: Paused after repeated failures, with a locked checkbox and “Monitoring paused after repeated failures - rotate the credentials below to resume.” | An Okta agent monitor paused itself | The same. The checkbox unlocks after the credentials are verified. |
| An email “Monitoring disabled for <tenant name>” | A monitor paused itself. The email goes to workspace admins. | Choose Update credentials in the email and rotate the credentials. |
| “Credentials updated. Awaiting next check.” | You rotated the credentials and no check has run since | Wait for the next check. |
| The toast is still there after you fixed the problem in Okta or Entra ID | The toast shows the last stored state. Entra ID is retried only every 30 minutes after a full rejection. | Rotate the credentials in Identiguard (the same secret is accepted), then reload the page. |
Okta agents
Section titled “Okta agents”| What you see | Why | What to do |
|---|---|---|
| Not Monitoring | The monitor is unticked | On the Edit page, tick Monitor AD Agents or Monitor LDAP Agents and choose Save Changes. If the checkbox is locked, the monitor is paused: rotate the credentials first. |
| Pending… or “No monitor check has completed yet.” | Monitoring is on and no check has finished | Wait one check interval. |
| No Agents Installed, “No Okta AD agent pools found for this tenant.” or “No Okta LDAP agent pools found for this tenant.” | The org has no agents of that kind | Switch that monitor off. |
| Offline, Disrupted, Update Required, or a summary such as “N agent(s) offline”, “N agent(s) disrupted”, “N agent(s) degraded”, “N agent(s) require an update” or “N agent(s) in critical state” | Okta reports that state for the agent | Fix or update the agent on the customer’s server. |
| “N agent(s) reporting healthy status” | All is well | Nothing. |
| “Agent health unknown”, “Status unavailable”, “Monitoring requires attention” or “Monitor execution failed” | The check could not be evaluated | Wait for the next check. Escalate if it continues. |
| “Monitoring disabled for this tenant” | Agent monitoring is off | Switch it on from the Edit page if you want it. |
Okta features in Tenant details
Section titled “Okta features in Tenant details”The Tenant details dialog on an Okta dashboard card lists the org’s enabled features. See Dashboard.
| What you see | Why | What to do |
|---|---|---|
| “Okta scope okta.features.read is required to list features.” | The integration lacks the scope | Authorise the integration in Okta again with that scope. |
| “Okta features were requested for this tenant moments ago. Try again in a minute.” | A short rate limit | Wait a minute. |
| “Okta features have not been loaded for this tenant yet. They appear here once a workspace member has opened this tenant.” | A viewer opened the dialog before any member or admin did | Ask a member or admin to open it once. |
| “Authentication required to load features.” | Your session expired | Sign in again. |
| “Unable to load features (HTTP <n>)” or “Unable to load features.” | An error | Try again. |
Topology and trial
Section titled “Topology and trial”| What you see | Why | What to do |
|---|---|---|
| “0 req/min” for one tenant | That tenant sent no events in the last 24 hours | Check the feed on the platform side. Send a test event. |
| “0 req/min” for every tenant | No events at all in 24 hours, or the traffic figures failed to load | Reload the page. Then check the Dashboard. |
| “AI service · Offline” | The Ask Alex service is not answering | See Ask Alex. |
| Banner Some tenants are not being monitored on this trial | Those Auth0 tenants were used in another trial | Choose Go to the Billing page and choose a plan, or contact Identiguard support. |