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 have questions about Nintex Ideas, please contact

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact

Status Not Planned
Categories Connectors
Created by Guest
Created on Aug 18, 2021

Azure Active Directory Connector - Query User - Adding additional AD fields

Additional common Azure Active Directory Connector fields need to be pulled in for querying a users by such as Office. We are needing to use the Active Directory Query Users Control to pull emails for staff members based off their Office and Job Title. With this we have notice that with this control, we can query most of the basic fields in Azure AD other then Office. Adding this would help where multiple people have the same title but are in different office building.

This is based on a ticket (case 00404834) I put in about a month ago where the development team replied with ""according to Microsoft's documentation ( , those fields (mobilePhone, officeLocation, businessPhones, streetAddress, and postalCode) are considered as advanced queries, looking at the Active Directory Query Users action was built few years prior, those fields were excluded because of the API limitation at that time. So it would be a feature request to have those fields revisited."
  • Attach files
  • Admin
    Leigh Burke
    Jan 2, 2024

    Thank you very much for posting your feedback for our review. At this time, we will not be adding this request to the near-term backlog, as we are focused on other highly requested features. However, we reevaluate requests every quarter and will reach out if priorities change. Please keep the feedback coming as it is critical for our longer-term planning.

  • Gavin Adams
    Sep 7, 2022
    Hi Rick,
    while this is under review could we also consider the extension attributes. Even if they are not available to query if they could be returned in the result set
    That is extensionAttribute1 to extensionAttribute15

    From the advanced query link above that is in graph

    The extension attributes are used to many organisation to meet specific user metadata or custom application requirements. Being able to reference these in NWC would be awesome.