microsoftgraph / microsoftgraph/msgraph-sdk-python

me-token-to-replace not being replaced

Open
#1,271 0 comments 2 reactions 1 assignee View on GitHub

@ramsessanchez is already working on this.

Since May 18, 2026.

type:bug
Dominant language
Python
Stars
630
Forks
96
Avg merge
15h 20m
Merged PRs (30d)
3

Description

I am following the same tutorial as in #544 ( https://learn.microsoft.com/en-us/graph/tutorials/python?tabs=aad ) and getting the same error. As that issue is closed, I can't re-open it. The error is that the URL used in the ultimate request includes the path component me-token-to-replace:

https://graph.microsoft.com/v1.0//users/me-token-to-replace/mailFolders/inbox/messages?$orderby=receivedDateTime%20DESC&$select=from,isRead,receivedDateTime,subject&$top=25

And the error returned by the server is:

Response content: {"error":{"code":"ErrorInvalidUser","message":"The requested user 'me-token-to-replace' is invalid."}}

I would like to know if there has been any progress on solving this or workarounds? The ticket listed in the comments is still open and it was suggested it would be fixed more than a year ago. I have used both DeviceCodeCredential and InteractiveBrowserCredential with the same error.

One of the workarounds, using graph_client.users.by_user_id instead of graph_client.me might work except I can't hardcode the user_id in the long term.

If it makes any difference, I'm running on RHEL9, Python 3.9, msgraph sdk version 1.35.0 and all dependencies the latest versions downloaded as of today. Thanks for any help!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.