Graph API for call records unable to establish new subscriptions

Question

Graph API for call records unable to establish new subscriptions

Sonal R 0

Hi,

I'm using Graph API for subscribing to call records. This was working till recently. However, when I try to request a new subscription, I'm getting a 400 Bad Request with "Subscription validation request timed out". However, it doesn't look like Graph API even tries to reach the validation endpoint. The validation endpoint is reachable (I verified this), so what could be the reason for this?

In other cases, I also see the validation endpoint being reached with this message being print "Testing client application reachability for subscription Request-Id: d6ab33f7-8678-488b-8f51-36bab68284e9" (this is the validation token from Graph API) - e.g. for error cases like "Forbidden; Reason: The request is not authorized for this user or application." But, if there are no errors for authorization, the validation request is never to sent to the validation endpoint of my service.

Was there any change in this area?

Suchitra Suregaunkar 340 Reputation points Microsoft External Staff Moderator

2025-08-25T08:44:04.58+00:00

Hello Sonal R,

Thank you for posting your query on Microsoft Q&A portal.

Validation Endpoint Viability: While your endpoint may be accessible through a browser or other tools, Microsoft Graph also needs to connect to it directly from its own network. Check firewalls and IP restrictions: Make sure your endpoint allows inbound traffic from Microsoft Graph IP ranges. Response requirements: The validation request must return an HTTP 200 OK status within 10 seconds, include Content-Type: text/plain, and the body must contain the exact validation token provided by Graph.

Reference: https://learn.microsoft.com/en-us/graph/change-notifications-delivery-webhooks?

Subscription Limits: Make sure you are not hitting any subscription limits which might block new subscription requests. While you're focusing on call records, other subscriptions in your tenant could potentially be affecting your ability to create new ones.

Reference: https://learn.microsoft.com/en-us/graph/api/resources/subscription?view=graph-rest-1.0

Permissions and Authorization: If the app you are using does not have the right application or delegated permissions for the resource, subscriptions might fail, and you might not even see any error messages. If some subscriptions hit your endpoint but show errors like "Forbidden; Reason: The request is not authorized," while others never reach your endpoint, it could be a sign of issues with permissions, user context, or how the app registration is set up.

Reference: https://learn.microsoft.com/en-us/graph/api/resources/callrecords-api-overview?view=graph-rest-1.0

Use Graph Explorer to test subscription creation, which can help isolate whether the issue is client-side or Graph-side

Reference: https://developer.microsoft.com/en-us/graph/graph-explorer

Thanks,

Suchitra.

Your answer

Suchitra Suregaunkar 340 Reputation points Microsoft External Staff Moderator

2025-08-25T08:44:04.58+00:00

Hello Sonal R,

Thank you for posting your query on Microsoft Q&A portal.

Validation Endpoint Viability: While your endpoint may be accessible through a browser or other tools, Microsoft Graph also needs to connect to it directly from its own network. Check firewalls and IP restrictions: Make sure your endpoint allows inbound traffic from Microsoft Graph IP ranges. Response requirements: The validation request must return an HTTP 200 OK status within 10 seconds, include Content-Type: text/plain, and the body must contain the exact validation token provided by Graph.

Reference: https://learn.microsoft.com/en-us/graph/change-notifications-delivery-webhooks?

Subscription Limits: Make sure you are not hitting any subscription limits which might block new subscription requests. While you're focusing on call records, other subscriptions in your tenant could potentially be affecting your ability to create new ones.

Reference: https://learn.microsoft.com/en-us/graph/api/resources/subscription?view=graph-rest-1.0

Permissions and Authorization: If the app you are using does not have the right application or delegated permissions for the resource, subscriptions might fail, and you might not even see any error messages. If some subscriptions hit your endpoint but show errors like "Forbidden; Reason: The request is not authorized," while others never reach your endpoint, it could be a sign of issues with permissions, user context, or how the app registration is set up.

Reference: https://learn.microsoft.com/en-us/graph/api/resources/callrecords-api-overview?view=graph-rest-1.0

Use Graph Explorer to test subscription creation, which can help isolate whether the issue is client-side or Graph-side

Reference: https://developer.microsoft.com/en-us/graph/graph-explorer

Thanks,

Suchitra.

Share via

Graph API for call records unable to establish new subscriptions

Your answer