Skip to Main Content
Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!

If you are looking for the Nintex roadmap, you can find that on Nintex Community

If you have questions about Nintex Ideas, please contact

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact

Categories Workflow Designer
Created by Brandi Woodson
Created on Jun 24, 2023

Please improve and add to conditions to QUERY USERS action for AD

Query users is limited to 999 users.

Please remove the limit AND enhance the condition operators.

At present, we can only filter with begins with or equals to (both ignoring case), however the limited conditions make it extremely difficult to use this action when we have 58k+ enabled accounts and need to ignore some that are flagged how we have structured them for test accounts, service accounts, guests etc.

Need the following operator options for conditions:

  • Ability to filter by empty or null fields

  • Ability to filter by does not start with

  • Ability to filter by does not equal to

  • Ability to filter by contains

  • Ability to filter by contains (ignore cases)

  • Ability to filter by group user is part of - the "get members of an azure active directory" action doesn't have the level of user details when looping through what we need.

  • Ability to filter by user type, that field isn't even available! This is how we differentiate guests from members (employees). It would be helpful to identify which users are GUESTS!!!

It's making workflows difficult to manage as well due to the 1k loop limit and the 10k workflow iterations per workflow and the 10k limit for instances per hour restriction. We need to break down groups to add them to NAC User Management but can't with the limited restrictions.

Because we have to STRIP back the UPN (display name/username) for guest accounts just to obtain a first and last name (our first and last name fields are blank for guest accounts), the iterations are stacking up quick! We also have to check for email, and if email field is blank, use username for email variable. It would be more sufficient if we could remove the need for all the actions in our workflow just to get a first and last name and use the conditions to reduce the scenarios we are using at present.

Our only option at the moment is running through 676 condition scenarios using the alphabet (e.g; begins with aa, ab, ac, ad, ae etc.) to reduce the returned results for us to loop through and clean up before firing off another component workflow to add users to NAC.

I'm only on AJ and have to get EVERYONE in our AD added to NAC which is 58k+ users - very annoyed.

  • Attach files