Skip to content

Error in PATCH onlineMeeting #2589

@giancanuz

Description

@giancanuz

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.

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_

Metadata

Metadata

Assignees

No one assigned

    Labels

    status:waiting-for-triageAn issue that is yet to be reviewed or assignedtype:bugA broken experience

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions