BertJansen As an ISV building standard solution on SharePoint Online, we are worried about the retirement of RER. We understand the need for retiring the synchronous event receivers as they probably causes performance issues in your end, as the the infrastructure becomes dependent on external services. However, there is a huge gap between the synchronous remote event receivers and web hooks which we need to address.
- They expire after 6 months - running solutions with +100.000 sites it's really a pain to keep all web hook registrations active. Using the graph it's only 1 month as I understand this.
- We don't get any information about the actual item being changed. This causes extra calls to SharePoint Online. A typical scenario would be that we need to check the change log for the site, get the item from the SharePoint list, get the previous version of the item to determine what was changed. These days we are really focused on resource units and reducing our call to SharePoint to avoid throttling - this will have a great impact on this.
- Timeline: Giving 1 year of notice before retiring on new tenants is not very respectful to all ISV building solution based on SharePoint. We need more time
Please reach out if you want to discuss further.
Microsoft