Enhancement Request: Support for Multiple Conditions Queries in Microsoft Graph API Messages Endpoint

The request concerns Microsoft Graph's messages endpoint and proposes combining date and recipient conditions while retaining count support. No repository file, entry point, or test is identified, and the requested capability appears to require an upstream API change rather than a defined SDK change.

Feature Request

Is your feature request related to a problem? Please describe

Currently, there is a limitation in the Microsoft Graph API where querying messages based on multiple conditions, such as messages received during a specific period and sent to a specific address, can be challenging.

Describe the solution you'd like

I would like to request an enhancement to the Microsoft Graph API that allows for more flexible and efficient querying of messages based on multiple conditions. Specifically, I would like to see the ability to perform queries like the following example:
https://graph.microsoft.com/v1.0/me/messages?$(filter=ReceivedDateTime ge 2023-06-01 and ReceivedDateTime le 2023-06-19 and ('c.ivanov@companyname.com' in toRecipients))
This would enable users to filter messages based on both date ranges and specific recipient addresses in a single query.

Describe alternatives you've considered

Currently, the only alternative to achieve this is to use the $search parameter, as shown in the following example:
https://graph.microsoft.com/v1.0/me/messages?$search="to:o.ivanova@companyname.com AND received>=2023-06-01 AND received<=2023-06-19"
However, using $search does not allow for the use of $count=true to determine the quantity of emails that fit the specified requirements. As a workaround, users may need to retrieve a limited set of fields (e.g., $select=id) and calculate the length of the returned JSON to approximate the count.

Additional context

The ability to perform multiple conditions queries in a single request would greatly enhance the usability and efficiency of the Microsoft Graph API for users who need to filter messages based on complex criteria. This feature would provide more flexibility and reduce the need for workarounds to achieve the desired results.