Microsoft Graph Explorer: ctrl-click to the next results raises error

Rik Vercauteren 11 Reputation points
2021-02-08T08:15:38.71+00:00

Hello,

testing following queries in Microsoft graph explorer :

https://graph.microsoft.com/v1.0/groups
or
https://graph.microsoft.com/v1.0/teams/

raises following error after skipping to the next page 65257-image.png after selecting the @odata.nextlink with <ctrl> - click.

{
"error": {
"code": "InvalidAuthenticationToken",
"message": "Access token is empty.",
"innerError": {
"date": "2021-02-08T07:57:46",
"request-id": "7aaa29d0-1cba-4d4a-bc25-f8a3b0e4769b",
"client-request-id": "7aaa29d0-1cba-4d4a-bc25-f8a3b0e4769b"
}
}
}

How can I fix this?

Kind regards,

Rik

Microsoft Teams Development
Microsoft Teams Development
Microsoft Teams: A Microsoft customizable chat-based workspace.Development: The process of researching, productizing, and refining new or existing technologies.
3,401 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
22,439 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Rik Vercauteren 11 Reputation points
    2021-02-12T17:06:56.203+00:00

    Hello, you can close this case.

    ctrl-click always results in an error.
    I needed to copy the odatalink for the next page in the query field of the graph explorer. That works fine for all the graph queries I tested. Except for the shifts query. For this issue i raised another question : https://learn.microsoft.com/en-us/answers/questions/266925/microssoft-graph-explore-raises-an-error-when-fetc.html

    1 person found this answer helpful.
    0 comments No comments

  2. Deva-MSFT 2,266 Reputation points Microsoft Employee
    2021-02-12T14:39:20.673+00:00

    Thanks for reporting the issue Rik. I tried repro the issue at my end, but i failed to repro it.
    Being said that i see the above error "Access token is empty", which tells that "No authorization header in request".

    So,

    • Please validate it before making the API call.
    • Logout from the Graph Explorer, clear the browser cache. Login into the Graph Explorer with credentials and now make the above Graph API call - observe still if you can repro the issue
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.