![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 66%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYL%3C/text%3E%3C/svg%3E)
Microsoft 365 and Office | SharePoint | Development
The process of building custom applications and tools that interact with Microsoft SharePoint, including SharePoint Online in Microsoft 365.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 69%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHV%3C/text%3E%3C/svg%3E)
Thank you for the detailed information and logs.
Based on your description, this issue does not appear to be related to your client endpoint or application. From the timestamps, the list changes occurred as expected, but the webhook notifications were not delivered in real time. Instead, they were delayed and then received in a batch across multiple lists at the same time. This pattern typically suggests that the events were queued within the SharePoint Online webhook delivery pipeline and released later, rather than indicating a service issue.
Regarding your question about whether this behavior is expected, as far as I know, SharePoint Online webhooks operate asynchronously and do not guarantee real-time delivery. In certain situations, such as transient service conditions or internal retry/backoff handling, notifications may be delayed before being sent. When this happens, it can result in notifications being grouped and delivered together after a period of time. Since your endpoint is consistently responding within the expected timeframe and returning a 200 status, and the same behavior is not observed in other environments, this points more toward a service-side delay within SharePoint Online or tenant-specific conditions, rather than an issue with your client implementation.
Regarding documentation, you are correct that the current official guidance mainly focuses on initial retry logic and error handling. At this time, there is no detailed official documentation describing extended delay scenarios or longer retry/backoff intervals.
As the delay appears to originate from the service-side notification pipeline, further investigation will require involvement from Microsoft’s support team. A technical support engineer can perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis.
Reference: Get support - Microsoft 365 admin | Microsoft Learn
Note: Creating a support ticket requires Microsoft 365 admin privileges. Please ask your client to contact their administrator to submit a new ticket.
Apologies for redirecting you to the related development team support. As moderators in this community, we do not have access to your specific tenant configuration, and my testing environment is limited. Therefore, my guidance is based on available Microsoft documentation and resources. That said, I’ll do my best to provide additional insight where possible.
If you have any additional concerns, feel free to comment below. I would be more than happy to assist.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.