Microsoft Graph Call Records API Returning 404 for Recent Call IDs

Question

When querying recent call records using the Microsoft Graph Communications API, the endpoint consistently returns a 404 Not Found response with the message:

“Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available.”

However, the call IDs we are retrieving are well within the 30‑day retention window, and therefore should be available.

Answer 1

Hi Kudos,

Thank you for your response.

We are using the ID obtained from the Call Records API to query the child endpoints. For the specific call_id, the startDateTime is 2026-02-06T10:08:50Z, which is not older than 30 days. However, we are still receiving a 404 error with the message:

"Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available."

We have two child endpoints for the call endpoint: sessions and participants. The issue is occurring only with the sessions endpoint for this particular call_id.

When we use the same call_id with the participants endpoint, we are able to retrieve data successfully.

Since the same ID works for one child endpoint but fails for the other, it does not appear to be related to record age or incorrect ID usage.

Could you please help us understand why the sessions endpoint is returning a 404 error in this scenario?

Answer 2

Hi Louis Desmet,

Thank you for posting your question in the Microsoft Q&A forum.

I have researched the error message you provided and found that there have been multiple reports in the past regarding similar issues where valid calls within the 30-day window still return a 404 error. While some cases were temporary service-side glitches that resolved themselves, the error message stating that the "call record is older than 30 days" can often be a generic "Not Found" response rather than an accurate reflection of the call's age.

Based on my findings, I have summarized some suggestions that you can try to troubleshoot this issue:

• Wait for Record Availability: Call records require some time to become available after a call ends. This process can take up to 150 minutes (2.5 hours). If you query the API too quickly after the call concludes, you may receive a 404 error because the record is not yet ready to be read.
• Verify the correct ID Usage: Ensure you are using the correct id to retrieve the call record. A common mistake is using the CallId from Client SDKs, Call Quality Dashboard (CQD), or PSTN logs (pstnCallLogRow). These IDs cannot be used to query the Call Records API directly. Reference: Call records API overview
  • To obtain the correct ID, you can use the callChainId property of a call or set up a Webhook subscription to receive notifications when a call record becomes available.

Additionally, I have seen cases where call records were successfully retrieved but then returned a 404 error when queried again with the same id a few days later. In such persistent cases, I recommend logging the request-id and timestamp of the failed request and submitting a support ticket via the Azure Portal. This will allow Microsoft support agents to use their internal tools to troubleshoot the issue further with your specific call details.

I hope this helps.

---

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.