This is an interesting search query you have build. What Sandilya pointed out is important, sometimes typo does happen. I believe nonHumanIdentity is a custom identity attribute that holds string value. If there are multiple sources with name containing “Active Directory“, use below query: -
attributes.nonHumanIdentity:“true” AND @accounts(source.name.exact:“Active Directory” AND disabled:false)
Here, the keywork exact plays an important role. If you are not getting all the results expected, just run the same query after an identity refresh, this would help bring identities that had recently manually correlated to show up in search results.
Results I would also expect from query: attributes.nonHumanIdentity:“true” AND @accounts(source.name.exact:“Active Directory” AND disabled:false) are identities who has the string value true for custom identity attribute: nonHumanIdentity and atleast an active/enabled account in source named exactly “Active Directory”.
I am suspecting data issue here.
When we create a custom identity attribute in one Identity Profile it is automatically available in other Identity Profiles as well. Do you have multiple identity profiles?
Suggestion to validate data: download search results of both below queries and look up accounts and identity attribute: nonHumanIdentity of a few identities who are not in both the downloaded reports: -
attributes.nonHumanIdentity:“true”
attributes.nonHumanIdentity:“true” AND @accounts(source.name.exact:“Active Directory” AND disabled:false)