Skip to content

Commit e8ee2bb

Browse files
Merge pull request #273257 from ashwinder/patch-4
update note for 1:1 call experience
2 parents ff0819a + 5dd00ba commit e8ee2bb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ On the Microsoft Teams desktop client, Jack's call will be sent to the Microsoft
137137

138138
![Screenshot of Microsoft Teams desktop client, Jack's call is sent to the Microsoft Teams user through an incoming call toast notification.](./media/incoming-call-toast-notification-teams-user.png)
139139

140-
After the Microsoft Teams user accepts the call, the in-call experience for the Microsoft Teams user will have all the participants displayed on the Microsoft Teams roster. Note that your application that is managing the call using Call Automation API will remain hidden to Teams user on the call screen.
140+
After the Microsoft Teams user accepts the call, the in-call experience for the Microsoft Teams user will have all the participants displayed on the Microsoft Teams roster. Note that your application that is managing the call using Call Automation API will remain hidden to Teams user on the call screen, except in the case where you start a 1:1 call with the Teams user.
141141
![Screenshot of Microsoft Teams user accepting the call and entering the in-call experience for the Microsoft Teams user.](./media/active-call-teams-user.png)
142142

143143
## Step 4: Remove a Teams user from an existing Communication Services call controlled by Call Automation APIs

0 commit comments

Comments
 (0)