Active Directory reporting Answers for auditors, managers and your own team. Ready when they ask.

Seventy-eight built-in reports run over what Identity CORE has already collected, so they cost your directories nothing. Save one with its parameters, share it, put it on a schedule, and hand over the PDF.

  • 78 reports across identity, activity, data classification and what-if
  • What-if scenarios that show the effect of an account, group or permission change first
  • Saved, shared and scheduled reports with email notification, exported to PDF, Excel or CSV
Identity CORE / Reporting
The Identity CORE Reporting page on the Identity category: the report catalog down the left with Privileged Membership selected, its Domain and Expand nested groups parameters, the Run report and Save as buttons, and the result grid of sensitive-group members grouped by group with member type, SID, nesting depth, the group reached through, enabled state and last logon, with the format picker and Export button above it
78 built-in reports

Four categories, each written for the question behind it

Most identity and activity reports exist for Active Directory, Entra ID and Okta alike. Data classification reports cover the file servers.

Identity

29 reports

What the directory holds right now: inventory, posture and the accounts that need attention.

  • Stale Accounts. Users and computers that have not logged on for a number of days, or never
  • Privileged Membership. The members of the sensitive groups, nesting expanded
  • Dangerous Permissions. Directory permissions granting full control, access or owner changes, replication or password resets to non-privileged principals
  • Password Hygiene. Old, never-expiring, not-required, reversible, no-pre-authentication and DES-only passwords
  • Service Accounts And Delegation. Accounts with service principal names, delegation or a managed service account class
  • Entra Applications And Credentials. The secrets and certificates of app registrations and service principals, with their expiry
  • Entra Guests And External Users. The guest users, their invitation state and last sign-in
  • Security Posture. The open checks of the latest analysis of each domain, tenant and organization, with its score
  • Backup Coverage. Objects with and without a backup per class, and how old the backups are

Activity

29 reports

What happened, who did it and when, from the audit trail of each directory.

  • Changes By Actor. Who changed what in the period, with the changes made outside business hours
  • Privileged Membership Changes. Members added to and removed from the sensitive groups, directory roles or administrator privileges
  • Account Lifecycle. Accounts created, deleted, enabled, disabled, locked out, unlocked, and passwords reset or changed
  • Group Policy Changes. Changes to the policy containers and links, matched to the SYSVOL backups taken
  • Administrative Activity By Location. Who acted from which address, and whether the address is new
  • Failed Operations. The operations that did not succeed, with the reason
  • Monitored Object Detections. What the monitored objects evaluation found, how it was found and what was done
  • Operator Actions. What the operators did in the console, with success or failure

Data classification

13 reports

Which files on your Windows file servers hold personal data, and who can reach them.

  • PII Inventory. The files holding personal data, per server, share and type of data
  • Who Can Reach Sensitive Data. Who has access to files with sensitive data and how that access was granted
  • Open Access To Sensitive Data. Files holding personal data that Everyone, Authenticated Users or Domain Users can reach
  • Highest-Risk Files. The files with the most findings and the most kinds of them
  • Stale Sensitive Data. Files with findings not modified or accessed for years
  • Permission Boundaries. The folders whose permissions differ from their parent's, with the explicit entries
  • Share Inventory And Permissions. The shares with their size, contents and open access
  • Scan Coverage. Per server and share, the files catalogued, scanned, waiting and failed

What-if

7 reports

The consequences of a change you have not made yet, resolved across memberships, permissions and files.

  • Account Removal. If an account were disabled or deleted: groups left empty, objects only it can reach, orphaned permissions, service principal names
  • Group Removal. If a group were deleted: what its members would lose, the permission entries that name it and the policies it filters
  • Group Membership Change. If an account were added to or removed from a group: the memberships, privileges, objects and files it would gain or lose
  • Permission Change. If a permission were granted or revoked on a share, folder or object: who gains or loses access, and to which sensitive files
  • Clean-Up Policy Preview. If accounts inactive for N days were disabled: the accounts affected, with the service and privileged ones that need an exception
  • Rollback Preview. If an object were rolled back to a backup: the attributes that would change, with their current and backed-up values
  • Tenant Policy Scope. Who and what a Conditional Access policy includes and excludes, resolved against the tenant, to judge the effect of enabling it
Running a report

Pick it, set the parameters, read the answer

Every report has the parameters that make sense for it: the domain or tenant, a period, a threshold in days, an account or group name, a minimum score. Run it and the result fills the grid as soon as it is ready, with a chart where the report carries one.

Reports run against the data Identity CORE has already collected, never against a live directory, tenant or file server. A report that would have been a scripted query against production is now a click with no load on the directory.

A row that names a file opens its details: properties, who can reach it, the findings in it and its duplicates. Recent runs of each report are kept, so last week's answer is still there to compare.

Identity CORE / Reporting / Report result
A report result in Identity CORE Reporting: the File Type Distribution report from the Data Classification category with a Files by Extension donut chart beside the result grid of files and bytes per server and extension, the Server and Include deleted parameters above, and the format picker and Export button
Identity CORE / Reporting / What-if
The What If category in Identity CORE Reporting with the Account Removal report run for an administrator account: rows for each privileged group that would be left empty or lose a member and a share permission entry that would become an orphan, with kind, name, path, scope, rights and detail columns
What-if scenarios

Know what a change would do before you make it

What-if reports resolve memberships and permissions across the directory and the file servers to answer the question every administrator asks before touching a group: what breaks?

  • Account Removal Groups left empty, objects only that account can reach, orphaned permission entries, service principal names, and what it manages
  • Group Removal and Group Membership Change What members would lose, what an account would gain or lose: memberships, privileges, objects and files
  • Permission Change Who gains or loses access when a right is granted or revoked, down to the sensitive files it reaches
  • Clean-Up Policy Preview The accounts a disable-after-N-days policy would catch, with the service and privileged accounts that need an exception
  • Rollback Preview The attributes a rollback would change, with their current and backed-up values side by side
  • Tenant Policy Scope Who a Conditional Access policy would include and exclude, resolved against the tenant's real users, groups and applications
Saved and scheduled

Set it up once. Have it land in the inbox every Monday.

Save a report with its parameters under a name of your own. Share it so colleagues run the same report the same way, give it a schedule, and choose who is told by email when a run finishes. Runs are kept for the retention you set on the saved report.

A scheduled report runs under its owner's name with the owner's permissions, so a shared report never shows someone more than they are allowed to see.

Share Colleagues see the saved report in their catalog and run it with the same parameters.
Schedule On the schedule you set, like any other job in Identity CORE.
Notify Email when a run finishes, with the outcome and a link to the result.
Identity CORE / Reporting / Save report
Identity CORE / PDF export
The first page of a Stale Accounts report exported from Identity CORE as a PDF: the Identity CORE header, the report title and description, the source, row count and who ran it, the Domain, Days, Account type and Include disabled accounts parameters, then the first rows of the table with name, domain, account name, object type, distinguished name, last logon, password last set, enabled and days inactive
Operations

Reports on Identity CORE itself, and notifications that say what matters

A platform that watches your directories has to be watchable too. Operational reports cover the agents and components with when they were last seen, every job run with its outcome and duration, the backup sets and recoveries, every notification queued, sent or failed, and everything the operators did.

Notifications go out when a job finishes, a monitored object rule fires, an analysis completes or a scheduled report is ready. Each one carries what matters: the score and the costliest open indicators, the backups needing attention, the changes found and who made them.

  • Agent And Component Health
  • Job Execution
  • Forest Backups And Recoveries
  • Notification Delivery
  • Operator Actions
  • Monitored Object Detections
  • Scan Coverage
  • Tagged Objects
Identity CORE / Home
The Identity CORE home page showing the Active Directory dashboard for one domain: the security analysis panel with the exposure health score, per-category scores and a score trend chart, count cards for users, computers, domain controllers, never-logged-on accounts and old passwords, the directory objects breakdown by type, and user, group and computer overview panels, with collapsed Entra and Okta dashboards below

Common Questions

Do reports put load on my domain controllers or tenants?

No. Every report runs over the data Identity CORE has already collected and stored. Nothing contacts a directory, a tenant or a file server when a report runs.

Can I build my own report?

Not in the console today. The catalog is deliberately curated, and most requests turn out to be a built-in report with different parameters. If one is missing, tell us: the catalog grows with every release. You can specify the parameters for a built-in report and save that to run on a schedule and deliver results via email.

Who can see what in a shared report?

Role-based access applies to reports like everything else. Data classification reports that reveal personal data need the sensitive data role, and a scheduled report runs with its owner's permissions.

What formats can I export?

CSV, Excel and PDF from every report. The PDF carries the title, description, run details, parameters and chart on the first page, then the rows with a repeating header, portrait or landscape to fit the columns.

See the report your auditor asked for last quarter

Book a demo and bring the question. We will run the report that answers it.

An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.