I am able to replicate the same when I am using Customer-Id in body while creating appointment.
So as a workaround, I will suggest you to use Body without Customer-id.
Please refer to the below sample screenshot:
Sample Body:
{
"@odata.type": "#microsoft.graph.bookingAppointment",
"endDateTime": {
"@odata.type": "#microsoft.graph.dateTimeTimeZone",
"dateTime": "2023-04-04T16:30:00.0000000",
"timeZone": "UTC"
},
"serviceId": "service-id",
"staffMemberIds": [
"Staff-member-id"
],
"startDateTime": {
"@odata.type": "#microsoft.graph.dateTimeTimeZone",
"dateTime": "2023-04-04T16:00:00.0000000",
"timeZone": "UTC"
},
customers@odata.type: "#Collection(microsoft.graph.bookingCustomerInformation)",
"customers": [
{
"@odata.type": "#microsoft.graph.bookingCustomerInformation",
"name": "Jordan Miller",
"emailAddress": jordanm@****.com
}
]
}
Also, I would recommend you to raise a support case with Microsoft Graph, a Support Engineer will be able to assist you better. You can raise support ticket from
http://aad.portal.azure.com/ or https://admin.microsoft.com/#/support/requests.
Hope this helps.
If the answer is helpful, please click Accept Answer and kindly upvote. If you have any further questions about this answer, please click Comment.