What each report contains
Each platform has its own report, because each platform has its own risks. This page lists every card you see when you open a report in the app, in the order it appears. Use it to choose which pages to show a client, and to explain the notes printed on the cards.
To open a report, see Read a report in the app.
An Okta report has a fixed shape. Most cards cover the last three monthly windows. The app shows 10 cards.
| Card | What it answers | Good to know |
|---|---|---|
| End user lifecycle | How many lifecycle, security, password and session events were there in each month? | Counts come from the Okta System Log. When a report is Partial or Failed, the reason appears in amber at the bottom of this card |
| International User Activity | Where in the world are people signing in from? | Successful sign-ins by country |
| System Log Activity | How much sign-in activity was there, and how healthy is the active user base? | |
| User Access Summary | How engaged are active users? | A snapshot from Okta user profiles. Needs the Okta scope okta.users.read |
| MFA Factors | Which factors are users enrolled in? | Enrolment by factor type. Needs the Okta scope okta.users.read |
| Suspicious Activity | What do the System Log indicators say about suspicious authentication and security events? | |
| Password Reset Failure Reasons | Why do password resets fail? | A breakdown of failure reasons |
| Platform Activity Highlights | Which applications do people sign in to most? | Application sign-ins |
| Directory Agent Health | Are the AD and LDAP agents healthy? | The latest agent monitoring summaries for the tenant. Needs agent monitoring to be set up |
| Directory Agent Inventory | Which agents exist, and are they up to date? | “Latest seen” is the highest agent version across the tenants that Identiguard monitors. Okta does not provide install dates |
Okta reports can be compared with an earlier report.
Notes on Okta cards
Section titled “Notes on Okta cards”| Note on the card | Meaning |
|---|---|
Okta scope okta.users.read is required to load factor enrollments. |
The Okta integration does not have the scope, so MFA Factors is empty |
Okta scope okta.users.read is required to populate the user access summary. |
The same scope is missing, so User Access Summary is empty |
| No agent monitoring configuration is available for this tenant. | AD and LDAP agent monitoring is not set up for the tenant, so Directory Agent Health is empty |
An Auth0 report covers the Reporting window you chose: 7 days, 30 days or 12 weeks. The 7 and 30 day windows are charted by day and 12 weeks by week. The app shows 8 cards.
| Card | What it answers | Good to know |
|---|---|---|
| Journey Success Rates | What share of login, registration and password reset requests succeed? | Taken from the log stream. Not an availability measure |
| Journey availability | Was each critical journey up? | Measured by synthetic probes that run the journey end to end. Needs Journeys |
| MFA Health | How often do MFA authentication and enrolment fail, for each factor? | |
| Password Reset Funnel | How many resets were requested, and how many were completed? | |
| Factor Usage Mix | Which factors do people really authenticate with? | Shares are by use, not by the number of users enrolled |
| Connections and Social | Which connections carry the sign-ins, and how many registrations came from a social provider? | |
| Attack Protection | How often did Auth0 attack protection act, and how often was the Management API rate limited? | |
| API Traffic | How many API requests did the tenant make? | Needs a metric stream. See Auth0 API metrics |
Notes on Auth0 cards
Section titled “Notes on Auth0 cards”A trainee must be able to explain each of these to a client.
| Note on the card | Meaning |
|---|---|
| Success rate is traffic-weighted and is not an availability measure. | The rate is calculated only from requests that happened. During an outage there is no traffic, so the rate does not fall. Use Journey availability for uptime |
| Availability is measured by Identiguard synthetic probes that run each journey end to end. It is not derived from Auth0 logs and is not a success rate. | This card answers “was it up?”. It is a different measure from the success rate and the two must not be mixed |
| Scores are not comparable across identity providers. | Do not put an Auth0 score next to an Okta or Entra ID score |
| Aggregates for the most recent days are still being built. | The newest days are not counted yet. The gap at the end of a chart is not zero traffic |
| * Current week in progress: N of 7 days aggregated so far. | The last point of a 12 week chart is a part week. A low value there is not a bad week |
| Building history: X of Y weeks (or days) | The tenant has less data than the window. The report shows what exists |
| Dotted connectors span days with no attempts: a success rate needs at least one attempt. | A dotted line joins days where nobody tried the journey. It is not data |
| Metric Streams is not enabled for this tenant. with the link Set up Metric Streams | The API Traffic card has no data because the tenant has no metric stream |
| Synthetic journey monitoring is off and Synthetic journey monitoring is not enabled for this tenant. | The Journey availability card has no data because journeys are not set up |
| Registration probes are coming soon. | There is no availability figure for registration |
| No grant type (not a token request) | In API Traffic, most requests are not token requests and so have no grant type. This is normal |
Microsoft Entra ID
Section titled “Microsoft Entra ID”An Entra ID report covers the Reporting window you chose: 7 days, 30 days or 12 weeks. The app shows 8 cards. Several of them have tables with pages of 10 rows.
| Card | What it answers | What it needs |
|---|---|---|
| Risk detections | What did Entra ID Protection flag in the period, by type and origin? | The risk detections stream, switched on for the tenant |
| Risky users | Which users were flagged in the period, and who is still at risk now? | The risky users stream. The current figures also need IdentityRiskyUser.Read.All |
| Sign-in failures | Which sign-ins did Conditional Access block, and which did Microsoft judge risky? | The sign-ins stream |
| Privileged changes | Which role assignments, federation settings and other privileged directory changes happened? | The directory audits stream |
| MFA coverage | How many member users can complete MFA, go passwordless or reset their own password? | Reports.Read.All or AuditLog.Read.All, and an Entra ID P1 or P2 licence |
| Conditional Access | Which policies exist, in which state, and is legacy authentication blocked? | Policy.Read.All |
| App credentials | Which application secrets and certificates have expired or expire within 90 days? | Application.Read.All or Directory.Read.All |
| Microsoft Secure Score | What is Microsoft’s own score for the tenant? | SecurityEvents.Read.All |
What gates each Entra ID section
Section titled “What gates each Entra ID section”There are two kinds of section.
Sections built from collected events. Risk detections, Risky users, Sign-in failures and Privileged changes are built from the events that Identiguard has already collected. They depend on the matching stream being switched on for the tenant, not directly on a permission. The stream needs its own permission to collect. Data exists only from the day the stream was switched on. For the streams and their permissions, see Connect Entra ID.
Sections read at report time. MFA coverage, Conditional Access, App credentials and Microsoft Secure Score are read from Microsoft Graph when the report runs. They depend on the permission in the table above. To see which are granted, open the tenant’s Edit page and look under Reporting permissions (optional).
Two figures inside a card have their own permission:
| Figure | Card | Needs | Without it |
|---|---|---|---|
| Global Administrator count | MFA coverage | RoleManagement.Read.Directory. RoleManagement.Read.All or Directory.Read.All also work |
The figure shows Not available with Needs RoleManagement.Read.Directory |
| Current risky users | Risky users | IdentityRiskyUser.Read.All |
Current risky users: Not available (IdentityRiskyUser.Read.All not granted). The figures for the period still appear |
“Not available” cards
Section titled ““Not available” cards”A section that the tenant cannot produce is not an error. The card shows Not available for this tenant: followed by the reason, and then a hint that says how to enable it. The rest of the report still completes, and the report is not marked Partial because of it.
| Reason on the card | Hint on the card |
|---|---|
| The risk detections stream is not enabled for this tenant. (also risky users, sign-ins, directory audits) | Enable risk detections on the tenant’s settings page. Events collect from then on. |
| Reports.Read.All has not been granted. (also Policy.Read.All, Application.Read.All, SecurityEvents.Read.All) | Add the permission to the app registration in the Entra admin centre, then grant admin consent. |
| This tenant is not licensed for this data (Entra ID P1 or higher). | Available once the tenant holds an Entra ID P1 or P2 licence. |
| Microsoft Graph refused the request (403). | Check the permission has admin consent in the Entra admin centre. |
To fix one, see Fix a “Not available” Entra ID section.
Notes on Entra ID cards
Section titled “Notes on Entra ID cards”| Note on the card | Meaning |
|---|---|
| Covers X of Y days, limited by event retention. | The window is longer than the events the workspace keeps. The figures cover fewer days than you chose |
| Covers X of Y days, limited by when monitoring started. | The stream was switched on part way through the window |
| Scan stopped early: the figures cover the users read before the report’s time budget ran out. (also applications, policies) | The directory is large and the report ran out of time. The figures are a part of the whole |
| Enabled, Report-only, Disabled | The three states of a Conditional Access policy. Report-only policies are evaluated but not enforced |
| Microsoft’s own measure. A reference figure, separate from the Identiguard secure score. | Microsoft Secure Score is Microsoft’s number. Do not confuse it with the Identiguard secure score |
Sections only in the PDF
Section titled “Sections only in the PDF”Each report has one monitoring section that is in the progress checklist and in the PDF, but has no card in the app.
| Provider | Section | What it answers |
|---|---|---|
| Auth0 | Log stream monitoring | Did events arrive without gaps? |
| Entra ID | Poll monitoring | Did Identiguard collect data without gaps? Needs no extra permission |
To read these, download the PDF.
Cards that were not collected
Section titled “Cards that were not collected”On an Auth0 or Entra ID report, a section that failed has a heading such as MFA health was not collected or Connections were not collected. Under it is the recorded error, or This report has no … section. when the run ended before the section. This is different from Not available: something went wrong, and the report is Partial or Failed. See Report statuses.
Choosing pages for a client
Section titled “Choosing pages for a client”| The client is worried about | Show |
|---|---|
| Account takeover | Okta Suspicious Activity and System Log Activity, Entra ID Risk detections, Auth0 Attack Protection |
| Weak MFA | The MFA card for their platform: MFA Factors, MFA Health or MFA coverage |
| Too many administrators | Entra ID Privileged changes and the Global Administrator count in MFA coverage, Okta User Access Summary |
| Customer sign-in experience | Auth0 Journey Success Rates and Journey availability |
| Expiring secrets | Entra ID App credentials |
| Platform hygiene | Okta Directory Agent Health and Directory Agent Inventory |
Troubleshooting
Section titled “Troubleshooting”Entra ID
Section titled “Entra ID”| What you see | Why | What to do |
|---|---|---|
| Not available for this tenant: The … stream is not enabled for this tenant. | The stream is off for the tenant | Open the tenant’s Edit page and switch the stream on. Events collect from then on, so a new report has data only from that day |
| Not available for this tenant: … has not been granted. | The Microsoft Graph permission is missing | Add the permission to the app registration in the Entra admin centre, then grant admin consent |
| Not available for this tenant: This tenant is not licensed for this data (Entra ID P1 or higher). | The tenant has no Entra ID P1 or P2 licence | The section is available when the tenant holds a P1 or P2 licence |
| Not available for this tenant: Microsoft Graph refused the request (403). | The permission has no admin consent | Grant admin consent in the Entra admin centre |
| Needs RoleManagement.Read.Directory | The permission for the Global Administrator count is missing | Add RoleManagement.Read.Directory and grant admin consent |
| Current risky users: Not available (IdentityRiskyUser.Read.All not granted). | The permission for the current figures is missing | Add IdentityRiskyUser.Read.All and grant admin consent |
| Scan stopped early: the figures cover the … read before the report’s time budget ran out. | A large directory, and the report reached its time limit | Treat the figures as partial. Generate the report again |
| Covers X of Y days, limited by event retention. | The window is longer than the event retention | Choose a shorter window, or raise retention. See Change retention and policies |
| Covers X of Y days, limited by when monitoring started. | The stream is newer than the window | Choose a shorter window, or wait |
| A heading that ends in was not collected or were not collected | The section failed, or the run ended before it | Generate again. If it repeats, check the permissions and the Microsoft Graph rate limits |
| What you see | Why | What to do |
|---|---|---|
| Metric Streams is not enabled for this tenant. | The tenant has no metric stream | Choose Set up Metric Streams. See Connect Auth0 |
| Synthetic journey monitoring is not enabled for this tenant. | Journeys are not set up | Set up journeys. See Manage journeys |
| Building history: X of Y weeks | A new tenant, with less data than the window | Expected. Generate again later |
| Aggregates for the most recent days are still being built. | The newest days are not counted yet | Expected. Generate again later |
| A heading that ends in was not collected or were not collected | The section failed, or the run ended before it | Generate again |
| What you see | Why | What to do |
|---|---|---|
Okta scope okta.users.read is required to load factor enrollments. |
The Okta integration does not have the scope | Authorise the Okta integration again with the scope. See Connect Okta |
Okta scope okta.users.read is required to populate the user access summary. |
Same cause | Same fix |
| No agent monitoring configuration is available for this tenant. | AD and LDAP agent monitoring is not set up for the tenant | Switch on agent monitoring for the tenant. See Managing tenants |
| Raw technical text in amber under End user lifecycle | The report is Partial or Failed, and this is the recorded reason for each section | Read which sections are named. If the text mentions a rate limit, generate again at a quieter time |