MicrosoftHi BertJansen ,
Following up on the requests made on December 19, 2024, regarding Webhook validation and expiration, we would like to propose a third enhancement to the Webhook functionality.
Currently, when assigning a Remote Event Receiver (RER), it is possible to scope it to a specific action, such as Add, Update, or Delete. This allows us to reduce the number of messages we need to process, focusing only on the events we are interested in, such as Added events. However, with Webhooks, it is not possible to set such a scope. As a result, we receive all events and must handle them, even when we are only interested in Add events.
It would be extremely beneficial if we could set a similar scope when registering a Webhook. This change would likely have minimal impact on the SharePoint side but could significantly enhance processing efficiency on our end.
As ikarstein also mentioned, it would be great if the community could receive updates on this topic. Many of us have invested considerable effort into adapting to these changes without knowing the current status or the new features that might be implemented to assist us.
Thank you in advance for considering this request, and we look forward to any updates you can provide.
MicrosoftSander Simons : having web hook registration for only certain types of events can indeed lead to less calls to your service. To be transparent, I don't see us build that anytime soon, so I would not count on that for your immediate needs. I would strongly advise to ensure your solutions can work using the current web hook features, maybe in a less ideal manner, without a dependency on RER's registered with Azure ACS.
