IdentityIQ Health Check Checklist for a New Customer

IdentityIQ (IIQ) IIQ Discussion and Questions
, , , ,
1

Hello everyone,

I have a question regarding SailPoint IdentityIQ health checks / environment reviews.

When working with a new customer (new logo), what are the key checks you usually perform to assess the overall health of the IdentityIQ environment and identify potential issues?

So far, my checklist includes:

  • Reviewing the Environment Report.
  • Identifying uncorrelated accounts (using reports or custom queries).
  • Checking failed tasks, understanding the root cause, and verifying that scheduled tasks are running as expected.
  • Reviewing workgroup memberships to ensure there are no inactive or leaver identities that still have administrative capabilities.
  • Verifying task schedules and looking for long-running or failed executions.

I’m sure there are many other important areas that experienced IIQ consultants review during a health check.

I’d really appreciate it if you could share your health check checklist or any lessons learned from customer assessments.

Thanks in advance!

2

Hi @IslamElkhouly - A few things you can add to the list:

  • Verify JVM settings are appropriate and consistent across servers.
  • Does the IQService version match the IIQ Version?
  • Verify any required E-fixes have been applied
  • Are there rules or workflows using any deprecated logging imports or system.out statements?
  • Evaluate the Role model for efficiency.
3

Hi @IslamElkhouly

Your checklist already covers many of the operational checks. A few additional areas I usually review during an IdentityIQ health assessment are:

  • Verify application aggregation health (failed, stale, or long-running aggregations).

  • Review Identity Refresh configuration and execution performance.

  • Check for failed or pending provisioning transactions.

  • Ensure maintenance tasks (TaskResult, Request Archive, Identity Archive) are running regularly.

  • Review custom rules and workflows for performance issues or deprecated APIs.

  • Check logs for recurring errors and make sure unnecessary debug logging is disabled.

  • Verify IQService versions, connector compatibility, and required patches/E-fixes.

These checks have helped me identify potential issues early and provide a better overall view of the IdentityIQ environment.