Skip to content

Status and advisories

When an identity platform has an outage, the first question is “is it us or them?” Identiguard shows each provider’s status and security advisories in the sidebar, so the answer is one click away.

These pages are available on every plan. Admins, members and viewers can all open them. Nothing on these pages can be edited.

A platform operator switches each row on for the workspace. There is one switch for the two Okta rows together, and a separate switch for each of Entra ID status, Entra ID advisories, Auth0 status and Auth0 advisories. A row that is switched off does not appear in the sidebar.

Under Security & monitoring, each provider has a status row and an advisories row. Each row has a small coloured icon on its right edge.

Icon Label On which rows When
Red octagon active incident Status rows The provider’s feed has at least one current incident
Amber triangle security advisory Advisories rows An advisory rated critical or high was published in the last 30 days
Green tick operational All rows The feed has loaded and none of the conditions above apply
Dashed circle status unknown All rows The feed has not loaded yet
Grey triangle no tenant connected Entra ID status only The workspace has no Entra ID tenant

Good to know:

  • Planned maintenance never turns a light red.
  • An advisories row is amber only for critical and high advisories from the last 30 days. Older or lower advisories leave it green.
  • For Okta and Auth0, the severity is worked out by Identiguard from words in the advisory text. It is not the vendor’s own rating. See How severity is decided.
  • The grey triangle exists only on the Entra ID status row. The Okta and Auth0 rows show their lights even when the workspace has no tenant of that provider.
  • The labels are the icon’s accessible name. It is not confirmed that every browser shows them as a tooltip when you hover.
Sidebar row Page title Source
Okta status Okta Service Status Okta’s status feed
Auth0 status Auth0 Service Status Auth0’s status page
Entra ID status Microsoft Entra Service Status Microsoft Graph service health, for each connected Entra ID tenant
Element What it is
Refresh Loads the latest data. The page does not refresh by itself. Data loads when you open the page and when you choose Refresh
Overview card All Systems Operational (green) or Service Issues Detected (amber), with Last updated: and the time
Overview text With incidents: There are currently N active incident(s) affecting … services. Without: All … services are operating normally. No current incidents reported.
Current Incidents One card for each open incident. Shown only when there is at least one
Recent Resolved Incidents Up to 10 resolved incidents. With none: No recent incidents to display.

Each incident card shows the title, a status chip, an external-link icon that opens the vendor’s own incident page in a new tab, the time (Updated: or Resolved:), and the start of the vendor’s text. The text is cut at 300 characters for current incidents and 200 characters for resolved ones. Use the external-link icon to read all of it.

Chip Colour
Investigating, Identified, Notice Red
Analysis, Monitoring, Mitigated, Degraded Dark
Maintenance Blue
Resolved, Completed, Closed, Operational, Informational Grey

The Okta page shows the overview card, Current Incidents and Recent Resolved Incidents. It has no Status page button and no maintenance section.

An Okta incident that has had no update for 45 days is treated as resolved, even if Okta has not closed it.

The Auth0 page has two extra parts.

  • Status page button: opens status.auth0.com in a new tab.
  • Regions card (Per-region status and 90-day uptime): one row for each Auth0 region.
On a region row Meaning
Uptime and a figure The region’s uptime over 90 days, as Auth0 publishes it
Operational or Degraded The region’s state now
Auth affected (red) A current incident affects authentication in that region
Maintenance (blue) Maintenance is scheduled for that region

Always check the region the client’s Auth0 tenant is in. An incident in another region does not affect them.

The Entra ID page has two extra parts.

  • Status page button: opens service health in the Microsoft 365 admin centre in a new tab. You need a Microsoft admin account to read it.
  • Tenants card (Identity Service health per Entra tenant): one row for each Entra ID tenant in the workspace.
Chip on a tenant row Meaning
Operational Microsoft reports the identity service as healthy for this tenant
Degraded Microsoft reports an identity service problem for this tenant
Checking Identiguard is still fetching the health for this tenant
Permission required Identiguard cannot read service health for this tenant

Entra ID service health is kept for 5 minutes for each tenant, so Refresh can show the same answer for up to 5 minutes.

If the workspace has no Entra ID tenant, the page shows No Microsoft Entra tenants are configured in this workspace.

On the Auth0 and Entra ID pages, planned work has its own blue section, Planned Maintenance. The overview card adds the line N planned maintenance window(s) announced. Planned work does not count as a service issue. Planned maintenance does not change the overview to Service Issues Detected and does not turn the sidebar light red.

Entra ID status needs the Microsoft Graph application permission ServiceHealth.Read.All on the tenant’s app registration. Without it, the page shows the warning card Service-health permission not granted, which names the tenants, and each of those tenants has the chip Permission required. The same warning appears when the credentials stored for the tenant are incomplete.

  1. In the Entra admin centre, open the app registration that Identiguard uses for the tenant.
  2. Open API permissions and add the Microsoft Graph application permission ServiceHealth.Read.All.
  3. Choose Grant admin consent.
  4. In Identiguard, open Entra ID status and choose Refresh.

The chip can read Checking or Permission required for up to 5 minutes. Choose Refresh again after that. It then reads Operational or Degraded. For the app registration itself, see Connect Entra ID.

When a provider reports an incident that affects a tenant, the tenant’s card on the dashboard shows a banner. See Dashboard.

Use this when users report sign-in problems and you need to know if the provider is the cause.

  1. In the sidebar, under Security & monitoring, look at the light beside the provider’s status row. A red octagon means the provider reports a current incident.
  2. Open the row. Read the overview card: All Systems Operational or Service Issues Detected.
  3. Choose Refresh to be sure you have the latest data.
  4. Read Current Incidents. Check the chip and the time on each one.
  5. Check that the incident applies to this client:
    • Auth0: find the client’s region in Regions and look for Auth affected or Degraded.
    • Entra ID: find the client’s tenant in Tenants and read its chip.
  6. For the full vendor text, choose the external-link icon on the incident, or Status page on the Auth0 and Entra ID pages.

If the provider is green and users still cannot sign in, the cause is more likely in the client’s own configuration. Continue in Events and Incidents.

Sidebar row Page title Source
Okta advisories Okta Security Advisories Okta’s security advisories feed
Auth0 advisories Auth0 Security Advisories The same Okta security feed, filtered to advisories that mention Auth0. Auth0 advisories are rare
Entra ID advisories Microsoft Entra Security Advisories The Microsoft Security Response Center (MSRC) feed, filtered to identity topics: Entra, Azure AD, Active Directory, identity, and the Microsoft authentication libraries
Element What it is
Refresh Loads the latest data. The page does not refresh by itself
Security advisory overview N security advisories available • M resolved updates • Latest: and a date
Year groups Advisories are grouped by year, with a badge such as 12 advisories
Advisory card Title, Published: and the date, chips, an external-link icon to the full advisory, and the start of the description

Chips on an advisory card:

Chip Values
Status advisory or resolved
Severity low, medium, high or critical
CVE Shown when the advisory names at least one CVE. Each CVE number then has its own chip under the description

Limits:

  • A page shows at most 50 advisories.
  • The description is cut at 400 characters. Use the external-link icon for the full text.
  • There is no search, filter or sort.

For Okta and Auth0, Identiguard reads the title and description and picks the severity from the words it finds:

Words in the advisory Severity shown
“critical” or “severe” critical
“high” or “important” high
“medium” or “moderate” medium
None of these low

This is not a vendor rating. Always open the advisory and read the vendor’s own assessment before you advise a client. The resolved status is decided in the same way, from words in the text.

How the severity of Entra ID advisories is decided is not confirmed. Treat it in the same way: read the Microsoft advisory itself.

  1. Open the provider’s advisories row in the sidebar.
  2. Read the overview line: how many advisories, how many are resolved, and the date of the latest one.
  3. In the current year, look for critical or high chips on advisories that are still marked advisory and not resolved.
  4. Choose the external-link icon to read the full advisory.
  5. Note the CVE numbers for the client’s vulnerability tracker.

When you open Ask Alex on a status page, Alex knows what the page shows: whether there are active incidents, how many current and resolved incidents and planned maintenance windows there are, and how many regions or tenants are listed.

Open a status page and say: “Your team does not need to remember where each vendor publishes this. It is beside your own events.”

What you see Why What to do
Auth0 Trust is disabled or access denied or Microsoft Entra Trust is disabled or access denied The row is switched off for the workspace, or you are not a member of the workspace Ask a platform operator to switch it on
Access denied on the Okta status page Same cause, for Okta Same fix
Authentication required Your session expired Sign in again
Failed to fetch Okta status, Failed to fetch Auth0 status or Failed to fetch Microsoft Entra status The vendor’s feed could not be reached, or it returned an error Choose Refresh. On Auth0 and Entra ID, choose Status page to check with the vendor directly
Unable to load Okta status (or Auth0, Microsoft Entra) A network error between your browser and Identiguard Check your connection and choose Refresh
Service-health permission not granted, with the chip Permission required ServiceHealth.Read.All is missing or has no admin consent, or the credentials stored for the tenant are incomplete Follow Enable Entra ID status for a tenant. If the permission is already granted, re-enter the credentials. See Rotate credentials
Chip Checking The health for that tenant is still being fetched Wait a moment, then choose Refresh
No Microsoft Entra tenants are configured in this workspace. No Entra ID tenant is connected Connect one. See Connect Entra ID
Grey triangle, no tenant connected, on Entra ID status No Entra ID tenant is connected Expected. Nothing to fix unless the client uses Entra ID
Dashed circle, status unknown The feed has not loaded yet, or it failed to load Wait, or reload the page
No recent incidents to display. The vendor’s feed has no resolved incidents Nothing to do
A status or advisories row is missing from the sidebar The row is switched off for the workspace Ask a platform operator to switch it on
The light is green but the vendor’s own page shows planned work Planned maintenance is not counted as an incident Expected. Read the Planned Maintenance section
An old Okta incident moved to Recent Resolved Incidents although Okta did not close it It had no update for 45 days Expected
What you see Why What to do
Auth0 advisories are disabled or access denied or Microsoft Entra advisories are disabled or access denied The row is switched off for the workspace, or you are not a member of the workspace Ask a platform operator to switch it on
Access denied on the Okta advisories page Same cause, for Okta Same fix
Authentication required Your session expired Sign in again
Failed to fetch security advisories The vendor’s feed could not be reached, or it returned an error Choose Refresh
Unable to load security advisories A network error between your browser and Identiguard Check your connection and choose Refresh
No security advisories available. The Okta feed returned nothing Choose Refresh
No Auth0-specific advisories published. Auth0 advisories are sourced from Okta Security and are rare. Nothing in the Okta security feed mentions Auth0 Nothing to do
No identity-related Microsoft advisories in the current MSRC feed. No MSRC item matches the identity topics Nothing to do
The advisories light stays green although there are advisories None is rated critical or high and published in the last 30 days Expected
The severity chip does not match the vendor’s rating For Okta and Auth0 the severity is taken from words in the text Use the vendor’s rating. See How severity is decided