ACS retirement (2028-09-30): Is joining Teams meetings as a Teams user (getTokenForTeamsUser + TeamsCallAgent) on iOS/Android still supported?

チン・ドゥク タム 20 Reputation points
2026-10-14T04:43:25.4766667+00:00

We provide a mobile app (iOS/Android) that joins Microsoft Teams meetings from a meeting link using the ACS Calling SDK. After reading the Retirement and breaking changes guide, we would like Microsoft to confirm whether our implementation remains supported after September 30, 2028.

Our implementation

(A) Join as an ACS identity (guest)

  • Server: CommunicationIdentityClient creates an ACS user and issues a VOIP-scoped token
  • App: CallClient.createCallAgent → CallAgent.join(TeamsMeetingLinkLocator)

(B) Join as a Teams user (Microsoft 365 identity / Custom Teams Endpoint)

  • Server: exchanges the user's Entra ID token (delegated scopes https://auth.msft.communication.azure.com/Teams.ManageCalls and Teams.ManageChats) for an ACS token via CommunicationIdentityClient.getTokenForTeamsUser
  • App: CallClient.createTeamsCallAgent → TeamsCallAgent.join(TeamsMeetingLinkLocator)

SDKs: iOS AzureCommunicationCalling 2.12.1, Android azure-communication-calling 2.16.0, Java azure-communication-identity 1.5.3. We do not use ACS Chat, the UI Library, Rooms, or Call Automation.

Questions

  1. The guide's FAQ states that ACS identities continue to work with supported services such as Teams Meeting Interop, so we understand that (A) remains supported. Is (B), joining a Teams meeting as a Teams user via Custom Teams Endpoint, also covered by "Teams Meeting Interoperability" after September 30, 2028? The guide does not mention Teams user identities.
  2. Will getTokenForTeamsUser (Teams user token exchange) in the Communication Identity service remain available after September 30, 2028? Are any changes planned for the required Entra ID app permissions?
  3. Which Calling SDK version is required after September 30, 2028? Is iOS/Android 3.0.0 (released 2026-09-18) sufficient, or will a later major version be required? The guide's example mentions "4.x.x". Also, iOS 3.0.0 is not published on CocoaPods (latest stable there is 2.15.1). Is CocoaPods distribution discontinued in favor of Swift Package Manager?
  4. The migration table lists "applicable Teams license" as a requirement for the Calling SDK. Are any additional licenses or pricing changes expected for (A) guest participants or (B) Teams users?

Related question

The same question about Teams identities was asked here, and it currently has only an AI-generated answer: https://learn.microsoft.com/en-us/answers/questions/6022621/azure-communication-services-calling-sdk-post-2028

The AI-generated answers so far infer support from capability documentation written before the retirement announcement. We would appreciate an official confirmation from the ACS product team or Microsoft staff.

Note: The Teams Meeting Interop migration link in the guide (https://aka.ms/acs-calling-teamsinterop) currently redirects to a Bing search page. If there is an official migration document, a pointer would be helpful.

Thank you.

Azure Communication Services
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rukshan edirisinghe 2,205 Reputation points
    2026-10-19T03:15:47.02+00:00

    Hi @チン・ドゥク タム

    I went through the "Retirement and breaking changes guide" for this. Here's how your two paths line up against what it says, plus the gap you'll need Microsoft to fill.

    (A) Joining as an ACS identity (guest) via CallAgent.join(TeamsMeetingLinkLocator)

    This one is covered. The guide lists "Teams Interop, Teams Phone, and Teams Phone Extensibility" as continuing, and says "Teams interoperability scenarios will continue to be supported as a calling experience." Its FAQ also says ACS identities keep working with supported services such as Teams meeting interop. The Calling SDK is classed as a breaking change, not a retirement, so to stay supported after September 30, 2028 you'll need to move to the latest major SDK version when it ships.

    (B) Joining as a Teams user (getTokenForTeamsUser + TeamsCallAgent)

    The guide doesn't name Custom Teams Endpoint, getTokenForTeamsUser or TeamsCallAgent anywhere. It's clearly Teams-aligned in spirit, but I can't point you to a line that confirms it, so I wouldn't treat it as guaranteed.

    Things to check in your app regardless of A or B:

    1. If you use the ACS UI Library (mobile), that's in the retired list. Plan to move to the Calling SDK directly.
    2. If you show meeting chat through ACS Chat for Teams Meeting Interop, that's retired too.
    3. Between now and the retirement date, iOS/Android OS-update issues are treated only as break-fix. Keep that in mind for testing.

    For written confirmation on path B, the guide points to a dedicated retirement support channel: https://aka.ms/acs-retirement-support. I'd send both scenarios exactly as you described them here.

    Do you use the ACS UI Library in the mobile app, or the Calling SDK directly?

    If this answered your question, please consider accepting it as the answer. If Microsoft's reply changes the picture for path B, let me know and I'll be happy to keep helping.

    Reference:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.