Advanced query capabilities not working in Microsoft Graph API

Question

Hello

Following this documentation:
https://learn.microsoft.com/en-us/graph/aad-advanced-queries

However, the examples don't work in Graph API Explorer. When trying you always get response with error code "Request_UnsupportedQuery".

Example:

GET https://graph.microsoft.com/v1.0/users?$filter=accountEnabled ne true&$count=true  
ConsistencyLevel: eventual  
  
{  
   "error": {  
      "code": "Request_UnsupportedQuery",  
      "message": "Unsupported property filter clause operator 'NotEqualsMatch'.",  
      "innerError": {  
      "date": "2021-09-01T08:49:09",  
      "request-id": "42eae13b-0c60-4d1f-bd07-dced22f788d3",  
      "client-request-id": "42eae13b-0c60-4d1f-bd07-dced22f788d3"  
   }  
}  

Thanks,
Roger

Answer 1

You are right. "Unsupported property filter clause operator 'NotEqualsMatch'." happens when you call MS Graph users without a signed in user on Graph Explorer. GET https://graph.microsoft.com/v1.0/users?$filter=accountEnabled ne true&$count=true with Header ConsistencyLevel: eventual should work with signed users and right permissions.

However, the query operators are not fully supported on all resource properties. As for endsWith(DisplayName,'vasil') this does not work because as per Advanced query capabilities on Azure AD directory objects support for filters, quoting:

The endsWith operator is supported only with advanced queries on mail and userPrincipalName properties.

Answer 2

To resolve the issue, you can include the ConsistencyLevel: eventual attribute in the header of your request. This attribute ensures that your query is executed with eventual consistency, which can be particularly helpful in cases where the data might not be immediately consistent across all replicas.

In .NET, you can achieve this by creating an HttpRequestMessage object and adding the ConsistencyLevel header before sending the request. Here's an example:

csharpCopy code
HttpRequestMessage request = 

By including this header attribute, you can potentially mitigate errors related to unsupported filter operators, as it ensures a consistent behavior in retrieving data from the Microsoft Graph API.