You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/add-run-powershell-scripts.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.date: 05/23/2025
9
9
# Customer intent: As a logic app workflow developer, I want to write and run PowerShell code so that I can perform custom integration tasks in Standard workflows for Azure Logic Apps.
10
10
---
11
11
12
-
# Add and run PowerShell script code in Standard workflows for Azure Logic Apps (Preview)
12
+
# Add and run PowerShell scripts in Standard workflows for Azure Logic Apps (Preview)
@@ -47,7 +47,7 @@ This guide shows how to add the action in your workflow and add the PowerShell c
47
47
48
48
The *.ps1* file format lets you write less "boilerplate" and focus just on writing PowerShell code. If you rename the action, the file is also renamed, but not vice versa. If you directly rename the file, the renamed version overwrites the previous version. If the action name and file names don't match, the action can't find the file and tries to create a new empty file.
49
49
50
-
- The script is local to the workflow. To use the same script in other workflows, [view the script file in the **KuduPlus** console](#view-script-file), and then copy the script to reuse in other workflows.
50
+
- The script is local to the workflow. To use the same script in other workflows, [view the script file in the **Kudu** console](#view-script-file), and then copy the script to reuse in other workflows.
51
51
52
52
## Limitations
53
53
@@ -242,7 +242,7 @@ To use the managed identity from inside the **Execute PowerShell Code** action,
242
242
243
243
1. On the logic app resource menu, under **Development Tools**, select **Advanced Tools**.
244
244
245
-
1. On the **Advanced Tools** page, select **Go**, which opens the **Kudu Plus** console.
245
+
1. On the **Advanced Tools** page, select **Go**, which opens the **Kudu** console.
246
246
247
247
1. Open the **Debug console** menu, and select **CMD**.
248
248
@@ -287,7 +287,7 @@ To find publicly available modules, visit the [PowerShell gallery](https://www.p
287
287
288
288
1. On the **Advanced Tools** page, select **Go**.
289
289
290
-
1. On the **Kudu Plus** toolbar, from the **Debug console** menu, select **CMD**.
290
+
1. On the **Kudu** toolbar, from the **Debug console** menu, select **CMD**.
291
291
292
292
1. Browse to your logic app's root level at **C:\home\site\wwwroot** by using the directory structure or the command line.
293
293
@@ -324,7 +324,7 @@ You can generate your own private PowerShell modules. To create your first Power
324
324
325
325
1. On the **Advanced Tools** page, select **Go**.
326
326
327
-
1. On the **Kudu Plus** toolbar, from the **Debug console** menu, select **CMD**.
327
+
1. On the **Kudu** toolbar, from the **Debug console** menu, select **CMD**.
328
328
329
329
1. Browse to your logic app's root level at **C:\home\site\wwwroot** by using the directory structure or the command line.
Copy file name to clipboardExpand all lines: articles/logic-apps/logic-apps-enterprise-integration-liquid-transform.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,9 +132,9 @@ After you create your Liquid template, you now have to upload the template based
132
132
133
133
| Property | Value | Description |
134
134
|----------|-------|-------------|
135
-
|**Name**|`JsonToJsonTemplate`| The name for your map, which is "JsonToJsonTemplate" in this example |
135
+
|**Name**|`JsonToJsonTemplate`| The name for your map, which is *JsonToJsonTemplate* in this example |
136
136
|**Map type**|**Liquid**| The type for your map. For JSON to JSON transformation, you must select **Liquid**. |
137
-
|**Map**|`SimpleJsonToJsonTemplate.liquid`| An existing Liquid template or map file to use for transformation, which is "SimpleJsonToJsonTemplate.liquid" in this example. To find this file, you can use the file picker. For map size limits, see [Limits and configuration](../logic-apps/logic-apps-limits-and-config.md#artifact-capacity-limits). |
137
+
|**Map**|`SimpleJsonToJsonTemplate.liquid`| An existing Liquid template or map file to use for transformation, which is *SimpleJsonToJsonTemplate.liquid* in this example. To find this file, you can use the file picker. For map size limits, see [Limits and configuration](../logic-apps/logic-apps-limits-and-config.md#artifact-capacity-limits). |
138
138
139
139
:::image type="content" source="media/logic-apps-enterprise-integration-liquid-transform/add-liquid-template.png" alt-text="Screenshot showing Add Map pane with new template uploaded.":::
140
140
@@ -254,7 +254,7 @@ The following steps show how to add a Liquid transformation action for Consumpti
254
254
255
255
To trigger your workflow, follow these steps:
256
256
257
-
1. In the Request trigger, find the **HTTP POST URL** property, and copy the URL.
257
+
1. In the Request trigger, find the **HTTP URL** property, and copy the URL.
258
258
259
259
1. Open your HTTP request tool and use its instructions to send an HTTP request to the copied URL, including the method that the **Request** trigger expects.
0 commit comments