Graph API returns an empty array when listing transcripts

Thanks @saleha mubeen

I verified that the transcript is available for the user in the Teams channel (via the Shared tab) as well as in the meeting itself (via the Recap tab)

• The delegated token contains OnlineMeetingTranscript.Read.All

The API response for the regular Teams meeting returns a list of objects, when the response for a meeting scheduled from a channel returns an empty array

In the graph explorer I observe the same behavior: list of objects for a regular meeting, and an empty array for a meeting scheduled from a channel

• Below is are the response headers

{
    "client-request-id": "68f51cec-c040-5911-dd1f-35b6b80e68b5",
    "content-type": "application/json;odata.metadata=minimal;odata.streaming=true;IEEE754Compatible=false;charset=utf-8",
    "request-id": "37cb67de-f053-4f2b-afbc-c9b9d46bd9e8"
}

Thank you for the suggestions both. If you a not able to assist further, I will raise a ticket with the Microsoft support.

Dear @Yuri Kunash

I understand your concern. However, I do not have access to a suitable test environment to reproduce and validate the behavior in Teams channel meetings.

Based on your description, the issue started around August 18-19, 2026, and appears to affect only channel meetings. Since this appears to be a recent service-side change or regression and requires access to Microsoft backend telemetry for further investigation, I recommend opening a case with Microsoft Unified Support. The support team can review the affected tenant, analyze backend logs, and determine whether there is a known issue impacting channel meeting transcripts.

For reference: Microsoft Unified Support

Please note that this is a paid support ticket, which means it requires an active support plan or a one-time support purchase. However, the benefit of using this channel is that your inquiry will be routed directly to the Microsoft Product Group responsible for the specific service or feature in question. This team includes engineers and developers who work on the product itself, so they are best positioned to provide accurate, in-depth, and authoritative answers, especially for complex or edge-case scenarios that go beyond publicly available documentation or community knowledge. 

I apologize that I cannot reproduce the issue directly, but Unified Support would be the best path to obtain a definitive root cause and service-side investigation.

I hope the information shared is helpful. If you have any questions, please feel free to reach out. I'm looking forward to your update.

Note: Please follow the steps in the documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

This sounds like a regression or a Teams-channel-meeting-specific behavior rather than an authentication issue, especially since the same endpoint was working previously and the problem started around Aug 18–19.

A couple of things I’d check:

Confirm whether the transcript is actually available in the Teams channel meeting and not just generated for the meeting recording.

Verify the delegated token contains OnlineMeetingTranscript.Read.All and that admin consent is still valid.

Compare the response for a regular Teams meeting vs. a meeting scheduled from a channel using the same user/token.

Check whether calling the transcript endpoint with the same onlineMeetingId through Graph Explorer produces the same empty value array.

If only channel meetings are affected, it would be useful to capture the request/response headers, request-id, and Date/client-request-id and raise it with Microsoft support.

Given that this started suddenly around Aug 18–19 and appears limited to channel-scheduled meetings, I’d lean toward a service-side change/regression rather than the delegated permission itself.