Updates per feedback

Author: ecfan

articles/logic-apps/create-standard-workflows-hybrid-deployment.md

@@ -147,7 +147,7 @@ If you want to deploy with SMB file share, confirm that the following conditions
 
 #### Deploy your logic app
 
-After you finish building your workflow, you can deploy your logic app to your Azure Container Apps connected environment.
+After you finish building your workflow, you can deploy your logic app to your on-premises Azure Container Apps connected environment.
 
 ##### Zip deployment
 
@@ -228,7 +228,7 @@ For more information, see the following resources:
 
 You can set up enhanced telemetry collection in Application Insights for your Standard logic app and then view the collected data after your workflow finishes a run. This capability gives you a simpler experience to get insights about your workflows and more control over filtering events at the data source, which helps you reduce storage costs. These improvements focus on real-time performance metrics that provide insights into your system's health and behavior.
 
-For partially connected and on-premises scenarios, you can set up your Standard logic app to emit telemetry in [OpenTelemetry format](https://opentelemetry.io/). By default, this telemetry data is sent to Application Insights. For more information, see [Enable enhanced telemetry in Application Insights for Standard workflows in Azure Logic Apps](enable-enhanced-telemetry-standard-workflows.md).
+For partially connected and on-premises scenarios, you can set up your Standard logic app to emit telemetry based on the [OpenTelemetry-supported](https://opentelemetry.io/) app settings that you define for the specific environment. By default, this telemetry data is sent to Application Insights. For more information, see [Enable enhanced telemetry in Application Insights for Standard workflows in Azure Logic Apps](enable-enhanced-telemetry-standard-workflows.md).
 
 <a name="change-vcpu-memory"></a>
 
@@ -384,6 +384,18 @@ You can store the client ID and client secret values in your logic app resource
 
 ## Known issues and troubleshooting
 
+The following section describes currently known issues and guidance for troubleshooting common problems.
+
+### General environment setup or portal deployment problems
+
+To help you diagnose and debug problems with your environment configuration or portal deployment failures, you can try running the **troubleshoot.ps1** PowerShell script provided for the hybrid deployment option.
+
+1. Go to the [Azure Logic Apps GitHub repository: **scripts/hybrid** folder](https://github.com/Azure/logicapps/blob/master/scripts/hybrid).
+
+1. Copy the **troubleshoot.ps1** file to a folder in the same on-premises location as your logic app deployment.
+
+1. Run the script using PowerShell.
+
 ### Arc-enabled Kubernetes clusters
 
 In rare scenarios, you might notice a high memory footprint in your cluster. To prevent this issue, either scale out or add autoscale for node pools.

articles/logic-apps/enable-enhanced-telemetry-standard-workflows.md

@@ -119,17 +119,17 @@ For partially connected and on-premises scenarios, you can configure your Standa
 
 To set up OpenTelemetry capability in the Azure portal, follow the steps, based on hosting option for your Standard logic workflow.
 
-##### Workflow Service Plan or App Service Environment V3
+#### Workflow Service Plan or App Service Environment V3
 
-Follow these steps to update the **host.json** file in the root directory for your logic app resource:
+For a Standard logic app that uses the hosting option for **Workflow Service Plan** or **App Service Environment V3**, follow these steps to update the **host.json** file in the root directory for your logic app resource:
 
 1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
 
 1. On the resource navigation menu, under **Development Tools**, select **Advanced Tools** > **Go**.
 
 1. In the **Kudu+** console, from the **Debug console** menu, select **CMD**. Go to **site** > **wwwroot**.
 
-1. Edit the **host.json** file. At the root level, add the following **telemetryMode** setting with the **OpenTelemetry** value, and save your changes, for example:
+1. Edit the **host.json** file. At the root level, add the following **telemetryMode** setting with the **OpenTelemetry** value, for example:
 
    ```json
    {
@@ -157,45 +157,47 @@ Follow these steps to update the **host.json** file in the root directory for yo
 
 1. If your OpenTelemetry endpoint requires other OpenTelemetry-related settings, include these settings in the app settings too.
 
-##### Hybrid deployment
+#### Hybrid deployment
 
-Follow these steps to update the **host.json** file in the root directory for an SMB file share in an Azure storage account:
+For a Standard logic app that uses the hosting option for **Hybrid**, follow the corresponding steps to set up OpenTelemetry based on the deployment option that you chose.
 
-1. In the [Azure portal](https://portal.azure.com), open the Azure storage account with your SMB file share.
+##### Zip deployment
 
-1. On the storage account menu, under **Data storage**, select **File shares**, and then select your SMB file share.
+##### On-premises SMB file share
 
-1, 
-open the host.json in the root directory of SMB file share path configured in your logic app
-In the host.json file, at the root level, add the following telemetryMode setting with the OpenTelemetry value, for example:
-JSONCopy
-{
-    "version": "2.0",
-    "extensionBundle": {
-        "id": "Microsoft.Azure.Functions.ExtensionBundle.Workflows",
-        "version": "[1.*, 2.0.0)"
-    },
-    "telemetryMode": "OpenTelemetry"
-}
-When you enable OpenTelemetry in the host.json file, your logic app exports telemetry based on the OpenTelemetry-supported app settings that you define in the environment.
-Add below app settings from portal by navigating to Containers-->Enviornment variables-->edit and deploy
-App setting
-	
-Description
+For a Standard logic app that uses the hosting option for **Hybrid** and an on-premises SMB file share, follow these steps to update the **host.json** file:
+
+1. On your on-premises SMB file share, in the root directory, find and open the **host.json** file.
+
+1. In the **host.json** file, at the root level, add the following **telemetryMode** setting with the **OpenTelemetry** value, and save your changes, for example:
+
+   ```json
+   {
+       "version": "2.0",
+       "extensionBundle": {
+           "id": "Microsoft.Azure.Functions.ExtensionBundle.Workflows",
+           "version": "[1.*, 2.0.0)"
+       },
+       "telemetryMode": "OpenTelemetry"
+   }
+   ```
+
+1. Save your edits.
 
+1. In the [Azure portal](https://portal.azure.com), find and open your Standard logic app resource.
+
+1. On the resource navigation menu, under **Settings** > **Environment variables**, select **App settings**.
+
+1. Add the following app settings:
 
    | App setting | Description |
    |-------------|-------------|
    | **OTEL_EXPORTER_OTLP_ENDPOINT** | The online transaction processing (OTLP) exporter endpoint URL for where to send the telemetry data. |
    | **OTEL_EXPORTER_OTLP_HEADERS** (optional) | A list of headers to apply to all outgoing data. Commonly used to pass authentication keys or tokens to your observability backend. |
 
-1. If your OpenTelemetry endpoint requires other OpenTelemetry-related settings, include these settings in the app settings too.
-
-For more information, see the following documentation:
-
-- [Edit host and app settings for Standard logic apps](edit-app-settings-host-settings.md)
+1. When you're done, select **Apply**.
 
-- [OTLP Exporter Configuration documentation](https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/)
+1. If your OpenTelemetry endpoint requires other OpenTelemetry-related settings, include these settings in the app settings too.
 
 ### [Visual Studio Code](#tab/visual-studio-code)
 
@@ -216,8 +218,6 @@ To set up OpenTelemetry capability in Visual Studio Code, follow these steps:
    }
    ```
 
-   When you enable OpenTelemetry in the **host.json** file, your logic app exports telemetry based on the OpenTelemetry-supported app settings that you define in the environment.
-
 1. Open the **local.settings.json** file at the project root level, add the following app settings:
 
    | App setting | Description |
@@ -227,14 +227,14 @@ To set up OpenTelemetry capability in Visual Studio Code, follow these steps:
 
 1. If your OpenTelemetry endpoint requires other OpenTelemetry-related settings, include these settings in the app settings too.
 
+---
+
 For more information, see the following documentation:
 
 - [Edit host and app settings for Standard logic apps](edit-app-settings-host-settings.md)
 
 - [OTLP Exporter Configuration documentation](https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/)
 
----
-
 <a name="open-application-insights"></a>
 
 ## Open Application Insights