Repository navigation
400 error code while trying to update an onlineMeeting #3112
Description
Hello everyone,
I am facing an issue while trying to update an online meeting.
According to the official documentation, the allowParticipantsToChangeName andparticipants.organizer fields cannot be updated. Until a few days ago, setting those properties to null before sending the update request worked correctly, but recently Microsoft Graph started replying with a 400 Bad Request.
if (!ShouldCreate(meeting))
{
onlineMeeting.Participants.Organizer = null;
onlineMeeting.AllowParticipantsToChangeName = null;
}With response:
{"error":{"code":"InvalidArgument","message":"One or more properties do not support updating. Please refer to Microsoft Graph documentation for more information.","innerError":{"date":"2026-05-11T08:57:37","request-id":"6278bc77-d708-48ac-9876-b9aead4d90e9","client-request-id":"b7d68166-3049-410e-ac1b-c7890004155f"}}}Investigating futher the issue i logged the request body and started removing one by one the properties untill removing the @odata.type one it started working accordingly with a 200 status code. As a hotfix my team deployed a custom DelegatingHandler implementation to remove the subjected property but we consider this temporary and would appreciate guidance on a cleaner or officially supported solution.
Activity
Petri-X commentedon May 11, 2026
The same problem on here. Thanks Leonardo Baldazzi (@squirlyfoxy) for sharing this.
Based on our logs the issues started here in last week, around Wed - Fri.
MIchaelMainer commentedon May 11, 2026
This is likely a service issue. Can you confirm that you haven't made a client library update?
Petri-X commentedon May 12, 2026
Michael Mainer (@MIchaelMainer)
At least on our site, we have not made any changes to the code. Interesting is Microsoft support says this is Graph SDK issue.
squirlyfoxy commentedon May 12, 2026
Michael Mainer (@MIchaelMainer)
We use version 5.95, having the same issue updating to the latest 5.105
Luspin commentedon May 12, 2026
Michael Mainer (@MIchaelMainer) the same requests work when issued without leveraging the SDK (i.e. plain HTTP requests)