OData property changes to callRecords change notifications in Microsoft Graph

Microsoft Graph API will introduce OData property changes to webhook change notifications for the callRecords endpoint. From April 20, 2023, the resourceData field will contain renamed entries of oDataId and oDataType, which will be replaced with @odata.id and @odata.type, respectively. Developers can continue using the old naming conventions while updating their applications with the new ones. After October 2023, the old naming conventions will be fully deprecated and removed from the notification.

About the breaking change

A breaking change will occur in the callRecords endpoint of Microsoft Graph API, which will introduce OData property changes to webhook change notifications. Starting April 20, 2023, the resourceData field will contain two renamed entries of oDataId and oDataType, which will be replaced with @odata.id and @odata.type, respectively. Both the old and new naming conventions will be provided in the payload during a six-month transition period, giving developers time to update their applications with the new naming conventions. After October 2023, the old naming convention will be fully deprecated and removed from the notification.

What you need to do to prepare

Developers can continue using the old naming conventions while updating their applications with the new naming conventions. However, developers should note that the content of the new @odata.type field will be #Microsoft.Graph.callrecord, while the old oDataType field will remain #microsoft.graph.callrecord. After the transition period, only @odata.id and @odata.type will remain in the notification.

Resources

• Visit the Microsoft Graph Dev Center
• Read our documentation
• Follow us on (@Microsoft365Dev) / Twitter
• Join our community