Merge pull request #246770 from SnehaAgrawal-MSFT/patch-71

(AzureCXP) fixes MicrosoftDocs/azure-docs/issues/112822

Author: prmerger-automator[bot]

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

@@ -544,8 +544,12 @@ To locally run webhook-based triggers and actions in Visual Studio Code, you nee
    > [!NOTE]
    >
    > If your project is NuGet package-based (.NET), not extension bundle-based (Node.js), 
-   > `"FUNCTIONS_WORKER_RUNTIME"` is set to `"dotnet"`. However, to use **Inline Code Operations**, 
-   > you must have `"FUNCTIONS_WORKER_RUNTIME"` set to `"node"`
+   > `"FUNCTIONS_WORKER_RUNTIME"` is set to `"dotnet"`. To use the **Transform XML** action 
+   > [with XSLT maps that call .NET Framework assemblies](#add-assemblies-to-your-project), 
+   > to [create maps for data transformation](create-maps-data-transformation-visual-studio-code.md), 
+   > or to [create and run .NET code from Standard workflows](create-run-custom-code-functions.md), 
+   > you must set `"FUNCTIONS_WORKER_RUNTIME"` to `"dotnet-isolated"`. To use **Inline Code Operations**, 
+   > you must set`"FUNCTIONS_WORKER_RUNTIME"` to `"node"`.
 
 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.