‎Call Compliance Recording Issue for Calls via Graph API‎

Question

‎Call Compliance Recording Issue for Calls via Graph API‎

Babu Singh 5

Scenario:

We have call compliance recording partner and when we add Teams user to Call Compliance Policy Group the calls stops working.

The calls are working fine when Teams user is not assigned to Call Compliance policy group.

Technical Details:

We use the Graph API to create a call between a bot and a Teams user, then invite an external (PSTN) participant.

Without any recording policy, all calls (including PSTN participants) work as expected.

When we assign the Teams user to a Call Recording Compliance Policy group, the call between bot and Teams user still succeeds, but inviting the phone participant fails.

In failed calls (with compliance policy), the “phone” participant information is missing in the response.

Summary:

The PSTN participant invite fails only when the Teams user is under a call recording compliance policy.

The error 403#10151 appears consistently.

Request:

Please help investigate why inviting external (PSTN) participants via Graph API fails when call recording compliance is active.

1 answer

Your answer

Answer 1

Kudos-Ng 8,255 Microsoft External Staff Moderator

Hi Babu Singh,

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

From what you described, it seems you are experiencing an issue with a peer-to-peer call where compliance recording policy is enabled, and you are trying to invite an external PSTN participant using the Graph API addParticipant method. Please confirm if my understanding is correct.

Based on this behavior, I conducted some research and found that multiple users have reported similar issues in the past. From what I know, resolving this scenario typically requires engagement with the engineering team. To proceed, you will need to create a support ticket via the Microsoft 365 Admin Center so that a support agent can investigate further.

However, while waiting for the support team to reach out, you might consider testing the following workaround:

Try the same scenario using a scheduled Teams meeting instead of a peer-to-peer call.
This step can help narrow down whether the unexpected behavior is specific to the call type or applies to meetings as well.

I hope the information above is helpful. If you have any further questions, please feel free to share.

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.

Sayali-MSFT 4,146 Reputation points Microsoft External Staff Moderator

2025-10-31T04:31:43.7433333+00:00

Hi Babu Singh,Could you please confirm if your issue has resolved with provided suggestions or still looking for any help?
Babu Singh 5 Reputation points

2025-10-31T05:51:13.5333333+00:00
This is no where near to what I am looking for. Also I have already created ticket via Admin Center and they said its not their cup of tea do via azure portal.
I bought the developer plan especially for the resolution and then created this ticket here.

And its not peer to peer call. Its a PSTN call using graph API.

Graph -

Create Call - Bot and teams user

Invite Participant - PSTN (phone) participant.

It works perfectly fine when Call Compliance recording is not involved.

As soon as we add Teams user to Call Compliance Recording group, calls start failing and the invite participant is failing.

Appreciate if you can reproduce it and provide a fix.
I know people have reported it here but there is not a single answer providing the fix.

Appreciate if Developer Support plan can help us reach developer team also who can help here.

here is the Microsoft support ticket via Admin Center - __
__TrackingID#<PII removed>

here was the reply -
Upon discussing with <PII removed> on the call, I explained my constraints in providing further assistance on the scope matter as Graph API falls outside my support scope.

However, for further kindly contact the Graph team through the Azure portal
Kudos-Ng 8,255 Reputation points Microsoft External Staff Moderator

2025-10-31T09:50:42.6933333+00:00

Hi Babu Singh,

Thank you for your detailed response and for sharing the additional context about your situation.

Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

I’m truly sorry to hear that the information I provided earlier wasn’t what you were looking for, and that despite creating a support ticket via the Admin Center, you were unable to get assistance because the issue falls outside their scope.

From what I understand, problems related to PSTN calls—especially scenarios involving compliance recording—can be quite complex and often require coordination across multiple engineering teams. This is why it’s rare for public forum users to provide a complete resolution, and unfortunately, I couldn’t find any confirmed fixes in public discussions or documentation.

As a forum moderator, I don’t have the environment or resources needed to reproduce PSTN-related issues, nor do I have access to Microsoft internal systems to verify logs or apply fixes. My role here is limited to sharing information available through public articles or community discussions.

Given these constraints, the most viable next step would be to create a support ticket through the Azure portal, as suggested by the Admin Center support agent. This route connects you directly with the Graph engineering team who can investigate and provide a definitive solution. If you do receive a resolution, it would be incredibly helpful if you could share it here in this thread—this would benefit other users facing the same challenge and help them find answers more quickly.

Once again, I sincerely apologize for not being able to provide further assistance or a direct fix at this time.

Thank you for your understanding, and I appreciate your efforts in escalating this issue.

Share via

‎Call Compliance Recording Issue for Calls via Graph API‎

1 answer

Your answer