Merge pull request #265076 from maud-lv/ml-sentencetable

Clarify table content

Author: v-regandowner

articles/service-connector/how-to-integrate-app-configuration.md

@@ -1,26 +1,29 @@
 ---
 title: Integrate Azure App Configuration with Service Connector
-description: Integrate Azure App Configuration into your application with Service Connector
+description: In this document, learn how to integrate Azure App Configuration into your application with Service Connector
 author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: how-to
-ms.date: 10/26/2023
+ms.date: 02/02/2024
 ---
+
 # Integrate Azure App Configuration with Service Connector
 
 This page shows supported authentication methods and clients, and shows sample code you can use to connect Azure App Configuration to other cloud services using Service Connector. You might still be able to connect to App Configuration using other methods. This page also shows default environment variable names and values you get when you create the service connection. 
 
 ## Supported compute services
 
+Service Connector can be used to connect the following compute services to Azure App Configuration:
+
 - Azure App Service
 - Azure Functions
 - Azure Container Apps
 - Azure Spring Apps
 
 ## Supported authentication types and client types
 
-Supported authentication and clients for App Service, Azure Functions, Container Apps and Azure Spring Apps:
+The table below shows which combinations of authentication methods and clients are supported for connecting your compute service to Azure App Configuration using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
 
 
 | Client type | System-assigned managed identity | User-assigned managed identity | Secret/connection string | Service principal |
@@ -31,7 +34,7 @@ Supported authentication and clients for App Service, Azure Functions, Container
 | Python      |                Yes               |               Yes              |            Yes           |        Yes        |
 | None        |                Yes               |               Yes              |            Yes           |        Yes        |
 
----
+This table indicates that all combinations of client types and authentication methods in the table are supported. All client types can use any of the authentication methods to connect to Azure App Configuration using Service Connector.
 
 ## Default environment variable names or application properties and sample code
 

articles/service-connector/how-to-integrate-confluent-kafka.md

@@ -1,27 +1,30 @@
 ---
-title: Integrate Apache kafka on Confluent Cloud with Service Connector
-description: Integrate Apache kafka on Confluent Cloud into your application with Service Connector
+title: Integrate Apache Kafka on Confluent Cloud with Service Connector
+description: In this document, learn how to integrate Apache Kafka on Confluent Cloud into your application with Service Connector
 author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: how-to
-ms.date: 11/07/2023
+ms.date: 02/02/2024
 ms.custom: event-tier1-build-2022
 ---
+
 # Integrate Apache Kafka on Confluent Cloud with Service Connector
 
 This page shows supported authentication methods and clients to connect Apache Kafka on Confluent Cloud to other cloud services using Service Connector. You might still be able to connect to Apache Kafka on Confluent Cloud in other programming languages without using Service Connector. This page also shows default environment variable names and values (or Spring Boot configuration) you get when you create the service connection. 
 
 ## Supported compute services
 
+Service Connector can be used to connect the following compute services to Apache Kafka on Confluent Cloud:
+
 - Azure App Service
 - Azure Functions
 - Azure Container Apps
 - Azure Spring Apps
 
 ## Supported Authentication types and client types
 
-Supported authentication and clients for App Service, Azure Functions, Container Apps and Azure Spring Apps:
+The table below shows which combinations of client types and authentication methods are supported for connecting your compute service to Apache Kafka on Confluent Cloud using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
 
 | Client type        | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
 |--------------------|----------------------------------|--------------------------------|----------------------------|-------------------|
@@ -32,6 +35,8 @@ Supported authentication and clients for App Service, Azure Functions, Container
 | Python             | No                               | No                             | Yes                        | No                |
 | None               | No                               | No                             | Yes                        | No                |
 
+This table indicates that the only supported authentication method for all client types in the table is the Secret / connection string method. Other authentication methods are not supported for any of the client types.
+
 ## Default environment variable names or application properties
 
 Use the connection details below to connect compute services to Kafka. For each example below, replace the placeholder texts `<server-name>`, `<Bootstrap-server-key>`, `<Bootstrap-server-secret>`, `<schema-registry-key>`, and `<schema-registry-secret>` with your server name, Bootstrap server key, Bootstrap server secret, schema registry key, and schema registry secret. For more information about naming conventions, check the [Service Connector internals](concept-service-connector-internals.md#configuration-naming-convention) article. Refer to [Kafka Client Examples](https://docs.confluent.io/cloud/current/client-apps/examples.html#) to build Kafka client applications on Confluent Cloud.

articles/service-connector/how-to-integrate-cosmos-cassandra.md

@@ -1,27 +1,30 @@
 ---
-title: Integrate the Azure Cosmos DB for Apache Cassandra with Service Connector
+title: Integrate Azure Cosmos DB for Apache Cassandra with Service Connector
 description: Integrate the Azure Cosmos DB for Apache Cassandra into your application with Service Connector
 author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: how-to
-ms.date: 10/25/2023
+ms.date: 02/02/2024
 ms.custom: event-tier1-build-2022, ignite-2022
 ---
+
 # Integrate Azure Cosmos DB for Cassandra with Service Connector
 
 This page shows supported authentication methods and clients, and shows sample code you can use to connect Azure Cosmos DB for Apache Cassandra to other cloud services using Service Connector. You might still be able to connect to the Azure Cosmos DB for Cassandra in other programming languages without using Service Connector. This page also shows default environment variable names and values (or Spring Boot configuration) you get when you create the service connection. 
 
 ## Supported compute services
 
+Service Connector can be used to connect the following compute services to Azure Cosmos DB for Apache Cassandra:
+
 - Azure App Service
 - Azure Functions
 - Azure Container Apps
 - Azure Spring Apps
 
 ## Supported authentication types and client types
 
-Supported authentication and clients for App Service, Azure Functions, Container Apps and Azure Spring Apps:
+The table below shows which combinations of client types and authentication methods are supported for connecting your compute service to Azure Cosmos DB for Apache Cassandra using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
 
 | Client type        | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
 |--------------------|----------------------------------|--------------------------------|----------------------------|-------------------|
@@ -33,7 +36,7 @@ Supported authentication and clients for App Service, Azure Functions, Container
 | Python             | Yes                              | Yes                            | Yes                        | Yes               |
 | None               | Yes                              | Yes                            | Yes                        | Yes               |
 
----
+This table indicates that all combinations of client types and authentication methods in the table are supported, except for the Java - Spring Boot client type, which only supports the Secret / connection string method. All other client types can use any of the authentication methods to connect to Azure Cosmos DB for Apache Cassandra using Service Connector.
 
 ## Default environment variable names or application properties and Sample code
 

articles/service-connector/how-to-integrate-cosmos-db.md

@@ -5,24 +5,26 @@ author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: how-to
-ms.date: 12/04/2023
+ms.date: 02/02/2024
 ms.custom: event-tier1-build-2022, ignite-2022
+
 ---
 # Integrate Azure Cosmos DB for MongoDB with Service Connector
 
 This page shows supported authentication methods and clients, and shows sample code you can use to connect the Azure Cosmos DB for MongoDB to other cloud services using Service Connector. You might still be able to connect to Azure Cosmos DB for MongoDB in other programming languages without using Service Connector. This page also shows default environment variable names and values (or Spring Boot configuration) you get when you create the service connection. 
 
 ## Supported compute services
 
+Service Connector can be used to connect the following compute services to Azure Cosmos DB for MongoDB:
+
 - Azure App Service
 - Azure Functions
 - Azure Container Apps
 - Azure Spring Apps
 
 ## Supported authentication types and client types
 
-Supported authentication and clients for App Service, Azure Functions, Container Apps, and Azure Spring Apps:
-
+The table below shows which combinations of client types and authentication methods are supported for connecting your compute service to Azure Cosmos DB for MongoDB using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
 
 | Client type        | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
 |--------------------|----------------------------------|--------------------------------|----------------------------|-------------------|
@@ -34,7 +36,7 @@ Supported authentication and clients for App Service, Azure Functions, Container
 | Go                 | Yes                              | Yes                            | Yes                        | Yes               |
 | None               | Yes                              | Yes                            | Yes                        | Yes               |
 
----
+This table indicates that all combinations of client types and authentication methods in the table are supported, except for the Java - Spring Boot client type, which only supports the Secret / connection string method. All other client types can use any of the authentication methods to connect to Azure Cosmos DB for MongoDB using Service Connector.
 
 ## Default environment variable names or application properties and sample code
 

articles/service-connector/how-to-integrate-cosmos-gremlin.md

@@ -1,27 +1,30 @@
 ---
-title: Integrate the Azure Cosmos DB for Apache Gremlin with Service Connector
+title: Integrate Azure Cosmos DB for Apache Gremlin with Service Connector
 description: Integrate the Azure Cosmos DB for Apache Gremlin into your application with Service Connector
 author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: how-to
-ms.date: 12/04/2023
+ms.date: 02/02/2024
 ms.custom: event-tier1-build-2022, ignite-2022
 ---
+
 # Integrate the Azure Cosmos DB for Gremlin with Service Connector
 
-This page shows supported authentication methods and clients, and shows sample code you can use to connect the Azure Cosmos DB for Apache Gremlin to other cloud services using Service Connector. You might still be able to connect to the Azure Cosmos DB for Gremlin in other programming languages without using Service Connector. This page also shows default environment variable names and values you get when you create the service connection.
+This page shows supported authentication methods and clients, and shows sample code you can use to connect Azure Cosmos DB for Apache Gremlin to other cloud services using Service Connector. You might still be able to connect to Azure Cosmos DB for Gremlin in other programming languages without using Service Connector. This page also shows default environment variable names and values you get when you create the service connection.
 
 ## Supported compute services
 
+Service Connector can be used to connect the following compute services to Azure Cosmos DB for Apache Gremlin:
+
 - Azure App Service
 - Azure Functions
 - Azure Container Apps
 - Azure Spring Apps
 
 ## Supported authentication types and client types
 
-Supported authentication and clients for App Service, Azure Functions, Container Apps and Azure Spring Apps:
+The table below shows which combinations of client types and authentication methods are supported for connecting your compute service to Azure Cosmos DB for Apache Gremlin using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported. 
 
 | Client type | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
 |-------------|----------------------------------|--------------------------------|----------------------------|-------------------|
@@ -33,7 +36,7 @@ Supported authentication and clients for App Service, Azure Functions, Container
 | Go          | Yes                              | Yes                            | Yes                        | Yes               |
 | None        | Yes                              | Yes                            | Yes                        | Yes               |
 
----
+This table indicates that all combinations of client types and authentication methods in the table are supported. All client types can use any of the authentication methods to connect to Azure Cosmos DB for Apache Gremlin using Service Connector.
 
 ## Default environment variable names or application properties and sample code
 

articles/service-connector/how-to-integrate-cosmos-sql.md

@@ -1,27 +1,30 @@
 ---
 title: Integrate the Azure Cosmos DB for NoSQL with Service Connector
-description: Integrate the Azure Cosmos DB SQL into your application with Service Connector
+description: Integrate the Azure Cosmos DB for NoSQL into your application with Service Connector
 author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: how-to
-ms.date: 12/04/2023
+ms.date: 02/02/2024
 ms.custom: event-tier1-build-2022, ignite-2022
+
 ---
 # Integrate the Azure Cosmos DB for NoSQL with Service Connector
 
 This page shows supported authentication methods and clients, and shows sample code you can use to connect Azure Cosmos DB for NoSQL to other cloud services using Service Connector. You might still be able to connect to Azure Cosmos DB for NoSQL in other programming languages without using Service Connector. This page also shows default environment variable names and values (or Spring Boot configuration) you get when you create the service connection. 
 
 ## Supported compute services
 
+Service Connector can be used to connect the following compute services to Azure Cosmos DB for NoSQL:
+
 - Azure App Service
 - Azure Functions
 - Azure Container Apps
 - Azure Spring Apps
 
 ## Supported authentication types and client types
 
-Supported authentication and clients for App Service, Azure Functions, Container Apps and Azure Spring Apps:
+The table below shows which combinations of client types and authentication methods are supported for connecting your compute service to Azure Cosmos DB for NoSQL using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
 
 | Client type        | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
 |--------------------|----------------------------------|--------------------------------|----------------------------|-------------------|
@@ -33,6 +36,7 @@ Supported authentication and clients for App Service, Azure Functions, Container
 | Go                 | Yes                              | Yes                            | Yes                        | Yes               |
 | None               | Yes                              | Yes                            | Yes                        | Yes               |
 
+This table indicates that all combinations of client types and authentication methods in the table are supported. All client types can use any of the authentication methods to connect to Azure Cosmos DB for NoSQL using Service Connector.
 
 ## Default environment variable names or application properties and Sample code
 

articles/service-connector/how-to-integrate-cosmos-table.md

@@ -5,23 +5,26 @@ author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: how-to
-ms.date: 12/04/2023
+ms.date: 02/02/2024
 ms.custom: event-tier1-build-2022, ignite-2022
+
 ---
 # Integrate the Azure Cosmos DB for Table with Service Connector
 
 This page shows supported authentication methods and clients, and shows sample code you can use to connect the Azure Cosmos DB for Table to other cloud services using Service Connector. You might still be able to connect to the Azure Cosmos DB for Table in other programming languages without using Service Connector. This page also shows default environment variable names and values you get when you create the service connection. 
 
 ## Supported compute services
 
+Service Connector can be used to connect the following compute services to Azure Cosmos DB for Table:
+
 - Azure App Service
 - Azure Functions
 - Azure Container Apps
 - Azure Spring Apps
 
 ## Supported authentication types and client types
 
-Supported authentication and clients for App Service, Azure Functions, Container Apps and Azure Spring Apps:
+The table below shows which combinations of client types and authentication methods are supported for connecting your compute service to Azure Cosmos DB for Table using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
 
 | Client type | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
 |-------------|----------------------------------|--------------------------------|----------------------------|-------------------|
@@ -32,7 +35,7 @@ Supported authentication and clients for App Service, Azure Functions, Container
 | Go          | Yes                              | Yes                            | Yes                        | Yes               |
 | None        | Yes                              | Yes                            | Yes                        | Yes               |
 
----
+This table indicates that all combinations of client types and authentication methods in the table are supported. All client types can use any of the authentication methods to connect to Azure Cosmos DB for Table using Service Connector.
 
 ## Default environment variable names or application properties and sample code