Forum Widgets
Latest Discussions
ACS Teams interop meeting chat suddenly returns 403 Forbidden on all sends since late Aug 2026
Since approximately Aug 24, 2026, every Azure Communication Services (anonymous interop) user joining Microsoft Teams meetings in our tenant gets 403 Forbidden on ALL meeting chat operations, while calling, roster, and screen-share work normally. This broke suddenly with no changes on our side. The error on both ChatThreadClient.sendMessage and sendTypingNotification is "CommunicationError" Code "Forbidden", Message "The initiator doesn't have the permission to perform the requested operation." ACS users also receive no thread messages (Teams-native participants chat with each other fine in the same meeting), and the communication-react composite shows "You are no longer in this chat thread" immediately on join - so the ACS user appears to never be attached to the meeting chat thread, even though the call roster add works. What we have verified and ruled out - Reproduces with the minimal azure/communication-react (1.32.0) CallWithChatComposite quickstart and a freshly minted ACS identity (voip+chat scopes) - not our application. - Reproduces on BOTH Graph-app-created online meetings AND a meeting created by a human organizer in the Teams desktop app with default options. - Fails on chat api-versions 2024-06-05-preview and 2025-03-15. - All CsTeamsMeetingPolicy instances have MeetingChatEnabledType = Enabled (verified via Teams PowerShell as Global Admin). - ACS federation is configured. EnableAcsUsers = True and our ACS resource's immutable ID is in AllowedAcsResources. External access policies have EnableAcsFederationAccess = True. EnableExternalAccessRestrictionsForChatParticipants and EnableMutualFederationForChatParticipants are both False. - Per-meeting allowMeetingChat = enabled. Anonymous join allowed. BlockedAnonymousJoinClientTypes empty. - User is fully admitted and call state is Connected when sends fail (not the known join-timing issue), and the failure persists for the entire meeting. Sample failing request - POST to (resource).canada.communication.azure.com /chat/threads/19%3Ameeting_...%40thread.v2/messages?api-version=2025-03-15 returns 403, Ms-Cv IGMF4wkAI0+MIaxuFQ0kJw.0, 2026-08-31 16:04:38 UTC (Canada region resource). Was there a recent service-side change or rollout to how ACS interop users are added to Teams meeting chat threads, or a new tenant/meeting setting that now gates this? Is anyone else seeing this since late August 2026? We can share tenant ID, resource ID, and additional Ms-Cv values privately with Microsoft engineers. An Azure support case is also being opened in parallel. Also posted on Microsoft Q&A - https://learn.microsoft.com/en-us/answers/questions/5990218/acs-teams-interop-meeting-chat-suddenly-returns-40
Events for an agent not picking up the call
Hi, We have a requirement where the caller should be transferred to voicemail recording when the agent does not pick up the call. Currently, if the agent does not pick up the call, the caller reaches the agent's personal voicemail. Is it possible to interrupt that and redirect the call to ACS voicemail recording mechanism? The ACS framework send a "CallTransferAccepted" if the personal voicemail is reached. Are there any events which can be used to detect that agent did not pick the call. We tried the Job router, but it does not seem to detect that agent is not picking the call. Any suggestions? Thanks
Issue with Joining Microsoft Teams Meeting Directly from React Native App Using Azure Communication
I am currently working on integrating Azure Communication Services into a React Native app to enable direct joining of Microsoft Teams meetings. I have followed the official Azure repository for React Native: https://github.com/Azure-Samples/communication-services-ui-library-react-native Problem Description The issue I am encountering is that, after providing the access token and Microsoft Teams meeting link, the app does not behave as expected. Instead of directly joining the meeting, the user is redirected to an input fields screen, requiring additional interaction. My goal is for the app to join the Microsoft Teams meeting immediately after entering the access token and meeting link, without any intermediate screens. Issue When clicking "Join Call," instead of seamlessly joining the Microsoft Teams meeting, the app redirects to an input fields page. This step is unnecessary in my use case, as I want the app to join the Teams meeting directly. I am unsure whether this issue is due to an incorrect setup in the Azure Communication Services configuration or something related to the code implementation. Could someone please assist me in resolving an issue where my app redirects to an input fields page instead of joining a Microsoft Teams meeting directly? Thank you!
Speech Recognition for Alphanumeric
Hi, I am using Azure Communication Service with Cognitive Service for handling voice call scenarios (STT and TTS). One of our customer use cases requires alpha-numeric input in a workflow. The Azure Speech recognizer performs well for numbers and other patterns. However, when the user spells out alphabets for alphanumeric values, the recognition success rate is very low. For example, the product ID pattern is like "P-43246". In most cases, "P" is recognized as "D", "B", or "3". I have tested this on both mobile phone networks and VoIP. The success rate is significantly lower on mobile networks. Is there any settings available to improve the recognition success rate? Azure Services used: ACS Phone Number Azure Cognitive Service Event Grid Subscriptions Thanks, Aravind
how to record both video and unmixed audio of a group call
Hi, I need to record a meeting's video as well as unmixed audio stream of the call, but it seems from the documentation, we can only either record a mixed audioVideo format, or an unmixed multi channel audio format, we can not do both at the same time, I tried to start recording on the same serverCallId 2 times with different format mentioned, that did not work, is there any way to achieve what I want?Failed to create remote connection for private endpoint
Hi Team, We have set up an application gateway in Azure and enabled the private link service within the Azure application gateway. However, after configuring the above setup, we have encountered an issue while trying to create a private endpoint from either another tenant or the same tenant. We consistently receive the following error: An error occurred. Failed to create remote connection for private endpoint /subscriptions/175b2/resourceGroups/test/providers/Microsoft.Network/privateEndpoints/tstt (Code: InternalServerError) This configuration was working correctly until about 20 days ago, but since then, we have been facing this error continuously. We have strictly followed the Azure documentation to create the application gateway and configure the private link within it: https://learn.microsoft.com/en-gb/azure/application-gateway/private-link-configure?tabs=portal Any assistance or insights on resolving this issue would be greatly appreciated.
Azure Communication Service / Call a Call Queue
Hello When I try to call a call queue in the same tenant from Azure Communication Services, a connection is established and then terminated shortly afterwards with this error code: {message: 'CallSetupError', code: 403, subCode: 10391, resultCategories: Array(1)} I could not find anything about this error code in the documentation. Can anyone help me here? I have also adjusted the tenant policy as described here: https://learn.microsoft.com/en-us/answers/questions/1695333/azure-communication-service-call-queue?comment=question Best regards
