Merge pull request #288964 from maud-lv/ml-scfreshness

ttorble · web-flow · commit 046a980e8618 · 2024-10-23T10:18:38.000+01:00
Review service connector docs
diff --git a/articles/service-connector/concept-service-connector-internals.md b/articles/service-connector/concept-service-connector-internals.md
@@ -6,7 +6,7 @@ ms.author: malev
 ms.service: service-connector
 ms.custom: engagement-fy23
 ms.topic: conceptual
-ms.date: 01/17/2023
+ms.date: 10/22/2024
 ---
 # Service Connector internals
 
diff --git a/articles/service-connector/known-limitations.md b/articles/service-connector/known-limitations.md
@@ -1,10 +1,10 @@
 ---
 title: Service Connector limitations
-description: Learn about current limitations in Service Connector.
+description: Learn about current limitations in Service Connector used to connect apps and Cloud services in Azure.
 titleSuffix: Service Connector
 ms.service: service-connector
 ms.topic: troubleshooting
-ms.date: 03/02/2023
+ms.date: 10/22/2024
 ms.author: malev
 author: maud-lv
 ---
@@ -14,9 +14,9 @@ In this article, learn about Service Connector's existing limitations and how to
 
 ## Limitations to Infrastructure as Code (IaC)
 
-Service Connector has been designed to bring the benefits of easy, secure, and consistent backing service connections to as many Azure services as possible. To do so, Service Connector has been developed as an extension resource provider.
+Service Connector is designed to bring the benefits of easy, secure, and consistent backing service connections to as many Azure services as possible. To do so, Service Connector is developed as an extension resource provider.
 
-Unfortunately, there are some limitations with IaC support as Service Connector modifies infrastructure on users' behalf. In this scenario, users would begin by using Azure Resource Manager (ARM), Bicep, Terraform, or other IaC templates to create resources. Afterwards, they would use Service Connector to set up resource connections. During this step, Service Connector modifies resource configurations on behalf of the user. If the user reruns their IaC template at a later time, modifications made by Service Connector would disappear as they were not reflected in the original IaC templates. An example of this behavior is Azure Container Apps deployed with ARM templates usually have Managed Identity (MI) disabled by default, Service Connector enables MI when setting up connections on users' behalf. If users trigger the same ARM templates without updating MI settings, the redeployed container apps will have MI disabled again.
+IaC support comes with some limitations, as Service Connector modifies the infrastructure on the users' behalf. In this scenario, users begin by using Azure Resource Manager (ARM), Bicep, Terraform, or other IaC templates to create resources. Afterwards, they use Service Connector to set up resource connections. During this step, Service Connector modifies resource configurations on behalf of the user. If the user reruns their IaC template at a later time, modifications made by Service Connector disappear as they weren't reflected in the original IaC templates. As an example of this behavior, Azure Container Apps resources deployed with ARM templates usually have the managed identity authentication disabled by default. Service Connector enables the managed identity when setting up connections on the users' behalf. If users trigger the same ARM templates without updating the managed identity settings, the managed identity will be disabled once again in the redeployed Azure Container Apps resource.
 
 If you run into any issues when using Service Connector, [file an issue with us](https://github.com/Azure/ServiceConnector/issues/new).
 
@@ -25,9 +25,9 @@ If you run into any issues when using Service Connector, [file an issue with us]
 We suggest the following solutions:
 
 - Reference [how to build connections with IaC tools](how-to-build-connections-with-iac-tools.md) to build your infrastructure or translate your existing infrastructure to IaC templates.
-- If your CI/CD pipelines contain templates of source compute or backing services, suggested flow is: reapplying the templates, adding sanity check or smoke tests to make sure the application is up and running, then allowing live traffic to the application. The flow adds a verification step before allowing live traffic.
+- If your CI/CD pipelines contain templates of source compute or backing services, we suggested reapplying the templates, adding a sanity check or smoke tests to make sure the application is up and running, then allowing live traffic to the application. The flow adds a verification step before allowing live traffic.
 - When automating Azure Container App code deployments with Service Connector, we recommend the use of [multiple revision mode](../container-apps/revisions.md#revision-modes) to avoid routing traffic to a temporarily nonfunctional app before Service connector can reapply connections.
-- The order in which automation operations are performed matters greatly. Ensure your connection endpoints are there before the connection itself is created. Ideally, create the backing service, then the compute service, and then the connection between the two. This way, Service Connector can configure both the compute service and the backing service appropriately.
+- The order in which automation operations are performed matters. Ensure your connection endpoints are there before the connection itself is created. Ideally, create the backing service, then the compute service, and then the connection between the two. This way, Service Connector can configure both the compute service and the backing service appropriately.
 
 ## Next steps
 
diff --git a/articles/service-connector/quickstart-portal-app-service-connection.md b/articles/service-connector/quickstart-portal-app-service-connection.md
@@ -1,11 +1,11 @@
 ---
-title: Quickstart - Create a service connection in App Service from the Azure portal
+title: 'Quickstart: Create a service connection in App Service'
 description: Quickstart showing how to create a service connection in App Service from the Azure portal
 author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: quickstart
-ms.date: 10/05/2023
+ms.date: 10/22/2024
 #Customer intent: As an app developer, I want to connect several services together so that I can ensure I have the right connectivity to access my Azure resources.
 ---
 
@@ -45,7 +45,7 @@ Sign in to the Azure portal at [https://portal.azure.com/](https://portal.azure.
 
 1. Select **Next: Authentication** to choose an authentication method.
 
-    ### [System-assigned managed identity](#tab/SMI)
+    ### [System-assigned managed identity (recommended)](#tab/SMI)
 
     System-assigned managed identity is the recommended authentication option. Select **System-assigned managed identity** to connect through an identity that's generated in Microsoft Entra ID and tied to the lifecycle of the service instance.
 
diff --git a/articles/service-connector/quickstart-portal-container-apps.md b/articles/service-connector/quickstart-portal-container-apps.md
@@ -1,11 +1,11 @@
 ---
-title: Quickstart - Create a service connection in Container Apps from the Azure portal
+title: 'Quickstart: Create a service connection in Container Apps'
 description: This quickstart shows how to create a service connection in Azure Container Apps from the Azure portal
 author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: quickstart
-ms.date: 10/31/2023
+ms.date: 10/22/2024
 #Customer intent: As an app developer, I want to connect Azure Container Apps to a storage account in the Azure portal using Service Connector.
 ---
 
@@ -57,11 +57,11 @@ Use Service Connector to create a new service connection in Container Apps.
 
 1. Select **Next: Authentication** to choose an authentication method: system-assigned managed identity (SMI), user-assigned managed identity (UMI), connection string, or service principal.
 
-    ### [SMI](#tab/SMI)
+    ### [System-assigned managed identity (recommended)](#tab/SMI)
 
     System-assigned managed identity is the recommended authentication option. Select **System-assigned managed identity** to connect through an identity that's automatically generated in Microsoft Entra ID and tied to the lifecycle of the service instance.
 
-    ### [UMI](#tab/UMI)
+    ### [User-assigned managed identity](#tab/UMI)
 
     Select **User-assigned managed identity** to authenticate through a standalone identity assigned to one or more instances of an Azure service. Select a subscription that contains a user-assigned managed identity, and select the identity.
 
diff --git a/articles/service-connector/quickstart-portal-functions-connection.md b/articles/service-connector/quickstart-portal-functions-connection.md
@@ -5,7 +5,7 @@ author: houk-ms
 ms.author: honc
 ms.service: service-connector
 ms.topic: quickstart
-ms.date: 10/25/2023
+ms.date: 10/22/2024
 ---
 # Quickstart: Create a service connection in a function app from the Azure portal
 
diff --git a/articles/service-connector/tutorial-passwordless.md b/articles/service-connector/tutorial-passwordless.md
@@ -6,7 +6,7 @@ author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: tutorial
-ms.date: 09/28/2023
+ms.date: 10/22/2024
 ms.devlang: azurecli
 ms.custom: passwordless-dotnet, passwordless-java, devx-track-azurecli
 zone_pivot_group_filename: service-connector/zone-pivot-groups.json
@@ -66,7 +66,7 @@ Then you can check the log or call the application to see if it can connect to t
 
 #### Permission
 
-If you encounter any permission-related errors, confirm the Azure CLI signed-in user with the command `az account show`. Make sure you log in with the correct account. Next, confirm that you have the following permissions that might be required to create a passwordless connection with Service Connector.
+If you encounter any permission-related errors, confirm the Azure CLI signed-in user with the command `az account show`. Make sure you sign in with the correct account. Next, confirm that you have the following permissions that might be required to create a passwordless connection with Service Connector.
 
 ::: zone pivot="postgresql"
 
diff --git a/articles/service-connector/tutorial-portal-key-vault.md b/articles/service-connector/tutorial-portal-key-vault.md
@@ -1,16 +1,17 @@
 ---
-title: Tutorial - Connect Azure services and store secrets in Key Vault
-description: Tutorial showing how to store your web app's secrets in Azure Key Vault using Service Connector
+title: 'Tutorial: Connect Azure services and store secrets in Key Vault'
+description: Tutorial showing how to store your web application's secrets in Azure Key Vault using Service Connector.
 author: maud-lv
 ms.author: malev
 ms.service: service-connector
 ms.topic: tutorial
-ms.date: 10/31/2023
+ms.date: 10/22/2024
+#customer intent: As a web developer, I want store my app's secrets in Azure Key Vault so they can be managed and protected by Azure's security features.
 ---
 
 # Quickstart: Connect Azure services and store secrets in Azure Key Vault
 
-Azure Key Vault is a cloud service that provides a secure store for secrets. You can securely store keys, passwords, certificates, and other secrets. When you create a service connection, you can securely store access keys and secrets into connected Key Vault. In this tutorial, you'll complete the following tasks using the Azure portal. Both methods are explained in the following procedures.
+Azure Key Vault is a cloud service that provides a secure store for secrets. You can securely store keys, passwords, certificates, and other secrets. When you create a service connection, you can securely store access keys and secrets into connected Key Vault. In this tutorial, you complete the following tasks using the Azure portal. Both methods are explained in the following procedures.
 
 > [!div class="checklist"]
 > * Create a service connection to Azure Key Vault in Azure App Service
@@ -25,8 +26,8 @@ To create a service connection and store secrets in Key Vault with Service Conne
 * An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free).
 * An app hosted on App Service. If you don't have one yet, [create and deploy an app to App Service](../app-service/quickstart-dotnetcore.md)
 * An Azure Key Vault. If you don't have one, [create an Azure Key Vault](/azure/key-vault/general/quick-create-portal)
-* Another target service instance supported by Service Connector. In this tutorial, you'll use [Azure Blob Storage](../storage/blobs/storage-quickstart-blobs-portal.md)
-* Read and write access to the App Service, Key Vault and the target service.
+* Another target service instance supported by Service Connector. In this tutorial, you use [Azure Blob Storage](../storage/blobs/storage-quickstart-blobs-portal.md)
+* Read and write access to the App Service, Key Vault, and the target service.
 
 ## Create a Key Vault connection in App Service
 
@@ -52,7 +53,7 @@ To store your connection access keys and secrets into a key vault, start by conn
 
 ## Create a Blob Storage connection in App Service and store access keys into Key Vault
 
-Now you can create a service connection to another target service and directly store access keys into a connected Key Vault when using a connection string/access key or a Service Principal for authentication. We'll use Blob Storage as an example below. Follow the same process for other target services.
+Now you can create a service connection to another target service and directly store access keys into a connected Key Vault when using a connection string/access key or a service principal for authentication. We use Blob Storage as an example below. Follow the same process for other target services.
 
 1. In the Azure portal, type **App Service** in the search menu and select the name of the App Service you want to use from the list.
 1. Select **Service Connector** from the left table of contents. Then select **Create**.
@@ -83,11 +84,11 @@ Now you can create a service connection to another target service and directly s
 
     ### [Service principal](#tab/serviceprincipal)
 
-    Select **Next: Authentication** to select the authentication type and select **Service Principal** to use Service Principal to connect your storage account.
+    Select **Next: Authentication** to select the authentication type and select **Service Principal** to use a service principal to connect your storage account.
 
     | Setting      | Suggested value  | Description                                        |
     | ------------ |  ------- | -------------------------------------------------- |
-    | **Service Principal object ID or name** | Choose the Service Principal you want to use to connect to Blob Storage from the list | The Service Principal in your subscription that is used to connect to target service. |
+    | **Service Principal object ID or name** | Choose the service principal you want to use to connect to Blob Storage from the list | The service principal in your subscription that is used to connect to target service. |
     | **Store Secret to Key Vault** | Check | This option lets Service Connector store the service principal ID and secret into Key Vault. |
     | **Key Vault connection** | One of your key vault connections | Select the Key Vault in which you want to store your service principal ID and secret. |
 
@@ -103,7 +104,7 @@ Now you can create a service connection to another target service and directly s
 
 1. Expand the Blob Storage connection, select **Hidden value. Click to show value**. You can see that the value is a Key Vault reference.
 
-1. Select the **Key Vault** in the Service Type column of your Key Vault connection. You will be redirected to the Key Vault portal page.
+1. Select the **Key Vault** in the Service Type column of your Key Vault connection. You'll be redirected to the Key Vault portal page.
 
 1. Select **Secrets** in the Key Vault left ToC, and select the blob storage secret name.
 
diff --git a/articles/service-connector/tutorial-python-functions-storage-blob-as-input.md b/articles/service-connector/tutorial-python-functions-storage-blob-as-input.md
@@ -1,16 +1,17 @@
 ---
 title: 'Tutorial: Python function with Azure Blob Storage as input'
-description: Learn how you can connect a Python function to a storage blob as input using Service Connector
+description: Learn how you can connect a Python function to a storage blob as input using Service Connector in Azure.
 author: houk-ms
 ms.author: honc
 ms.service: service-connector
 ms.custom: devx-track-python
 ms.topic: tutorial
-ms.date: 10/25/2023
+ms.date: 10/22/2024
+#customer intent: As a developer, I want to configure a Python function with Storage Blob as input function binding so that I can process and manage large volumes of data stored in Azure Blob Storage. 
 ---
 # Tutorial: Python function with Azure Blob Storage as input
 
-In this tutorial, you learn how to configure a Python function with Storage Blob as input by completing the following tasks:
+In this tutorial, you learn how to configure a Python function with Azure Blob storage as input by completing the following tasks:
 
 > [!div class="checklist"]
 > * Use Visual Studio Code to create a Python function project.
diff --git a/articles/service-connector/tutorial-python-functions-storage-queue-as-trigger.md b/articles/service-connector/tutorial-python-functions-storage-queue-as-trigger.md
