0

I am trying to receive change notifications from Microsoft Graph whenever an event is updated (created, deleted, or updated).

I have successfully managed to create subscriptions. The URL that receives the notifications is of an Azure Function. However, whenever I create or delete an event, the Graph sends multiple notifications for one specific change.

As mentioned in the documentation https://learn.microsoft.com/en-us/graph/webhooks, I am sending back 202-Accepted status code to the Graph as soon as I receive the change notification.

return new StatusCodeResult(202);

This is supposed to stop any further notifications from Graph. However, I still receive 2 to 4 notifications for a specific change.

I couldn't figure out what else I can do to limit the number of notifications to just one per change. Any help/suggestion would be highly appreciated.

2
  • This sounds uncommon to me. I have hooks on users and groups and it normally takes up to a minute to get called, leading to an aggregated call if multiple changes are made to a single object. But the concrete behavior is on Microsoft site and you can't influence it. So you have to implement some debounce mechanism on your site. Commented Oct 23 at 7:52
  • Some scenarios will lead to this experience. Internal retries or backend replication can cause duplicates. I believe if you have more than one subscription for the same resource and changeType, each subscription will receive its own notification. The first paragraph on HTTP codes and retry logic here also explains a scenario where Microsoft Graph will continue to send notifications- learn.microsoft.com/en-us/graph/… Commented Nov 11 at 8:22

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.