Headings reconciled with TOC

Initial commit, batch 1 of 10

Author: vac0224

articles/communication-services/concepts/authentication.md

@@ -1,7 +1,7 @@
 ---
 title: Authenticate to Azure Communication Services
-titleSuffix: An Azure Communication Services concept document
-description: Learn about the various ways an app or service can authenticate to 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.
 author: tophpalmer
 
 manager: chpalm
@@ -34,15 +34,15 @@ The following table shows the Azure Communication Services SDKs and their authen
 | Calling            | User Access Token                            |
 | Chat               | User Access Token                            |
 
-Each authorization option is briefly described below:
+Each authorization option is briefly described as follows:
 
 ### Access Key
 
-Access key authentication is suitable for service applications running in a trusted service environment. Your access key can be found in the Azure Communication Services portal. The service application uses it as a credential to initialize the corresponding SDKs. See an example of how it is used in the [Identity SDK](../quickstarts/identity/access-tokens.md). 
+Access key authentication is suitable for service applications running in a trusted service environment. Your access key can be found in the Azure Communication Services portal. The service application uses it as a credential to initialize the corresponding SDKs. See an example of how it's used in the [Identity SDK](../quickstarts/identity/access-tokens.md). 
 
 Since the access key is part of the connection string of your resource, authentication with a connection string is equivalent to authentication with an access key.
 
-If you wish to call Azure Communication Services' APIs manually using an access key, then you will need to sign the request. Signing the request is explained, in detail, within a [tutorial](../tutorials/hmac-header-tutorial.md).
+If you wish to call Azure Communication Services' APIs manually using an access key, then you need to sign the request. Signing the request is explained, in detail, within a [tutorial](../tutorials/hmac-header-tutorial.md).
 
 <a name='azure-ad-authentication'></a>
 
@@ -52,23 +52,17 @@ To set up a service principal, [create a registered application from the Azure C
 
 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).
 
-
-
-
-
 ### 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.
   - 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 on how to use Managed Identity with Azure Communication Services, refer to [This Guide](/azure/communication-services/how-tos/managed-identity). 
-  
-  
+  - 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, the endpoint and credentials can be used to authenticate the SDKs.
+  - 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.
 
 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.
@@ -78,7 +72,7 @@ Use our [Trusted authentication service hero sample](../samples/trusted-auth-sam
 
 ### User Access Tokens
 
-User access tokens are generated using the Identity SDK and are associated with users created in the Identity SDK. See an example of how to [create users and generate tokens](../quickstarts/identity/access-tokens.md). Then, user access tokens are used to authenticate participants added to conversations in the Chat or Calling SDK. For more information, see [add chat to your app](../quickstarts/chat/get-started.md). User access token authentication is different compared to access key and Microsoft Entra authentication in that it is used to authenticate a user rather than a secured Azure resource.
+User access tokens are generated using the Identity SDK and are associated with users created in the Identity SDK. See an example of how to [create users and generate tokens](../quickstarts/identity/access-tokens.md). Then, user access tokens are used to authenticate participants added to conversations in the Chat or Calling SDK. For more information, see [add chat to your app](../quickstarts/chat/get-started.md). User access token authentication is different compared to access key and Microsoft Entra authentication in that it's used to authenticate a user rather than a secured Azure resource.
 
 ## Using identity for monitoring and metrics
 

articles/communication-services/concepts/european-union-data-boundary.md

@@ -1,6 +1,7 @@
 ---
 title: European Union Data Boundary compliance for Azure Communication Services
-description: Learn about how Azure Communication Services meets European Union data handling compliance laws
+titleSuffix: An Azure Communication Services article
+description: This article describes how Azure Communication Services meets European Union data handling compliance laws
 author: hrazi
 manager: mharbut
 services: azure-communication-services
@@ -14,47 +15,48 @@ ms.custom: references_regions
 
 # European Union Data Boundary (EUDB)
 
-Azure Communication Services complies with European Union Data Boundary (EUDB) [announced by Microsoft Dec 15, 2022](https://blogs.microsoft.com/eupolicy/2022/12/15/eu-data-boundary-cloud-rollout/). 
+Azure Communication Services complies with European Union Data Boundary (EUDB) [announced by Microsoft December 15, 2022](https://blogs.microsoft.com/eupolicy/2022/12/15/eu-data-boundary-cloud-rollout/). 
 
-This boundary defines data residency and processing rules for resources based on the data location selected when creating a new communication resource. When a data location for a resource is one of the European countries/regions in scope of EUDB, then all processing and storage of personal data  remain within the European Union. The EU Data Boundary consists of the countries/regions in the European Union (EU) and the European Free Trade Association (EFTA). The EU countries/regions are Austria, Belgium, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, and Sweden; and the EFTA countries/regions are Liechtenstein, Iceland, Norway, and Switzerland.
+This boundary defines data residency and processing rules for resources based on the data location selected when creating a new communication resource. When a data location for a resource is one of the European countries/regions in scope of EUDB, then all processing and storage of personal data remain within the European Union.
+
+The EU Data Boundary consists of the countries/regions in the European Union (EU) and the European Free Trade Association (EFTA). The EU countries/regions are: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, and Sweden. The EFTA countries/regions are: Liechtenstein, Iceland, Norway, and Switzerland.
 
 ## Calling
 
-Calls and meetings can be established in various ways by various users.  We define a few terms:
+Users can establish calls and meetings in various ways. We define a few terms:
 - Organizer: person who created the meeting, for example, set it up using Outlook
 - Initiator: the first person who joins the meeting (the meeting only exists as a calendar item before the first person joins it)
-- Guest: a participant who isn't a member of the tenant of the Organizer.  May include a member of a different tenant, PSTN (dial-in) user, etc. (Note that this use of Guest is specific to this description and broader than used within IC3 generally, but useful for the discussion here)
-- Call: refers to a 1:1 call and\or to a Group call to a larger group.  For the purposes of this conversation, they should be the same.
-- Real Time Text: RTT is an accessibility compliance requirement for voice and video platforms in the EU. You can find more information about this here: [Directive 2019/882](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019L0882)
+- Guest: a participant who isn't a member of the tenant of the Organizer. May include a member of a different tenant, PSTN (dial-in) user, and so on. In this article, *guest* is specific to this description and broader than used within IC3 generally.
+- Call: refers to a 1:1 call and\or to a Group call to a larger group. For the purposes of this conversation, they should be the same.
+- Real Time Text (RTT): is an accessibility compliance requirement for voice and video platforms in the EU. For more information, see: [Directive 2019/882](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019L0882).
 
-For EU communication resources, when the organizer, initiator, or guests join a call from the EU, processing and storage of personal data will be limited to the EU.
+For EU communication resources, when the organizer, initiator, or guests join a call from the EU, processing and storage of personal data is limited to the EU.
 
 ## SMS
 
-Azure Communication Services guarantees that SMS data within the EUDB is stored in EUDB regions. As of today, we process and store data in the Netherlands, Ireland or Switzerland regions, ensuring no unauthorized data transfer outside the EEA (European Economic Area).  
+Azure Communication Services guarantees that SMS data within the EUDB is stored in EUDB regions. As of today, we process and store data in the Netherlands, Ireland, or Switzerland regions, ensuring no unauthorized data transfer outside the EEA (European Economic Area). 
 Also, Azure Communication Services employs advanced security measures, including encryption, to protect SMS data both at rest and in transit. Customers can select their preferred data residency within the EUDB, making sure data remains within the designated EU regions. 
 
 #### SMS EUDB FAQ
 
 **What happens with SMS data in the UK?** 
 
-While the UK is no longer part of the EU, Azure Communication Services processes data for the UK within the EUDB. As of today, data processing and storage occur within the Netherlands, Ireland or Switzerland regions, maintaining compliance with EU regulations.  
+While the UK is no longer part of the EU, Azure Communication Services processes data for the UK within the EUDB. As of today, data processing and storage occur within the Netherlands, Ireland, or Switzerland regions, maintaining compliance with EU regulations. 
 
 **What happens when an SMS recipient is outside the EU?** 
 
-If an SMS recipient is outside the EU, the core data processing and storage remain within the EUDB (Netherlands, Ireland or Switzerland regions). However, for the SMS to be delivered, it may be routed through networks outside the EU, depending on the recipient's location and carrier, which is necessary for successful message delivery. 
+If an SMS recipient is outside the EU, the core data processing and storage remain within the EUDB (Netherlands, Ireland, or Switzerland regions). However, for the SMS to be delivered, it may be routed through networks outside the EU, depending on the recipient's location and carrier, which is necessary for successful message delivery. 
 
 **Can data be transferred to non-EU regions under any circumstances?** 
 
-Yes, to deliver SMS to recipients outside the EU, some data routing may occur outside the EUDB, but this is strictly for message delivery purposes. Data processing and storage at rest still comply with the EUDB regulations. 
+Yes, to deliver SMS to recipients outside the EU, some data routing may occur outside the EUDB. This routing is strictly for message delivery purposes. Data processing and storage at rest still comply with the EUDB regulations. 
 
 
 ## Messaging
 
-All threads created from an EU resource will process and storage personal data in the EU. 
+All threads created from an EU resource process and store personal data in the EU. 
 
 
-## Other resources
+## Related articles
 
-For more information, please refer to the Microsoft documentation on the EUDB:
-- [Microsoft EU Data Boundary Overview](https://www.microsoft.com/en-us/trust-center/privacy/european-data-boundary-eudb)
+For more information, see [Microsoft EU Data Boundary Overview](https://www.microsoft.com/en-us/trust-center/privacy/european-data-boundary-eudb).

articles/communication-services/concepts/government.md

@@ -1,6 +1,7 @@
 ---
-title: Azure Communication Services in Azure Government 
-description: Learn about using Azure Communication Services in US Government regions
+title: Azure Communication Services in Azure Government
+titleSuffix: An Azure Communication Services article
+description: This article describes Azure Communication Services in US Government regions.
 author: hrazi
 manager: mharbut
 services: azure-communication-services
@@ -11,29 +12,34 @@ ms.topic: conceptual
 ms.service: azure-communication-services
 ---
 
-
-
-
 # Azure Communication Services for US Government
 
 [!INCLUDE [Public Preview Notice](../includes/public-preview-include.md)]
 
-Azure Communication Services (ACS) can be used within [Azure Government](https://azure.microsoft.com/global-infrastructure/government/) to provide compliance with US government requirements for cloud services. In addition to enjoying the features and capabilities of Messaging, Voice and Video calling, developers benefit from the following features that are unique to Azure Government:
+You can use Azure Communication Services within [Azure Government](https://azure.microsoft.com/global-infrastructure/government/) to provide compliance with US government requirements for cloud services. In addition to enjoying the features and capabilities of Messaging, Voice and Video calling, developers benefit from the following features that are unique to Azure Government:
 - Your personal data is logically segregated from customer content in the commercial Azure cloud.
 - Your resource’s customer content is stored within the United States.
 - Access to your organization's customer content is restricted to screened Microsoft personnel. 
 
-Azure Communication Services in Azure Government is currently In Process for the FedRAMP High accreditation as part of the [M365 GCC-High service offering](https://marketplace.fedramp.gov/products/FR1824057433). Once the FedRAMP High certification process is completed and the authorization is granted, Azure Communication Services in the Azure Government cloud will GA and be officially recognized as meeting the requirements set forth by the FedRAMP, providing government customers with the confidence that the service is secure and compliant with federal standards.
+Azure Communication Services in Azure Government is currently In Process for the FedRAMP High accreditation as part of the [Microsoft 365 Government Community Cloud (GCC) - High service offering](https://marketplace.fedramp.gov/products/FR1824057433). Once the FedRAMP High certification process is completed and the authorization is granted, Azure Communication Services in the Azure Government cloud moves to GA. Then the government services officially meet the requirements of FedRAMP. Government customers can then use the service that is secure and compliant with federal standards.
+
+## General availability and feature releases
 
-## General Availability and Upcoming Feature Releases
-Azure Communication Services for US Government is scheduled for General Availability (GA) in 2025. The initial release will focus on delivering core capabilities, including basic video calling and messaging, to provide government customers with a secure and compliant communication solution.
+Azure Communication Services for US Government is scheduled for General Availability (GA) in 2025. The initial release focuses on delivering core capabilities, including basic video calling and messaging, to provide government customers with a secure and compliant communication solution.
 
-Additional advanced features, such as:
+Following GA, we expect to release advanced features such as:
 - Call Logs
 - Call Records
 - Transcriptions
 - Live Captions
 - Email Integration
-will be introduced in a subsequent release later in 2025, following GA. Azure Communication Services is committed to releasing these features as part of its roadmap, ensuring feature parity with Azure Communication Services Commercial within six months of each feature becoming available in the commercial cloud.
 
-You can find more information about the Office 365 Government – GCC High offering for US Government customers at [Office 365 Government plans](https://products.office.com/government/compare-office-365-government-plans). Please see [eligibility requirements](https://azure.microsoft.com/global-infrastructure/government/how-to-buy/) for Azure Government. 
+Azure Communication Services is committed to releasing these features as part of its roadmap. Regular releases ensure feature parity with Azure Communication Services Commercial within six months of each feature becoming available in the commercial cloud.
+
+## Related articles
+
+- [Office 365 Government plans](https://www.microsoft.com/en-us/microsoft-365/enterprise/government-plans-and-pricing)
+
+- [Office 365 GCC High and DoD](/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc-high-and-dod)
+
+- [Eligibility requirements for Azure Government](https://azure.microsoft.com/en-us/explore/global-infrastructure/government/how-to-buy/)