microsoftgraph / microsoftgraph/msgraph-sdk-java

Error in PATCH onlineMeeting

Open
#2,589 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status:waiting-for-triage type:bug
Dominant language
Java
Stars
444
Forks
154
Avg merge
18h 28m
Merged PRs (30d)
4

Description

Describe the bug

Hello,
I have integrated microsoft graph sdk to programmatically manage onlineMeetings. Since a couple of days I am getting errors in updating onlineMeetings (PATCH methods) even with this simple request:

PATCH https://graph.microsoft.com/v1.0/users/<owners_uid>/onlineMeetings/
{
"@odata.type": "#microsoft.graph.onlineMeeting",
"allowAttendeeToEnableCamera": true
}
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-11T09:52:54",
"request-id": "c33e69dd-de32-4030-a393-d6cd63a449ea",
"client-request-id": "c33e69dd-de32-4030-a393-d6cd63a449ea"
}
}
}

as a workaround I have used object.getBackingStore().clear(); just after its creation before passing it to the patch. This will delete the parameter "@odata.type": "#microsoft.graph.onlineMeeting" making it work again.

EDIT 2026-05-11 08:07:00: at the moment issue seems to have been fixed.
Expected behavior

PATCH https://graph.microsoft.com/v1.0/users/<owners_uid>/onlineMeetings/
{
"@odata.type": "#microsoft.graph.onlineMeeting",
"allowAttendeeToEnableCamera": true
}
returns 200 with updated onlineMeeting

How to reproduce

try to patch an existing meeting using the java sdk for example setting the parameter allowAttendeeToEnableCamera

sdk under the hood will automatically add
"@odata.type": "#microsoft.graph.onlineMeeting"
to the http patch

it used to work in the past, but since a couple of days it returns:
"error": {
"code": "InvalidArgument",
"message": "One or more properties do not support updating. Please refer to Microsoft Graph documentation for more information.",

SDK Version

6.64.0

Latest version known to work for scenario above?

No response

Known Workarounds

as a workaround I have used object.getBackingStore().clear(); just after its creation before passing it to the patch. This will delete the parameter "@odata.type": "#microsoft.graph.onlineMeeting" making it work again.

Debug output
Click to expand log ```
</details>


### Configuration

_No response_

### Other information

_No response_

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 PATCH request against the onlineMeetings endpoint with Java SDK 6.64.0, using allowAttendeeToEnableCamera and observing whether @odata.type is sent. Compare the request with the documented expected 200 response and the getBackingStore().clear() workaround; done means PATCH succeeds without manually clearing the backing store.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.