Just ran into this today... sure looks like jamf needs to tweak the graph API query they're using here. Came across this post when researching the error:  https://docs.microsoft.com/en-us/answers/questions/577870/filtering-on-onpremisessamaccountname-is-not-worki.html

Reproducing the jamf graph query in graph explorer results in the same error, adding the mentioned headers and count variable make the search completely successfully - it looks like searching on onpremisessamaccountname turns this into an advanced query, requiring the extra headers and $count=true that jamf doesn't currently appear to be sending to graph.

Hi @abremel 

Thanks for the explanation.
So far Jamf still hasn't solved the problem.

My last reply from support was that it's now an open product issue, but as is standard with those... no ETA.

From support: "This is a open Product Issue, PI103710. Currently the only workaround is to use different username mapping. "

Ok thank you for this information.
I had just created a Support ticket....

If it's a Product Issue that's already open, all we have to do is wait.

Thank you

Hello,

I see that PI103710 still exists and yet I notice that now I am able to search Users and Groups with the onPremisesSamAccountName attribute (instead of userPrincipalName) in User Name mapping.

Do you know if it's solved by Jamf or if it's a change on the Microsoft side?

Thanks