You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can use Azure Communication Services and Graph API to build Azure Communication Services support Teams identities to communicate with the Microsoft Teams client or other Azure Communication Services support Teams identities. With Azure Communication Services support Teams identities, you can customize a voice, video, chat, and screen-sharing experience for Teams users.
19
+
You can use Azure Communication Services and Graph API to integrate communication as Teams user into your products to communicate with other people in and outside your organization. With Azure Communication Services supporting Teams identities and Graph API, you can customize a voice, video, chat, and screen-sharing experience for Teams users.
20
20
21
21
You can use the Azure Communication Services Identity SDK to exchange Azure Active Directory (Azure AD) access tokens of Teams users for Communication Identity access tokens. The diagrams in the next sections demonstrate multitenant use cases, where fictional company Fabrikam is the customer of fictional company Contoso.
22
22
23
23
## Calling
24
24
25
25
Voice, video, and screen-sharing capabilities are provided via Azure Communication Services Calling SDKs. The following diagram shows an overview of the process you'll follow as you integrate your calling experiences with Azure Communication Services support Teams identities.
26
26
27
-
27
+
28
28
29
29
## Chat
30
30
31
-
Optionally, you can also use Azure Communication Services support Teams identities to integrate chat capabilities by using Graph APIs. For more information about the Graph API, see the [chat resource type](/graph/api/channel-post-messages) documentation.
31
+
Optionally, you can also use Graph API to integrate chat capabilities into your product. For more information about the Graph API, see the [chat resource type](/graph/api/channel-post-messages) documentation.
32
32
33
-
33
+
In this quickstart, you'll build a .NET console application to authenticate a Microsoft 365 user by using the Microsoft Authentication Library (MSAL) and retrieving a Microsoft Azure Active Directory (Azure AD) user token. You'll then exchange that token for an access token of Teams user with the Azure Communication Services Identity SDK. The access token for Teams user can then be used by the Communication Services Calling SDK to build Azure Communication Services support Teams identities.
20
+
In this quickstart, you'll build a .NET console application to authenticate a Microsoft 365 user by using the Microsoft Authentication Library (MSAL) and retrieving a Microsoft Azure Active Directory (Azure AD) user token. You'll then exchange that token for an access token of Teams user with the Azure Communication Services Identity SDK. The access token for Teams user can then be used by the Communication Services Calling SDK to integrate calling capability as Teams user.
21
21
22
22
> [!NOTE]
23
23
> When you're in a production environment, we recommend that you implement this exchange mechanism in back-end services, because requests for an exchange are signed with a secret.
@@ -37,7 +37,7 @@ The following sections will guide you through the steps for administrators, deve
37
37
38
38
The Administrator role has extended permissions in Azure AD. Members of this role can set up resources and can read information from the Azure portal. In the following diagram, you can see all actions that have to be executed by Administrators.
39
39
40
-
40
+
41
41
42
42
1. The Contoso Administrator creates or selects an existing *application* in Azure Active Directory. The property *Supported account types* defines whether users from various tenants can authenticate to the application. The property *Redirect URI* redirects a successful authentication request to the Contoso *server*.
43
43
1. The Contoso Administrator adds API permissions to `Teams.ManageCalls` and `Teams.ManageChats` from Communication Services.
@@ -112,7 +112,7 @@ The Contoso developer needs to set up the *client application* to authenticate u
112
112
113
113
The developer's required actions are shown in following diagram:
114
114
115
-
115
+
116
116
117
117
1. The Contoso developer configures the Microsoft Authentication Library (MSAL) to authenticate the user for the application that was created earlier by the Administrator for Communication Services Teams.ManageCalls and Teams.ManageChats permissions.
118
118
1. The Contoso developer initializes the Communication Services Identity SDK and exchanges the incoming Azure AD user token for the access token of Teams user via the identity SDK. The access token of Teams user is then returned to the *client application*.
@@ -145,14 +145,14 @@ For more information about setting up environments in public documentation, see
145
145
146
146
The user represents the Fabrikam users of the Contoso application. The user experience is shown in the following diagram:
147
147
148
-
148
+
149
149
150
150
1. The Fabrikam user uses the Contoso *client application* and is prompted to authenticate.
151
151
1. The Contoso *client application* uses the MSAL to authenticate the user against the Fabrikam Azure AD tenant for the Contoso application with Communication Services Teams.ManageCalls and Teams.ManageChats permissions.
152
152
1. Authentication is redirected to the *server*, as defined in the property *Redirect URI* in the MSAL and the Contoso application.
153
153
1. The Contoso *server* exchanges the Azure AD user token for the access token of Teams user by using the Communication Services Identity SDK and returns the access token of Teams user to the *client application*.
154
154
155
-
With a valid access token for Teams user in the *client application*, developers can integrate the Communication Services Calling SDK and build Azure Communication Services support Teams identities.
155
+
With a valid access token for Teams user in the *client application*, developers can integrate the Communication Services Calling SDK and manage calls as Teams user.
0 commit comments