Remote Event Receivers retirement update in SharePoint Online

Hi BertJansen

Thank you for the information about the recent update on missing Webhooks features.

We, as a software vendor, are currently fully engaged in migrating from Remote Event Receivers to Webhooks, despite their limitations. Unfortunately, we have to manage this transition. Migrating all our customer tenants, upon which tens of thousands of users depend, is quite challenging.

Apologies for the complaints ;-) Now, to the main point: we would greatly appreciate it if the Microsoft team could implement two small changes to the Webhook functionality.

First, regarding Webhook validation: currently, only a validation token is sent when adding a Webhook subscription to a list. It would be very helpful if we could also receive the standard payload that is sent when an item is added or updated. With this information, we would be better equipped to decide whether to approve the Webhook registration. At present, we have no insight into the tenant, site, or list from which the Webhook registration originates.

Second, concerning the expiration date: currently, a Webhook expires after six months. We have developed a mechanism to register all Webhooks in our database, enabling us to refresh them before they expire. However, it would be excellent if the Webhook expiration could be removed, allowing us to eliminate this burden from our provisioning engine.

I hope these small adjustments can be incorporated into the Webhooks, preferably in the near future, as our deadline is rapidly approaching.

Kind regards, and enjoy the Christmas holidays!