microsoftgraph / microsoftgraph/msgraph-sdk-dotnet

400 error code while trying to update an onlineMeeting

Open
#3,112 5 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Service issue
Dominant language
C#
Stars
789
Forks
264
Avg merge
15h 17m
Merged PRs (30d)
3

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.

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.

Research direction

Start by reproducing the onlineMeeting update from the C# snippet and inspect the logged request body, focusing on the @odata.type property. Check the SDK's request serialization path for this update and compare the result with the Microsoft Graph documentation. Done means the supported update succeeds without the custom DelegatingHandler workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.