Merge pull request #298880 from vac0224/vc-call-automation-2025-04-28

Add Call Automation line 30

Author: prmerger-automator[bot]

articles/communication-services/concepts/authentication.md

@@ -1,12 +1,10 @@
 ---
 title: Authenticate to Azure Communication Services
 titleSuffix: An Azure Communication Services article
-description: This article describes how you can use an app or service to authenticate to Communication Services.
+description: This article describes how you can use an app or service to authenticate to Azure Communication Services.
 author: tophpalmer
-
 manager: chpalm
 services: azure-communication-services
-
 ms.author: chpalm
 ms.date: 09/05/2024
 ms.topic: conceptual
@@ -16,9 +14,9 @@ ms.subservice: identity
 
 # Authenticate to Azure Communication Services
 
-Every client interaction with Azure Communication Services needs to be authenticated. In a typical architecture, see [client and server architecture](./client-and-server-architecture.md), *access keys* or *Microsoft Entra authentication* are used for server-side authentication.
+Every client interaction with Azure Communication Services needs to be authenticated. In a typical architecture, see [client and server architecture](./client-and-server-architecture.md), *access keys* or *Microsoft Entra ID authentication* are used for server-side authentication.
 
-Another type of authentication uses *user access tokens* to authenticate against services that require user participation. For example, the chat or calling service utilizes *user access tokens* to allow users to be added in a thread and have conversations with each other.
+Another type of authentication uses *user access tokens* to authenticate against services that require user participation. For example, the chat or calling service utilizes *user access tokens* to enable users to be added in a thread and have conversations with each other.
 
 ## Authentication Options
 
@@ -29,6 +27,7 @@ The following table shows the Azure Communication Services SDKs and their authen
 | Identity           | Access Key or Microsoft Entra authentication |
 | SMS                | Access Key or Microsoft Entra authentication |
 | Phone Numbers      | Access Key or Microsoft Entra authentication |
+| Call Automation    | Access Key or Microsoft Entra authentication |
 | Email              | Access Key or Microsoft Entra authentication |
 | Advanced Messaging | Access Key or Microsoft Entra authentication |
 | Calling            | User Access Token                            |
@@ -46,28 +45,25 @@ If you wish to call Azure Communication Services' APIs manually using an access
 
 <a name='azure-ad-authentication'></a>
 
-
-
 To set up a service principal, [create a registered application from the Azure CLI](../quickstarts/identity/service-principal.md?pivots=platform-azcli). Then, the endpoint and credentials can be used to authenticate the SDKs. See examples of how [service principal](../quickstarts/identity/service-principal.md) is used.
 
-Communication services supports Microsoft Entra ID authentication for Communication services resources. You can find more details, about the managed identity support in the [How to use Managed Identity with Azure Communication Services](/azure/communication-services/how-tos/managed-identity).
+Azure Communication services supports Microsoft Entra ID authentication for Communication Services resources. For more information about managed identity support, see [How to use Managed Identity with Azure Communication Services](/azure/communication-services/how-tos/managed-identity).
 
 ### Microsoft Entra ID Authentication
 
 The Azure platform provides role-based access (Azure RBAC) to control access to resources. Azure RBAC security principal represents a user, group, service principal, or managed identity that is requesting access to Azure resources. Microsoft Entra ID authentication provides superior security and ease of use over other authorization options.
 
 - **Managed Identity:**
-  - By using managed identity, you avoid having to store your account access key within your code, as you do with Access Key authorization. Managed identity credentials are fully managed, rotated, and protected by the platform, reducing the risk of credential exposure.
+  - By using managed identity, you avoid having to store your account access key within your code, as you do with Access Key authorization. The platform fully manages, rotates, and protects identity credentials, reducing the risk of credential exposure.
   - Managed identities can authenticate to Azure services and resources that support Microsoft Entra ID authentication. This method provides a seamless and secure way to manage credentials.
   - For more information about using Managed Identity with Azure Communication Services, see [Managed Identity](../how-tos/managed-identity.md). 
 
 - **Service Principal:**
-  - To set up a service principal [create a registered application from the Azure CLI](../quickstarts/identity/service-principal.md?pivots=platform-azcli). Then, you can use the endpoint and credentials to authenticate the SDKs.
-  - See examples of how [service principal](../quickstarts/identity/service-principal.md) is used.
+  - To set up a service principal, [create a registered application from the Azure CLI](../quickstarts/identity/service-principal.md?pivots=platform-azcli). Then use the endpoint and credentials to authenticate the SDKs.
+  - For examples, see [service principal](../quickstarts/identity/service-principal.md).
 
 Communication Services supports Microsoft Entra ID authentication for Communication Services resources, While you can continue to use Access Key authorization with communication services applications, Microsoft recommends moving to Microsoft Entra ID where possible.
 
-
 Use our [Trusted authentication service hero sample](../samples/trusted-auth-sample.md) to map Azure Communication Services access tokens with your Microsoft Entra ID.
 
 ### User Access Tokens