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
Azure Communication Services enables you to send and receive WhatsApp messages using the Azure Communication Services Messaging SDK. You can use this SDK to engage in conversations with customers for product inquiry and customer service scenarios. You can also use it to send messages such as appointment reminders, shipping updates, two-factor authentication, and other notification scenarios.
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/email/email-overview.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@ ms.date: 03/31/2023
10
10
ms.topic: conceptual
11
11
ms.service: azure-communication-services
12
12
---
13
+
13
14
# Overview of Azure Communication Services email
14
15
15
16
Email continues to be a key customer engagement channel globally for businesses. Businesses rely heavily on email communication for seamless business operations.
@@ -22,7 +23,7 @@ Azure Communication Services email enables rich collaboration in communication m
22
23
23
24
With Azure Communication Services, you can speed up your market entry with scalable and reliable email features by using your own SMTP domains. As with other communication channels, when you use Azure Communication Services to send email, you pay for only what you use.
Azure Communication Services enables you to send and receive SMS text messages using the Communication Services SMS SDKs. These SDKs can be used to support customer service scenarios, appointment reminders, two-factor authentication, and other real-time communication needs. Communication Services SMS allows you to reliably send messages while exposing deliverability and response metrics.
21
+
Azure Communication Services enables you to send and receive short message service (SMS) text messages using the Communication Services SMS SDKs. These SDKs can be used to support customer service scenarios, appointment reminders, two-factor authentication, and other real-time communication needs. Communication Services SMS allows you to reliably send messages while exposing deliverability and response metrics.
@@ -45,17 +45,21 @@ Applications can implement both authentication models and leave the choice of au
45
45
46
46
## External user
47
47
48
-
The *bring your own identity* (BYOI) authentication model enables you to build custom applications for external users to connect and communicate with Teams users. You control user authentication, and users of your custom applications don't need to have Microsoft Entra identities or Teams licenses. The first scenario enables your application's users to join Microsoft Teams meetings using external accounts, similar to [anonymous users that join meetings](/microsoftteams/meeting-settings-in-teams#allow-anonymous-users-to-join-meetings) using the Teams web application. This is ideal for business-to-consumer applications that combine employees (familiar with Teams) and external users (using a custom application) into a meeting experience. In the future, we plan to implement more scenarios, including direct calling and chat to enable your application to initiate calls and chats with Teams users outside the context of a Teams meeting.
48
+
The *bring your own identity* (BYOI) authentication model enables you to build custom applications for external users to connect and communicate with Teams users. You control user authentication, and users of your custom applications don't need to have Microsoft Entra identities or Teams licenses.
49
+
50
+
The first scenario enables your application's users to join Microsoft Teams meetings using external accounts, similar to [anonymous users that join meetings](/microsoftteams/meeting-settings-in-teams#allow-anonymous-users-to-join-meetings) using the Teams web application. This feature is ideal for business-to-consumer applications that combine employees (familiar with Teams) and external users (using a custom application) into a meeting experience.
51
+
52
+
In the future, we plan to implement more scenarios, including direct calling and chat to enable your application to initiate calls and chats with Teams users outside the context of a Teams meeting.
49
53
50
54
For more information, see [Join a Teams meeting](join-teams-meeting.md).
51
55
52
56
It's currently not possible for a Teams user to join a call that was initiated using the Azure Communication Services Calling SDK.
53
57
54
58
## Teams user
55
59
56
-
Developers can use [Communication Services Calling SDK with Teams identity](./interop/teams-user-calling.md) to build custom applications for Teams users. Custom applications can enable specialized workflows for Teams users, such as managing incoming and outgoing phone calls or bringing Teams calling experience into devices not supported with the standard Teams client. Microsoft Entra authenticates Teams users, and all attributes and details about the user are bound to their Microsoft Entra account.
60
+
Developers can use [Communication Services Calling SDK with Teams identity](./interop/teams-user-calling.md) to build custom applications for Teams users. Custom applications can enable specialized workflows for Teams users. Specialized workflows include managing incoming and outgoing phone calls or bringing Teams calling experience into devices not supported with the standard Teams client. Microsoft Entra authenticates Teams users, and all attributes and details about the user are bound to their Microsoft Entra account.
57
61
58
-
When a Communication Services endpoint connects to a Teams meeting or Teams call using a Teams identity, the endpoint is treated like a Teams user with a Teams client. The experience is driven by policies assigned to users within and outside of the organization. Teams users can join Teams meetings, place calls to other Teams users, receive calls from phone numbers, and transfer an ongoing call to the Teams call queue or share screen.
62
+
When a Communication Services endpoint connects to a Teams meeting or Teams call using a Teams identity, the endpoint is treated like a Teams user with a Teams client. The experience follows policies assigned to users within and outside of the organization. Teams users can join Teams meetings, place calls to other Teams users, receive calls from phone numbers, and transfer an ongoing call to the Teams call queue or share screen.
59
63
60
64
Teams users authenticate against Microsoft Entra ID in the client application. Developers then exchange authentication tokens from Microsoft Entra ID for access tokens via the Communication Services Identity SDK. This exchange creates a connection between Microsoft Entra ID and Communication Services. You're encouraged to implement an exchange of tokens in your backend services as credentials for Azure Communication Services sign exchange requests. In your backend services, you can require any other authentication.
61
65
@@ -76,14 +80,16 @@ Using the Teams identity authentication model, a Communication Services applicat
76
80
## Privacy
77
81
Interoperability between Azure Communication Services and Microsoft Teams enables your applications and users to participate in Teams calls, meetings, and chats. It is your responsibility to ensure that the users of your application are notified when recording or transcription are enabled in a Teams call or meeting.
78
82
79
-
Microsoft indicates to you via the Azure Communication Services API that recording or transcription has begun, and you must communicate this fact, in real-time, to your users within your application's user interface. You agree to indemnify Microsoft for all costs and damages incurred due to your failure to comply with this obligation.
83
+
Microsoft indicates to you via the Azure Communication Services API that recording or transcription is in progress. You must communicate this fact, in real-time, to your users within your application's user interface. You agree to indemnify Microsoft for all costs and damages incurred due to your failure to comply with this obligation.
80
84
81
85
## Pricing
82
-
All usage of Azure Communication Service APIs and SDKs increments [Azure Communication Service billing meters](https://azure.microsoft.com/pricing/details/communication-services/). Interactions with Microsoft Teams, such as joining a meeting or initiating a phone call using a Teams allocated number, increment these meters. However, there is no additional fee for the Teams interoperability capability itself, and there is no pricing distinction between the BYOI and Microsoft 365 authentication options.
86
+
87
+
All usage of Azure Communication Service APIs and SDKs increments [Azure Communication Service billing meters](https://azure.microsoft.com/pricing/details/communication-services/). Interactions with Microsoft Teams, such as joining a meeting or initiating a phone call using a Teams allocated number, increment these meters. However, there is no added fee for the Teams interoperability capability itself, and there is no pricing distinction between the BYOI and Microsoft 365 authentication options.
83
88
84
89
If your Azure application has a user spend 10 minutes in a meeting with a user of Microsoft Teams, those two users combined consumed 20 calling minutes. The 10 minutes exercised through the custom application and using Azure APIs and SDKs are billed to your resource. However, the 10 minutes consumed by the user in the native Teams application is covered by the applicable Teams license and is not metered by Azure.
85
90
86
91
## Trademark and brand guideline
92
+
87
93
Third parties must follow the [Microsoft Trademark and Brand Guidelines](https://www.microsoft.com/legal/intellectualproperty/trademarks) when using Microsoft Teams trademarks or product logos in advertising or promotional materials. In general, wordmarks can be used to truthfully convey information about your product or service, as long as customers and the public are not confused into believing Microsoft is affiliated with or endorses your product or service. However, our logos, app, product icons, illustrations, photographs, videos, and designs can never be used without an express license. To get more details about branding, read [Microsoft Trademark and Brand Guidelines](https://www.microsoft.com/legal/intellectualproperty/trademarks).
88
94
89
95
Third party use of Microsoft Teams branding is only allowed for certified Teams partners. Without a license arrangement or certification with Microsoft, everything in your app or product (including developer name, app name, logo, description, screenshots, and other app collateral) must be unique to (company name) and free of Microsoft’s Brand Assets. The only exception is that you may truthfully state whether your app is compatible or interoperable with a Microsoft product or service within the text description about their app.
0 commit comments