Include file

Author: ecfan

articles/logic-apps/azure-arc-enabled-logic-apps-create-deploy-workflows.md

@@ -575,13 +575,7 @@ The following example describes a sample Azure Arc-enabled Logic Apps resource d
 }
 ```
 
-> [!NOTE]
-> 
-> Previously, the **FUNCTIONS_WORKER_RUNTIME** setting's default value was **`node`**. 
-> Now, **`dotnet`** is the default value for all new and existing deployed Standard 
-> logic apps, even for apps that had a different value. This change shouldn't affect 
-> your workflow's runtime, and everything should work the same way as before. For more 
-> information, see the [**FUNCTIONS_WORKER_RUNTIME** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
+[!INCLUDE [functions-language-runtime](includes/functions-language-runtime.md)]
 
 <a name="include-app-service-plan"></a>
 

articles/logic-apps/create-single-tenant-workflows-azure-portal.md

@@ -117,25 +117,11 @@ More workflows in your logic app raise the risk of longer load times, which nega
    | **Windows Plan** | Yes | <*plan-name*> | The plan name to use. Either select an existing plan name or provide a name for a new plan. <br><br>This example uses the name **My-App-Service-Plan**. <br><br>**Note**: Don't use a Linux-based App Service plan. Only the Windows-based App Service plan is supported. |
    | **Pricing plan** | Yes | <*pricing-tier*> | The [pricing tier](../app-service/overview-hosting-plans.md) to use for your logic app and workflows. Your selection affects the pricing, compute, memory, and storage that your logic app and workflows use. <br><br>For more information, review [Hosting plans and pricing tiers](logic-apps-pricing.md#standard-pricing). |
 
-   > [!NOTE]
-   >
-   > If you select an Azure region that supports availability zone redundancy, the **Zone redundancy** 
-   > section is enabled. This section offers the choice to enable availability zone redundancy 
-   > for your logic app. However, currently supported Azure regions don't include **West US**, 
-   > so you can ignore this section for this example. For more information, see 
-   > [Protect logic apps from region failures with zone redundancy and availability zones](set-up-zone-redundancy-availability-zones.md).
-
    When you finish, your settings look similar to the following example:
 
    :::image type="content" source="media/create-single-tenant-workflows-azure-portal/create-logic-app-basics.png" alt-text="Screenshot shows Azure portal and page named Create Logic App Workflow Service Plan." lightbox="media/create-single-tenant-workflows-azure-portal/create-logic-app-basics.png":::
 
-   > [!NOTE]
-   > 
-   > By default, the language worker runtime value for your Standard logic app is **`dotnet`**. 
-   > Previously, **`node`** was the default value. However, **`dotnet`** is now the default value 
-   > for all new and existing deployed Standard logic apps, even for apps that had a different value. 
-   > This change shouldn't affect your workflow's runtime, and everything should work the same way 
-   > as before. For more information, see the [**FUNCTIONS_WORKER_RUNTIME** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
+   [!INCLUDE [functions-language-runtime](includes/functions-language-runtime.md)]
 
 1. When you finish, select **Next: Storage**.
 

articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md

@@ -633,13 +633,7 @@ To locally run webhook-based triggers and actions in Visual Studio Code, you nee
    }
    ```
 
-   > [!NOTE]
-   > 
-   > Previously, the **FUNCTIONS_WORKER_RUNTIME** setting's default value was **`node`**. 
-   > Now, **`dotnet`** is the default value for all new and existing deployed Standard 
-   > logic apps, even for apps that had a different value. This change shouldn't affect 
-   > your workflow's runtime, and everything should work the same way as before. For more 
-   > information, see the [**FUNCTIONS_WORKER_RUNTIME** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
+   [!INCLUDE [functions-language-runtime](./includes/functions-language-runtime.md)]
 
 The first time when you start a local debugging session or run the workflow without debugging, the Azure Logic Apps runtime registers the workflow with the service endpoint and subscribes to that endpoint for notifying the webhook operations. The next time that your workflow runs, the runtime won't register or resubscribe because the subscription registration already exists in local storage.
 

articles/logic-apps/includes/functions-language-runtime

@@ -0,0 +1,15 @@
+---
+ms.service: azure-logic-apps
+ms.author: estfan
+author: ecfan
+ms.date: 08/16/2024
+ms.topic: include
+---
+
+> [!NOTE]
+> 
+> Previously, the **FUNCTIONS_WORKER_RUNTIME** setting's default value was **`node`**. 
+> Now, **`dotnet`** is the default value for all new and existing deployed Standard 
+> logic apps, even for apps that had a different value. This change shouldn't affect 
+> your workflow's runtime, and everything should work the same way as before. For more 
+> information, see the [**FUNCTIONS_WORKER_RUNTIME** app setting](../edit-app-settings-host-settings.md#reference-local-settings-json).