Teams bot invite PSTN participant fails Intermittently when Compliant Recording Policy is enabled for user
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 4%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDD%3C/text%3E%3C/svg%3E)
Dr Dave H
160
Reputation points
We use the Graph Cloud Communications API for our Teams Calling Bot to answer an incoming call to the Bot from a Teams user, and then add a PSTN participant into the call (as per this example participant: invite - Microsoft Graph v1.0 | Microsoft Learn).
This works fine as expected if the Teams user making the initial call does not have a "Teams Compliance Recording Policy" set against them. However, if the Teams user has a recording policy set against them (and a recoding bot is brought into the call, even if it then drops out) the Invite Participant operation usually fails (It should be noted that it does work ok sometimes). When it fails we see the following error;
Steps to Reproduce;
1. Teams user (with Teams Compliance Recording Policy set against them) makes call to Teams Calling Bot (Call UPN or phone number of Resource Account/Application Instance)
2. Teams Bot answers call [call: answer - Microsoft Graph v1.0 | Microsoft Learn]
3. Teams Bot invites PSTN participant to the call [participant: invite - Microsoft Graph v1.0 | Microsoft Learn]
4. Intermittently, the invite fails with a 403 response
I can confirm that the Application Instance (Resource Account) has a phone number and Microsoft Teams Phone Resource Account license assigned, and also a suitable Voice Routing Policy has been applied to allow for calls over Teams Direct Routing. The Teams user also has a suitable Teams license for making PSTN calls.
Since this works ok for users without a recording policy, and we've tested with a number of different recording Bots, we believe that our Bot code must be correct and that the issue is within the Teams infrastructure.
Any help in this matter will be gratefully received. Cheers, Dave
Microsoft Teams | Development
{count} vote
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 85%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
Nivedipa-MSFT 3,846 Reputation points Microsoft External Staff Moderator2025-05-22T06:21:53.43+00:00 @Dr Dave H - Thanks for bringing this issue to our attention. The issue is intermittent, implement retry logic with exponential backoff for the
inviteoperation. -
Nivedipa-MSFT 3,846 Reputation points Microsoft External Staff Moderator
2025-05-29T06:16:41.08+00:00 @Dr Dave H - Could you please confirm if the above suggestion helped you or are you still facing this issue?
-
Dr Dave H 160 Reputation points
2025-05-29T08:43:14.64+00:00 Hi @Nivedipa-MSFT , thanks for your response. A retry doesn't help. It seems that if it's a VoIP call into the Bot in which the Invite-Participant API call fails, any subsequent retry also fails. I can retry a minute later and it will still fail. When I used the word "intermittent", I was meaning that some calls into the Bot are fine (and the Invite-Participant works ok), whereas some calls into the Bot are going to always going to fail the Invite-Participant operation (no matter if the API call is retried).
-
Dr Dave H 160 Reputation points
2025-05-29T08:52:24.77+00:00 For further information, here is the error message (I tried to include it in the original post but the AI Content verifier kept deleting my post);
"resultInfo": { "code": 403, "message": "addParticipants failed for participant 4:+<phoneNumber>. Underlying reason: Forbidden. DiagCode: 403#10151.@", "subcode": 10151, "@odata.type": "#microsoft.graph.resultInfo"},
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 94%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Babu Singh 0 Reputation points2025-10-30T11:26:09.3733333+00:00 Hi @Nivedipa-MSFT , Is there any solution for this issue. We are facing the exact same issue and its a big concern for us as we might loose customers due to this issue.
Calls start dropping once we assign Teams user to Call Compliance Policy.
Otherwise they work perfectly fine.
Exact same issue and scenario as mentioned in this issue.
@Dr Dave H Appreciate if you can share if you found any solution to this issue already.
Appreciate a quick response here.
-
Dr Dave H 160 Reputation points
2025-10-31T09:42:59.8766667+00:00 Hi @Babu Singh , we've been unable to find a solution. We've also tried accessing Microsoft support via other routes but to no avail.
-
Babu Singh 0 Reputation points
2025-10-31T10:02:29.7333333+00:00 @Dr Dave H Thanks for the update. Looks like a Teams graph product issue which they should really fix. This limitation is almost killing the implementation for graph PSTN calls for Call Compliance recording.
Sign in to comment
Sign in to answer