Update Inactive User Tracker for Hybrid Environments

What is a one sentence summary of your feature request?

Update the Inactive User Tracker to correlate Active Directory and Entra ID sign-in activity for hybrid users, providing a more complete and accurate determination of account inactivity.

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

In a hybrid Active Directory and Entra ID environment, user activity may occur through either on-premises AD or Entra ID. If the Inactive User Tracker only considers on-premises AD logon activity, it may not provide a complete picture of whether an account is actually active.

The Inactive User Tracker should incorporate Entra ID sign-in activity and correlate it with Active Directory logon activity for the same user account. The most recent activity from either source could then be considered when determining whether an account is inactive.

This would provide a more accurate view of user activity in hybrid environments and reduce the possibility of accounts being identified as inactive when the user is still actively authenticating through Entra ID.

How do you currently solve the challenges you have by not having this feature?

Currently, AD and Entra ID activity must be reviewed separately to determine whether an account is truly inactive. As a long-time Netwrix customer, we would expect the Inactive User Tracker to evolve to support hybrid environments by correlating activity across both AD and Entra ID. This would reduce the need for manual validation and provide a more complete and reliable view of user inactivity.

Hi Dave,

Thank you for the detailed write-up — this is a very fair point for hybrid environments.

Before we go further, could you tell us whether you specifically need this in the Inactive Users Tracker, or would a risk-based view also work for you? In Netwrix Auditor 10.9 we added this capability to Risk Assessment: the Inactive Users risk calculation now correlates logon activity from both on-premises Active Directory and Microsoft Entra ID, so users who authenticate only through cloud services are no longer flagged as inactive. You can find the details here: Hybrid Inactive User Risk: Active Directory and Entra ID Combined.

Could you take a look and let us know whether this covers your use case? If not — for example, if you rely on the Tracker’s automated actions such as disabling, moving or deleting inactive accounts, or on its notifications — please tell us what’s missing, and we’ll take it into account when evaluating this request.

Thanks again for the feedback!

Best regards,
Evgenii

1 Like

Hello! We rely on Tracker’s automated actions and notifications. Let me know if you have any additional questions. Thanks!

1 Like

Hi Dave,

Thanks for confirming — that makes the scope clear: the correlation needs to live in the Inactive User Tracker itself, so that its notifications and automated actions are based on combined AD and Entra ID activity.

At a high level, the approach we’re looking at is:

  • A new section in the Tracker settings to connect to your Entra ID tenant (application ID, client secret, tenant ID and cloud type), plus an option to choose which sign-in types should count as activity.
  • The Tracker collects users from Active Directory and from Entra ID, matches hybrid accounts between the two, and uses the most recent activity from either side to calculate the effective inactivity period.
  • Notifications and automated actions then work off that combined value. Actions such as disabling or moving accounts would still be performed in on-premises AD, with changes reaching Entra ID through your existing Entra Connect / Cloud Sync.

A few questions to make sure this fits your environment:

  1. Which Entra ID sign-ins should count as activity — interactive only, or non-interactive as well (e.g. token refreshes from mobile/Outlook clients)?
  2. Do you also have cloud-only accounts you’d expect the Tracker to cover, or only synchronized hybrid users? Note that acting on cloud-only accounts would mean performing actions directly in Entra ID rather than in AD, which requires write permissions in the tenant (e.g. User.ReadWrite.All) in addition to the read-only permissions mentioned below.
  3. Is your tenant in the global Microsoft cloud, or in a government/sovereign cloud?

Please note that reading sign-in activity requires an Entra ID P1 or P2 license and an app registration with User.Read.All and AuditLog.Read.All permissions.

No commitment on timing yet, but your answers will help us shape this correctly.

Best regards,
Evgenii