Microsoft Graph API 搜索 function 无法按预期工作

Question

I am trying to do a basic search for displayName of my organization using the Microsoft Graph API.

The problem is, the search function doesn't work as expected. Based on my tests the search function doesn't actually do fuzzy searching properly, the logic is obviously based on startsWith and endsWith and not contains. For my needs this doesn't suffice because my organization's displayName contains both Korean name and English name. For example:

A user with displayName: 이선빈(Annie Lee)

https://graph.microsoft.com/v1.0/users/?$search="displayName:이선" returns the correct result. https://graph.microsoft.com/v1.0/users/?$search="displayName:Annie" returns no result. https://graph.microsoft.com/v1.0/users/?$search="displayName:Lee" returns no result https://graph.microsoft.com/v1.0/users/?$search="displayName:Lee )" returns the correct result

What was the point of updating the API with the search function if actual fuzzy searching wasn't supported? $filter using startsWith and endsWith operator has been supported since the beginning, but the reason why people wanted the $search function was to be able to actually query for displayName properly using a contains function. It seems Microsoft essentially "added" a search function when functionally it's basically the $filter with startsWith and endsWith query.

Am I missing something with the API? Is there a possible workaround in my case?

Answer 1

I'm the PM for the Advanced Query Parameters .
$search tokenization considers the parenthesis character ( as a token delimiter, so 이선빈(Annie Lee) is split into these tokens:

 - 이선빈
 - (
 - Annie
 - Lee
 - )

It is very weird that your queries searching for "Annie" or "Lee" do not return any result. We tried on our end, and we cannot repro.
Can you share the request-id for your failed search to help us debugging this issue?

Note : we cannot implement a "true" contains algorithm due to performance reasons, we believe that tokenization search is the best compromise.

PS: we updated the documentation to highlight your specific case: https://docs.microsoft.com/en-us/graph/search-query-parameter#using-search-on-directory-object-collections

Answer 2

Thanks for the clarification in your last comment.
You can solve the issue by taking advantage of $search behavior for non-tokenized properties: it will default to startsWith operator.

Your final query should look like this:
/users?$search="displayName:<INPUT>" OR "givenName:<INPUT>" OR "surname:<INPUT>"

Let me know if this works for you.