Showing results for 
Search instead for 
Did you mean: 
Advocate I
Advocate I

Office365Users.SearchUser() Search by location/department/jobtitle

if I use  Office365Users.SearchUser({searchTerm:TextInput1.Text,top:500}) , it will only search by user name. Is there a way to search all other fields as well.

e.g. If type in Marketing in the textinput field, the gallery will return everyone from marketing department.

Community Support
Community Support

Hi @agent3154,


According to


Search for users: Retrieves search results of user profiles

Input properties

Name Data Type Required Description
searchTerm string no Search string. Applies to: display name, given name, surname, mail, mail nickname, and user principal name

Output properties

Property Name Type Description
Department string Department of the user.
DisplayName string Display name of user.
GivenName string Given name of user.
Id string User id
JobTitle string Job Title of the user.
Mail string Email id of user.
MailNickname string Nickname of user.
Surname string Surname of user.
TelephoneNumber string Telephone number of user.
UserPrincipalName string User Principal Name.
AccountEnabled boolean Account enabled flag.


But in my App, I had a connection to Office 365 Users, and I inserted a Text box and set its Text property to show information about current user, for example: Office365Users.MyProfile().DisplayName, it worked well and user DisplayName was shown. When I set its Text property to show user Department, I got the same issue with you, no error message and no user Department information was shown. And I also tried to show information about another user, I can also get information about DisplayName, ID, etc. but I can’t get Department information.


It is a limitation of the connector. The Microsoft Graph API supports filtering on department, but it is not exposed by the connector. We are currently working on a fix. 




Community Support Team _ Mona Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

I'm looking for a similar solution.  I'm looking to generate gallaries of all employees of a specific JobTitle, Department, or Location.

In this Casse the Office365Users.SearchUser() Connector is not reliable in Tenants with more then 999 Users, because the filter on JobTitle, Department or Location is established after the top:999 User Limit. No Pagination in Batches possible with this Connector. So the filters on JobTitle, Department or Location are not delegable. Suboptimal Connector Design.... 

Helpful resources

News & Announcements

Community Blog

Stay up tp date on the latest blogs and activities in the community News & Announcements.

Power Apps Community Call

Power Apps Community Call- January

Mark your calendars and join us for the next Power Apps Community Call on January 20th, 8a PST

PP Bootcamp Carousel

Global Power Platform Bootcamp

Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.


Power Platform Community Conference On Demand

Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!

Top Solution Authors
Top Kudoed Authors
Users online (6,637)