Azure Communication Services Calling SDK: post-2028 support for custom clients using Teams identities

Andrea Vincentini 0 Reputation points
2026-10-01T14:50:32.1466667+00:00

We are using Azure Communication Services Calling SDK in a custom web application with Microsoft Teams identities.

Our flow is:

  • User signs in with MSAL / Microsoft Entra ID using their Teams account.
  • We exchange the Entra ID token for an ACS token for the Teams user.
  • In the web client, we use createTeamsCallAgent(...).

The remote endpoint can be either:

  • a standard Microsoft Teams client, or
  • another custom web client using the same Teams identity flow.

We are currently using @azure/communication-calling@1.37.1, and we noticed that 2.0.0 is now the latest stable version on npm.

After reading the ACS retirement and breaking changes documentation for September 30, 2028, we would like to confirm whether our current architecture will still be supported.

Specifically:

Does a custom web client using createTeamsCallAgent(...) with a real Teams identity qualify as a supported Teams-aligned scenario after September 30, 2028?

Does this also apply when both endpoints are custom web clients using Teams identities?

Will upgrading to the required major version of the Calling SDK be enough, or will architectural changes also be required?

Is @azure/communication-calling@2.0.0 already the major version containing the breaking changes related to the 2028 transition?

Our main goal is to understand whether our current Teams identity + ACS Calling SDK architecture is already aligned with Microsoft's post-2028 model.

Thanks in advance.

Azure Communication Services
0 comments

1 answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-10-01T14:50:51.2866667+00:00

    Yes. A custom client that uses the Azure Communication Services Calling SDK with a real Teams user identity is aligned with the documented Teams user interoperability model.

    Supported facts from the documentation:

    1. Teams user custom clients are a supported interoperability model The Teams interoperability documentation defines a Teams user model where Microsoft Entra ID controls authentication, users must have Teams licenses, and calling is available via the Communication Services Calling SDKs. It also states that this model allows building custom applications for Teams users to enable specialized workflows or experiences.
    2. createTeamsCallAgent(...) matches the documented Teams user flow The calling SDK guidance for Teams users explicitly says to:
      • obtain a Teams user access token
      • create a CallClient
      • use createTeamsCallAgent with CommunicationTokenCredential to manage incoming and outgoing calls for a Teams user.
    3. Calling between a custom Teams-identity client and a standard Teams client is supported by this model The Teams interoperability documentation says Teams user mode allows custom applications for Teams users, and the Calling SDK page says the SDK enables Teams user devices to drive voice and video communication experiences.
    4. A call where both endpoints are custom clients using Teams identities remains within the same Teams user model The documentation supports custom applications for Teams users and calling via the Calling SDKs. That means both endpoints being custom clients with Teams identities still fits the documented Teams user interoperability pattern.

    On the 2028 transition:

    1. The Calling SDK is not listed as retiring; it is listed under services with breaking changes The ACS updates page says Azure Communication Services retires as a standalone offering on September 30, 2028, and lists Voice and Video Calling SDK under services with breaking changes, not under retiring services.
    2. The documentation does not say that upgrading the SDK alone will always be sufficient The retirement guide says some services remain available with breaking changes that require migration to supported Teams-aligned scenarios. It also says, for required operations, to verify supported endpoint and participant types, SDK version, permissions, licensing, and feature limitations. That supports this conclusion:
      • the current architecture is already in a Teams-aligned direction because it uses Teams identities and the Teams user Calling SDK model
      • but the documentation does not state that simply upgrading to a major SDK version is always enough
      • feature-by-feature validation may still be required
    3. The documentation provided does not confirm whether @azure/communication-calling@2.0.0 is the specific major version for the 2028 breaking changes The context mentions that supported configurations must be validated against SDK version and feature limitations, but it does not map npm version 2.0.0 to the 2028 transition. So that specific version question is not answered in the provided documentation.

    Practical conclusion:

    • Yes: the described architecture—MSAL/Entra sign-in, token exchange for a Teams user, and createTeamsCallAgent(...) in a custom web app—is consistent with the documented Teams user interoperability model.
    • Yes: this remains true when the other endpoint is another custom client using the same Teams identity flow.
    • No documented confirmation: the provided documentation does not say that upgrading to 2.0.0 alone is sufficient, and it does not identify 2.0.0 as the transition version.
    • Documented requirement: validate the exact calling operations, endpoint types, permissions, licensing, and SDK version against the retirement guidance. If the required configuration is not covered, the retirement guide says to contact Azure support before relying on that configuration for migration.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    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.