Merge pull request #303190 from TimShererWithAquent/us448924-06

Freshness Edit: Service Connectors

Author: prmerger-automator[bot]

articles/service-connector/how-to-integrate-key-vault.md

@@ -1,19 +1,20 @@
 ---
 title: Integrate Azure Key Vault with Service Connector
-description: Integrate Azure Key Vault into your application with Service Connector
+description: Use these code samples to integrate Azure Key Vault into your application with Service Connector.
 author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: how-to
-ms.date: 02/02/2024
+ms.date: 07/24/2025
+#customer intent: As a cloud developer, I want to connect my cloud services to Azure Key Vault by using Service Connector.
 ---
 
 # Integrate Azure Key Vault with Service Connector
 
 > [!NOTE]
 > When you use Service Connector to connect your Key Vault or manage Key Vault connections, Service Connector uses your token to perform the corresponding operations.
 
-This page shows supported authentication methods and clients, and shows sample code you can use to connect Azure Key Vault to other cloud services using Service Connector. You might still be able to connect to Azure Key Vault 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. 
+This page shows supported authentication methods and clients. It provides sample code you can use to connect Azure Key Vault to other cloud services using Service Connector. You might be able to connect to Azure Key Vault 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
 
@@ -27,7 +28,7 @@ Service Connector can be used to connect the following compute services to Azure
 
 ## Supported authentication types and client types
 
-The table below shows which combinations of client types and authentication methods are supported for connecting your compute service to Azure Key Vault using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
+The following table shows which combinations of client types and authentication methods are supported for connecting your compute service to Azure Key Vault using Service Connector. A "Yes" indicates that the combination is supported, while a "No" indicates that it isn't supported.
 
 | Client type        | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
 |--------------------|----------------------------------|--------------------------------|----------------------------|-------------------|
@@ -38,15 +39,15 @@ The table below shows which combinations of client types and authentication meth
 | Python             | Yes                              | Yes                            | No                         | Yes               |
 | None               | Yes                              | Yes                            | No                         | Yes               |
 
-This table indicates that all combinations of client types and authentication methods in the table are supported, except for the Secret / connection string method, which is not supported for any of the client types. All client types can use any of the other authentication methods to connect to Azure Key Vault using Service Connector.
+This table indicates that all combinations of client types and authentication methods in the table are supported, except for **Secret / connection string**. That method isn't supported for any of the client types. All client types can use any of the other authentication methods to connect to Azure Key Vault using Service Connector.
 
 ## Default environment variable names or application properties and sample code
 
-Use the connection details below to connect compute services to Azure Key Vault. For each example below, replace the placeholder texts `<vault-name>`, `<client-ID>`, `<client-secret>`, and `<tenant-id>` with your Key Vault name, client-ID, client secret and tenant ID. For more information about naming conventions, check the [Service Connector internals](concept-service-connector-internals.md#configuration-naming-convention) article.
+Use the following connection details to connect compute services to Azure Key Vault. For each of these examples, replace the placeholder texts `<vault-name>`, `<client-ID>`, `<client-secret>`, and `<tenant-id>` with your Key Vault name, client-ID, client secret, and tenant ID. For more information, see [Configuration naming convention](concept-service-connector-internals.md#configuration-naming-convention).
 
 ### System-assigned managed identity
 
-#### SpringBoot client type
+#### Spring Boot client type
 
 | Default environment variable name | Description                 | Example value                             |
 |-----------------------------------|-----------------------------|-------------------------------------------|
@@ -64,12 +65,12 @@ Use the connection details below to connect compute services to Azure Key Vault.
 
 #### Sample code
 
-Refer to the steps and code below to connect to Azure Key Vault using a system-assigned managed identity.
+To connect to Azure Key Vault using a system-assigned managed identity, refer to the following steps and code.
 [!INCLUDE [code sample for key vault](./includes/code-keyvault-me-id.md)]
 
 ### User-assigned managed identity
 
-#### SpringBoot client type
+#### Spring Boot client type
 
 | Default environment variable name | Description                 | Example value                             |
 |-----------------------------------|-----------------------------|-------------------------------------------|
@@ -90,12 +91,12 @@ Refer to the steps and code below to connect to Azure Key Vault using a system-a
 
 #### Sample code
 
-Refer to the steps and code below to connect to Azure Key Vault using a system-assigned managed identity.
+To connect to Azure Key Vault using a system-assigned managed identity, refer to the following steps and code.
 [!INCLUDE [code sample for key vault](./includes/code-keyvault-me-id.md)]
 
 ### Service principal
 
-#### SpringBoot client type
+#### Spring Boot client type
 
 | Default environment variable name | Description                 | Example value                             |
 |-----------------------------------|-----------------------------|-------------------------------------------|
@@ -121,12 +122,10 @@ Refer to the steps and code below to connect to Azure Key Vault using a system-a
 
 #### Sample code
 
-Refer to the steps and code below to connect to Azure Key Vault using a system-assigned managed identity.
+To connect to Azure Key Vault using a system-assigned managed identity, refer to the following steps and code.
 [!INCLUDE [code sample for key vault](./includes/code-keyvault-me-id.md)]
 
-## Next steps
-
-Follow the tutorials listed below to learn more about Service Connector.
+## Next step
 
 > [!div class="nextstepaction"]
 > [Learn about Service Connector concepts](./concept-service-connector-internals.md)

articles/service-connector/includes/code-keyvault-me-id.md

@@ -1,6 +1,6 @@
 ---
 author: wchigit
-description: managed identity, code sample
+description: Managed identity, code sample
 ms.service: service-connector
 ms.topic: include
 ms.date: 11/02/2023
@@ -10,11 +10,14 @@ ms.author: wchi
 ### [.NET](#tab/dotnet)
 
 1. Install dependencies.
+
     ```bash
     dotnet add package Azure.Identity
     dotnet add package Azure.Security.KeyVault.Secrets
     ```
-1. Authenticate using `Azure.Identity` and get the Azure Key Vault endpoint from the environment variables added by Service Connector. When using the code below, uncomment the part of the code snippet for the authentication type you want to use.
+
+1. Authenticate using `Azure.Identity` and get the Azure Key Vault endpoint from the environment variables added by Service Connector. When using this code, uncomment the part of the code snippet for the authentication type you want to use.
+
     ```csharp
     using Azure.Identity;
     using Azure.Security.KeyVault.Secrets;
@@ -56,6 +59,7 @@ ms.author: wchi
 ### [Java](#tab/java)
 
 1. Add the following dependencies in your *pom.xml* file:
+
     ```xml
     <dependency>
         <groupId>com.azure</groupId>
@@ -67,7 +71,9 @@ ms.author: wchi
         <version>1.1.5</version>
     </dependency>
     ```
-1. Authenticate using `azure-identity` and get the Azure Key Vault endpoint from the environment variables added by Service Connector. When using the code below, uncomment the part of the code snippet for the authentication type you want to use.
+
+1. Authenticate using `azure-identity` and get the Azure Key Vault endpoint from the environment variables added by Service Connector. When using this code, uncomment the part of the code snippet for the authentication type you want to use.
+
     ```java
     // Uncomment the following lines corresponding to the authentication type you want to use.
     // for system-managed identity
@@ -94,15 +100,18 @@ ms.author: wchi
 
 ### [SpringBoot](#tab/springBoot)
 
-Refer to [Tutorial: Connect Azure Spring Apps to Key Vault using managed identities](../../spring-apps/basic-standard/tutorial-managed-identities-key-vault.md?tabs=system-assigned-managed-identity) to set up your Spring application. Two sets of configuration properties are added to Spring Apps by Service Connector, according to Spring Cloud Azure version below 4.0 and above 4.0. For more information, check [Migration Guide for 4.0](https://microsoft.github.io/spring-cloud-azure/current/reference/html/appendix.html#configuration-spring-cloud-azure-starter-keyvault-secrets)
+To set up your Spring application, see [Connect Azure Spring Apps to Key Vault using managed identities](../../spring-apps/basic-standard/tutorial-managed-identities-key-vault.md?tabs=system-assigned-managed-identity). Two sets of configuration properties are added to Spring Apps by Service Connector, according to Spring Cloud Azure version below 4.0 and above 4.0. For more information, see [Migration Guide for 4.0](https://microsoft.github.io/spring-cloud-azure/current/reference/html/appendix.html#configuration-spring-cloud-azure-starter-keyvault-secrets).
 
 ### [Python](#tab/python)
 
 1. Install dependencies.
+
     ```bash
     pip install azure-keyvault-keys azure-identity
     ```
-1. Authenticate using `azure-identity` and get the Azure Key Vault endpoint from the environment variables added by Service Connector. When using the code below, uncomment the part of the code snippet for the authentication type you want to use.
+
+1. Authenticate using `azure-identity` and get the Azure Key Vault endpoint from the environment variables added by Service Connector. When using this code, uncomment the part of the code snippet for the authentication type you want to use.
+
     ```python
     import os
     from azure.identity import ManagedIdentityCredential, ClientSecretCredential
@@ -126,14 +135,17 @@ Refer to [Tutorial: Connect Azure Spring Apps to Key Vault using managed identit
     client = KeyClient(vault_url=VAULT_URL, credential=cred)
     ```
 
-
 ### [NodeJS](#tab/nodejs)
+
 1. Install dependencies.
+
     ```bash
     npm install @azure/identity
     npm install @azure/keyvault-secrets
     ```
-1. Authenticate using `@azure/identity` and get the Azure Key Vault endpoint from the environment variables added by Service Connector. When using the code below, uncomment the part of the code snippet for the authentication type you want to use.
+
+1. Authenticate using `@azure/identity` and get the Azure Key Vault endpoint from the environment variables added by Service Connector. When using this code, uncomment the part of the code snippet for the authentication type you want to use.
+
     ```javascript
     import { DefaultAzureCredential,ClientSecretCredential } from "@azure/identity";
     const { SecretClient } = require("@azure/keyvault-secrets");