When subscribing to presence updates via the Microsoft Graph SDK, the expected activity and availability fields in the resourceData object have gone missing in recent webhook payloads.
This issue has been affecting the functionality of our application as these fields are critical for monitoring user status.
Observe that the activity and availability fields are missing from resourceData.
Expected behavior: [What you expected to happen]
The resourceData object should include activity and availability fields to provide full presence information.
Actual behavior: [What actually happened]
The resourceData object does not include activity and availability fields, affecting our application's functionality.
Additional Context
The absence of these fields began around 10:00 PM UTC on April 16, 2024, without any changes to our subscription setup or handling code. This issue appears to be systemic as it is consistently observed across multiple environments.
Bug Report
Prerequisites
Description
When subscribing to presence updates via the Microsoft Graph SDK, the expected
activity
andavailability
fields in theresourceData
object have gone missing in recent webhook payloads.This issue has been affecting the functionality of our application as these fields are critical for monitoring user status.
https://learn.microsoft.com/en-us/graph/api/resources/presence?view=graph-rest-1.0#properties
Console Errors: [Is there any console error]
None
Screenshots: [If applicable, add screenshots to help explain your problem]
N/A
Steps to Reproduce
Receive a webhook notification payload.
Observe that the
activity
andavailability
fields are missing fromresourceData
.Expected behavior: [What you expected to happen]
The resourceData object should include activity and availability fields to provide full presence information.
Actual behavior: [What actually happened]
The resourceData object does not include activity and availability fields, affecting our application's functionality.
Additional Context
The absence of these fields began around 10:00 PM UTC on April 16, 2024, without any changes to our subscription setup or handling code. This issue appears to be systemic as it is consistently observed across multiple environments.
Usage Information
SDK Version - 3.0.7