Forum Discussion
Issue with Teams 'Add a User to Group Chat' API call?
I am getting a very strange error when trying to add a new user to an existing group chat using a GraphQL call. I have looked through the documentation, asked AI, and even contacted Microsoft support and no one can seem to explain why this API call is failing.
Below is the API call that I am making. I can find no reason that I should be receiving the error message '#microsoft.graph.aadUserConversationMember'
To get the basic questions out of the way....
- Yes, the account making the API call DOES have permission to add users to the channel (and can do so using the frontend as normal.)
Yes, the thread in question is a group chat, so adding members to that chat should be a valid command. - Yes, ALL members in the group chat currently have the type '#microsoft.graph.aadUserConversationMember', so it is definitely a valid type for users in this channel.
- Yes, I have tried both the beta and stable channel; each gives the same error message.
- Yes, the invited user is internal to our organization, and is a valid target for the invite (invites work through frontend as well.)
- No, I cannot use the 'add member to channel' endpoint, because the chat is a group chat, not a channel.
I can only assume, at this point, that the error message is a red herring and there's something else wrong with my API call?Why am I receiving this error message when trying to add a member to a pre-existing group chat? Thanks in advance for any assistance.
POST to URL:
https://graph.microsoft.com/beta/chats/[[THREAD_ID]]@thread.v2/members
BODY:
{
"@odXXX.type": "#microsoft.graph.aadUserConversationMember",
"roles": [],
"email address removed for privacy reasons": "https://graph.microsoft.com/v1.0/users/[[USER_ID]]"
}
ERROR MESSAGE:
{"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odXXX.type' is not valid for this operation.","innerError":{"date":"2026-01-29T18:10:32","request-id":"<PII:moderator removed>","client-request-id":"<PII:moderator removed>"}}}
8 Replies
- TRUSTCopper Contributor
- AutomatonSolutionsRDECopper Contributor
Sayali, your response is incorrect. I am following the exact API call format specified by the documentation.
https://graph.microsoft.com/v1.0/chats/IDHERE/members
{
"chatType": "group",
"\u0040odata.type": "#microsoft.graph.aadUserConversationMember",
"user\u0040odata.bind": "https://graph.microsoft.com/v1.0/users/IDHERE",
"roles": []
}
- Sayali-MSFT
Microsoft
Hello AutomatonSolutionsRDE ,
Apologies for delay in response.
We are checking this with the internal team and get back to you once we get an update.
- Sayali-MSFT
Microsoft
Hello AutomatonSolutionsRDE,
The request fails due to two issues: first, the @odata.type value was misspelled, causing Microsoft Graph to stop processing and return a misleading schema error. Second, an incorrect property was used instead of user@odata.bind. Correcting both issues resolves the problem. The proper request body must include the correct @odata.type, roles array, and the user@odata.bind reference to the target user.{
"@odata.type": "#microsoft.graph.aadUserConversationMember",
"roles": [],
"user@odata.bind": "https://graph.microsoft.com/v1.0/users('USER_ID')"
}
- AutomatonSolutionsRDECopper Contributor
Sayali, this is not correct. There's nothing wrong with my API call, it's following the exact format you would expect. You are looking at artifacts of my copy/paste, but the API call follows the exact format in the documentation.
https://graph.microsoft.com/v1.0/chats/[[THREAD_ID]]/members
BODY:{
"chatType": "group",
"\u0040odata.type": "#microsoft.graph.aadUserConversationMember",
"user\u0040odata.bind": "https://graph.microsoft.com/v1.0/users/[[USER_ID]]",
"roles": []
}
- AutomatonSolutionsRDECopper Contributor
Incorrect. You are referring to changes I made to the post for security reasons. Here is a screenshot of the call being made:
This exactly follows the convention in the documentation. Why isn't it working? (https://learn.microsoft.com/en-us/graph/api/chat-post-members?view=graph-rest-1.0&tabs=http)
Please don't just ask an AI. The AIs all say the same identical thing and they're wrong. Can anyone ACTUALLY explain this?
Error Message:
{"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odata.type' is not valid for this operation.","innerError":{"date":"2026-02-10T17:59:50","request-id":"7b28c192-7906-40b1-94d7-dd3abb5577c3","client-request-id":"7b28c192-7906-40b1-94d7-dd3abb5577c3"}}} - AutomatonSolutionsRDECopper Contributor
Sayali, this is not correct. Apologies that my initial report was not more clear. This is the exact API call being sent, as you can see; the issues you pointed out are not present in the actual API call. it's following the correct format.
Response body:
{"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odata.type' is not valid for this operation.","innerError":{"date":"2026-01-29T14:56:25","request-id":"8ef444c8-64e3-45db-80d4-2c0ea9e47902","client-request-id":"8ef444c8-64e3-45db-80d4-2c0ea9e47902"}}}
PPlease advise.
- Sayali-MSFT
Microsoft
Hello AutomatonSolutionsRDE,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.