Skip to content

Conversation

@v-dharmarajv
Copy link
Member

Adding the support for the microsoftteamsapp idenfier to add as participant and transfer

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for the MicrosoftTeamsAppIdentifier communication identifier type to the Call Automation SDK, enabling it to be used when adding participants and transferring calls.

Changes:

  • Added new constructors to TransferToParticipantOptions and CallInvite classes that accept MicrosoftTeamsAppIdentifier
  • Updated API surface definitions across all target frameworks (netstandard2.0, net8.0, net10.0)
  • Updated CHANGELOG with the new feature for version 1.5.1

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
sdk/communication/Azure.Communication.CallAutomation/src/Models/TransferToParticipantOptions.cs Added constructor overload accepting MicrosoftTeamsAppIdentifier parameter
sdk/communication/Azure.Communication.CallAutomation/src/Models/CallInvite.cs Added constructor overload accepting MicrosoftTeamsAppIdentifier parameter
sdk/communication/Azure.Communication.CallAutomation/api/Azure.Communication.CallAutomation.netstandard2.0.cs Updated API surface to include new constructors
sdk/communication/Azure.Communication.CallAutomation/api/Azure.Communication.CallAutomation.net8.0.cs Updated API surface to include new constructors
sdk/communication/Azure.Communication.CallAutomation/api/Azure.Communication.CallAutomation.net10.0.cs Updated API surface to include new constructors
sdk/communication/Azure.Communication.CallAutomation/CHANGELOG.md Added entry for version 1.5.1 documenting MicrosoftTeamsAppIdentifier support

@github-actions
Copy link

github-actions bot commented Jan 21, 2026

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Azure.Communication.CallAutomation

Copy link
Contributor

Copilot AI commented Jan 22, 2026

@v-dharmarajv I've opened a new pull request, #55193, to work on those changes. Once the pull request is ready, I'll request review from you.

Copy link
Contributor

Copilot AI commented Jan 22, 2026

@v-dharmarajv I've opened a new pull request, #55194, to work on those changes. Once the pull request is ready, I'll request review from you.

Copilot AI and others added 4 commits January 22, 2026 11:43
* Initial plan

* Add parameter descriptions to CallInvite constructors

Co-authored-by: v-dharmarajv <146493756+v-dharmarajv@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: v-dharmarajv <146493756+v-dharmarajv@users.noreply.github.com>
/// <param name="targetIdentity">The Microsoft Teams App identifier of the target participant.</param>
public CallInvite(MicrosoftTeamsAppIdentifier targetIdentity)
{
Target = targetIdentity;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we do null checking here?

Comment on lines +173 to +176
else if (targetParticipant is MicrosoftTeamsAppIdentifier)
{
options = new TransferToParticipantOptions(targetParticipant as MicrosoftTeamsAppIdentifier);
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: you can do this with the rest of them too

Suggested change
else if (targetParticipant is MicrosoftTeamsAppIdentifier)
{
options = new TransferToParticipantOptions(targetParticipant as MicrosoftTeamsAppIdentifier);
}
else if (targetParticipant is MicrosoftTeamsAppIdentifier mtai)
{
options = new TransferToParticipantOptions(mtai);
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants