Each of the components in the diagram all contain their own native Teams client and are actively registered to the Teams service. Notice that in all the diagram below there are no lines of communication depicted directly between the clients and devices. The same basic pattern of communications is utilized throughout all of the scenarios covered in this article. Yet, in Microsoft Teams at no point do any of these client or devices actually “pair” directly with each other, nor communicate directly between each other. Sometimes these are clients which are both registered to Teams with the same user account while in other scenarios different user accounts are registered to each. In Microsoft Teams there are several different scenarios where separate Teams clients and devices can communicate between each other to provide some beneficial feature or capability. The word “pairing” was specifically included as that term is commonly used for categorizing the behavior of tying multiple devices together. Yes, then the title of this article is purposely misleading.
The most important concept to understand in this article is that there is actually no direct pairing happening between the Teams clients among these scenarios. The purpose of this article is to demystify a common misconception with how Microsoft Teams allows various types of clients and devices to communicate between each other when leveraging several different native features.
0 kommentar(er)
