Hi @Prago, Ellen ,
From what I see in the explorer for me when I try to repo all results are same up to 8 :
Is this the same issue or is it for all order
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Per MS Graph documentation, A relevance score is used as a sort key, in relation to the other returned results. A higher relevance score value corresponds to a more relevant result. Relevance is determined by the user’s communication and collaboration patterns and business relationships."
From what we are seeing in the JSON responses, if I ask for the top 20 people related to me, the first 10 are not the same compared to if I asked for just 10 people.
Seems relevance score is not a true "order by" of data in the response. Anyone else seeing this?
https://graph.microsoft.com/v1.0/me/people?$select=displayName&$top=10 - gives 10 results
https://graph.microsoft.com/v1.0/me/people?$select=displayName&$top=20 - gives 20 results, but the first 10 are not the same people as top=10 list
Hi @Prago, Ellen ,
From what I see in the explorer for me when I try to repo all results are same up to 8 :
Is this the same issue or is it for all order
Hi @Prago, Ellen ,
Thanks for reaching out.
I can reproduce your issue in my test tenant. Executed the MS graph API: https://graph.microsoft.com/v1.0/me/people
with different values in $top query parameter and noticed the difference in order of people details from graph response.
I would recommend you to raise a support case with Microsoft Graph, a Support Engineer will be able to assist you better. You can raise support ticket from
http://aad.portal.azure.com/ or https://admin.microsoft.com/#/support/requests.
Hope this helps.
If the answer is helpful, please click Accept Answer and kindly upvote. If you have any further questions about this answer, please click Comment.