Graph Presence.Read.All Subscription with webhook works only for about 100 users

Please note that this is the German (de-de) forum. I kindly recommend posting your question in German so that more community members can assist you effectively. If you prefer using English, you are welcome to post in the English forum instead. I sincerely appreciate your understanding and cooperation.

Hi @Ruhrig, Manfred

Based on your description, I understand that you have a Teams connector product that subscribes to the presence of Teams users over a webhook. While this works perfectly when the count of subscribed users is under 100, subscribing to 225 users receives a successful response but then completely stops delivering any presence notification messages over the webhook.

According to Microsoft documentation, a bulk Microsoft Graph Presence subscription can support a maximum of 650 different User IDs in a single subscription request when using the delegated permission Presence.Read.All. Currently, Application Permissions are still not supported for Teams Presence Change Notifications.

The officially documented resource format for this operation is:

/communications/presences?$filter=id in ('{id}', '{id}', ...)

Microsoft also documents that Presence Subscriptions support webhooks and will dispatch a notification whenever the presence status of any registered user changes. Therefore, if a subscription for 225 users is created successfully but you subsequently receive zero presence notifications, this behavior does not align with an explicit product limit of 100 users.

While I conduct further research on this behavior, I recommend testing the configuration using sequential batch increments to isolate the issue. For example, please try:

• Batch 1: 50 users
• Batch 2: 100 users
• Batch 3: 150 users
• Batch 4: 225 users

If 50 or 100 users operate normally but 150 or 225 users fail, you can split your tracking into multiple smaller subscription batches as a temporary workaround while we continue gathering diagnostic data. Although the official published limit is 650 users, this batch-testing method will help us identify whether a specific User ID is causing the breakdown or if the overall payload size is triggering a silent rejection.

Simultaneously, please confirm the following essential factors:

• All IDs supplied within the filter string are valid Microsoft Entra ID Object IDs, not UPNs.
• The target users are active, possess valid Teams licenses, and are not disabled.
• The subscription is explicitly created using a delegated token from a Work/School account.
• The delegated token has been granted proper admin consent for the Presence.Read.All permission.
• Your webhook endpoint responds quickly and consistently returns a successful status code.
• The subscription is actively renewed before its expiration interval.
• Actual, live presence state changes (e.g., changing status from Available to Busy) are occurring after the subscription is successfully registered.

Please let me know the details and behaviors you observe after trying these tests so we can investigate further.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click ""Comment"".

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.