Fixed: In Exchange Hybrid scenario Microsoft Graph REST API query fails due to $select $top $skips commands ignored

Recently i was working with an app developer who’s using Microsoft Graph REST API in their application. They try to query contacts for Exchange 2016 CU5 on premises in a hybrid + Office 365 environment (they had one single mailbox setup in Office 365).

When they tested the Graph API query with $select, $top, $skips commands they lead to failure. Here is the related query:$select=displayName,emailAddresses,id&$top=2&$skip=0

I tested the query against my Office 365 account and it works. But on Hybrid scenario (Exchange 2016 on premises + Office 365) account it completely ignores the $select $top $skip commands, returns all contacts instead of just the top 2 and doesn't filter out the data like it should.

In addition, we see Status code 200 when we ran the same query from Office 365 GraphExplorer (for the same scenario):

Le Café Central de DeVa - Deva blogs

Based on this, we worked internally, investigated, fixed and it was rolled out. The issue is fixed now Smile

So now you can test the above Microsoft Graph API query in Hybrid (Office 365 + Exchange Server 2016 CU5) scenario and it works as expected.

Comments (6)
  1. Mikelasy says:

    This information very helpful for work and the gain the information.
    Thank you

    1. Deva [MSFT] says:

      Thanks for the feedback. Glad that the article helped 🙂

  2. AmiSmiled says:

    Glad the issue is fixed now..!!

  3. 賓果賓果app says:

    I have been exploring for a little bit for any high quality articles or weblog posts in this kind of house . Exploring in Yahoo I at last stumbled upon this website. Studying this info So i am glad to convey that I have a very good uncanny feeling I discovered exactly what I needed. I so much undoubtedly will make certain to do not forget this web site and give it a glance on a constant basis. Keep the good work Deva!!

    1. Deva [MSFT] says:

      Thanks for your compliments. Glad the post/site helped 🙂

Comments are closed.

Skip to main content