Azure Communication Services: Cannot join Teams meeting

Question

Hi,

we're developing a web app based on ACS with Teams interoperability enabled. Based on this guide https://learn.microsoft.com/en-us/azure/communication-services/concepts/teams-interop, we submitted the form to enable the interop functionality between ACS and Teams for our tenant more than a week ago.

Unfortunately, we are still not able to join a Teams meeting with our client. We are using the latest communication-calling SDK 1.0.1-beta (https://www.npmjs.com/package/@azure/communication-calling).

When trying to join the meeting, the request POST https://api3.cc.skype.com/conv/ fails with a 403 Forbidden message. The response body shows:

{  
  "operationFailure": {  
    "sender": null,  
    "reason": "unknown",  
    "code": 403,  
    "subCode": 5222,  
    "phrase": "Acs user is not allowed to create conversation.",  
    "resultCategories": [  
      "ExpectedError"  
    ],  
    "acceptedElsewhereBy": null  
  },  
  "CorrelationId": "<UUID>"  
}  

Our ACS user has an access token with the scopes "voip" and "chat".

Does this error indicate that the interop functionality between ACS and Teams might not have been enabled yet? How can we check whether or not the interop functionality has been enabled for our tenant successfully?

Thanks in advance

Jan

Answer 1

Thanks for asking question! Just to confirm when requesting to enable the federation between ACS resources and your Teams tenant while filling the form where providing the Email address please Note your email address must be one of the email addresses, registered as "Global Administrator" or "Teams Service Administrator" in Office 365.

Please read more on roles here https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/about-admin-roles?view=o365-worldwide

For enabling Teams interoperability you must be a member of the owning organization of both entities to use this feature.

Further Communication Services users can join scheduled Teams meetings as long as anonymous joins are enabled in the meeting settings. If the meeting is scheduled for a channel, Communication Services users will not be able to join the chat or send and receive messages.

Also you want to know that Azure Communication Services interoperability isn't compatible with Teams deployments using Microsoft 365 government clouds (GCC) at this time.

You may want to refer this document link might be helpful: https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/chat/meeting-interop

Hope this helps. Please let us know if issue remains.

Answer 2

Hi @SnehaAgrawal-MSFT ,

I've got exactly the same problem as @Jan Bender . I didn't get a reply after filling in the form, but I made an enquiry and had it confirmed that the interop had been activated. The only difference is that I'm using the latest azure/communication-calling 1.0.1-beta.2 package, but I had the same error on version 1.0.0.

Regards,
Ian.

Answer 3

I am getting the same problem. Please let me know how to fix these issues.

Answer 4

Hi @SnehaAgrawal-MSFT , could you please help me on this :
I have the same problem. And I've submitted the form to enable Teams interoperability twice (1 and 5 days ago)
I don't use Microsoft 365 government clouds (GCC). My app regions are Netherlands and South East Asia.
How can I find out if the federation between ACS and Teams has actually been enabled ?
Thank in advance