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/manage-logic-apps-visual-studio-code.md
+73-56Lines changed: 73 additions & 56 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,11 +75,13 @@ If you aren't already connected to your Azure account, follow these steps to con
75
75
76
76
1. In Visual Studio Code, [connect to your Azure account](#connect-azure-account), if you haven't already.
77
77
78
-
1. On the Visual Studio Code Activity Bar, select the Azure icon to open the **Azure** pane.
78
+
1. On the Activity Bar, select the Azure icon to open the **Azure** pane.
79
79
80
-
1. In the **Logic Apps (Consumption)** section, expand your subscription node.
80
+
1. In the **Logic Apps (Consumption)** section, expand your Azure subscription.
81
81
82
-
You can now view all the deployed Consumption logic apps in the selected subscription.
82
+
You can now view all the deployed Consumption logic apps in the selected subscription, for example:
83
+
84
+
:::image type="content" source="media/manage-logic-apps-visual-studio-code/find-deployed-logic-app-consumption.png" alt-text="Screenshot shows Visual Studio Code with Resources section and deployed Consumption logic app resource.":::
83
85
84
86
1. Find and expand the node for the deployed Consumption logic app that you want.
85
87
@@ -102,11 +104,13 @@ If you aren't already connected to your Azure account, follow these steps to con
102
104
103
105
1. In Visual Studio Code, [connect to your Azure account](#connect-azure-account), if you haven't already.
104
106
105
-
1. On the Visual Studio Code Activity Bar, select the Azure icon to open the **Azure** pane.
107
+
1. On the Activity Bar, select the Azure icon to open the **Azure** pane.
108
+
109
+
1. In the **Resources** section, expand your subscription, and then expand **Logic App**.
106
110
107
-
1. In the **Resources** section, expand your subscription node, and then expand the **Logic App** node.
111
+
You can now view all the deployed Standard logic apps in the selected subscription, for example:
108
112
109
-
You can now view all the deployed Standard logic apps in the selected subscription.
113
+
:::image type="content" source="media/manage-logic-apps-visual-studio-code/find-deployed-logic-app-standard.png" alt-text="Screenshot shows Visual Studio Code with Resources section and deployed Standard logic app resource.":::
110
114
111
115
1. Find and expand the node for the deployed Standard logic app that you want.
112
116
@@ -162,9 +166,9 @@ To edit a deployed Consumption or Standard workflow using the designer, make tho
162
166
163
167
### [Consumption](#tab/consumption)
164
168
165
-
1.On the Visual Studio Code Activity Bar, select the Azure icon to open the **Azure** pane.
169
+
1.In Visual Studio Code, on the Activity Bar, select the Azure icon to open the **Azure** pane.
166
170
167
-
1.Expand the Azure subscription for your Consumption logic app, and find your logic app.
171
+
1.In the **Logic Apps (Consumption)** section, expand your Azure subscription, and find your logic app.
168
172
169
173
1. Open the logic app shortcut menu, and select **Open in Editor**.
170
174
@@ -200,95 +204,108 @@ To edit a deployed Consumption or Standard workflow using the designer, make tho
200
204
201
205
---
202
206
203
-
> [!NOTE]
204
-
>
205
-
> The stop logic app and delete logic app operations affect workflow instances in different ways.
206
-
> For more information, see [Considerations for stopping logic apps](#considerations-stop-logic-apps) and
207
-
> [Considerations for deleting logic apps](#considerations-delete-logic-apps).
207
+
<aname="disable-enable-logic-apps"></a>
208
+
209
+
## Disable or enable a deployed logic app
210
+
211
+
Deployed Consumption and Standard logic apps have different ways to disable and enable their activity. For considerations around how these tasks affect each logic app resource type, see the following documentation:
212
+
213
+
-[Considerations for stopping Consumption logic apps](/azure/logic-apps/manage-logic-apps-with-azure-portal?tabs=consumption#considerations-stop-consumption-logic-apps)
214
+
-[Considerations for stopping Standard logic apps](/azure/logic-apps/manage-logic-apps-with-azure-portal?tabs=standard#considerations-stop-standard-logic-apps)
215
+
-[Considerations for disabling Standard workflows](/azure/logic-apps/manage-logic-apps-with-azure-portal?tabs=standard#considerations-disable-enable-standard-workflows)
216
+
217
+
### [Consumption](#tab/consumption)
218
+
219
+
1. In Visual Studio Code, on the Activity Bar, select the Azure icon to open the **Azure** pane.
220
+
221
+
1. In the **Logic Apps (Consumption)** section, expand your Azure subscription, and find your logic app.
222
+
223
+
1. Open the logic app shortcut menu. Based on the current actvitity state, select **Disable** or **Enable**.
208
224
209
-

225
+
### [Standard](#tab/standard)
210
226
227
+
In Visual Studio Code, you can stop, start, or restart a Standard logic app, which affects all workflow instances. You can also restart a Standard logic app without first stopping its activity. However, to disable and reenable individual workflows, [you must use the Azure portal](/azure/logic-apps/manage-logic-apps-with-azure-portal/stop-start-standard-workflows).
211
228
212
-
<aname="considerations-stop-logic-apps"></a>
229
+
Stopping the resource versus disabling a workflow have different effects, so review the considerations before you continue.
213
230
214
-
### Considerations for stopping logic apps
231
+
1. In Visual Studio Code, on the Activity Bar, select the Azure icon to open the **Azure** pane.
215
232
216
-
Stopping a logic app affects workflow instances in the following ways:
233
+
1. In the **Resources** section, expand your Azure subscription, and find your logic app.
217
234
218
-
* Azure Logic Apps cancels all in-progress and pending runs immediately.
235
+
1. Open the logic app shortcut menu. Based on the current actvitity state, select **Stop** or **Start**. Or, you can select **Restart**.
219
236
220
-
* Azure Logic Apps doesn't create or run new workflow instances.
237
+
---
221
238
222
-
* Triggers won't fire the next time that their conditions are met. However, trigger states remember the points where the logic app was stopped. So, if you restart the logic app, the triggers fire for all unprocessed items since the last run.
239
+
## Post logic app stoppage
223
240
224
-
To stop a trigger from firing on unprocessed items since the last run, clear the trigger state before you restart the logic app:
241
+
After you stop a logic app, workflow triggers won't fire the next time that their conditions are met. However, trigger states remember the points at where you stopped the logic app. When you a restart a logic app, the trigger fires for all unprocessed items since the last workflow run.
225
242
226
-
1. On the Visual Studio Code Activity Bar, select the Azure icon, which opens the **Azure** pane.
243
+
To stop a trigger from firing on unprocessed items since the last workflow run, you must clear the trigger state before you restart a logic app by following these steps:
227
244
228
-
1. In the **Resources** section, expand your subscription, which shows all the deployed logic apps for that subscription.
245
+
### [Consumption](#tab/consumption)
229
246
230
-
1.Expand your logic app, and then expand the **Workflows** node.
247
+
1.In Visual Studio Code, [open your Consumption logic app workflow](#edit-workflow), and edit any part of the workflow trigger.
231
248
232
-
1.Open a workflow, and edit any part of that workflow's trigger.
249
+
1.Save your changes. This step resets your trigger's current state.
233
250
234
-
1.Save your changes. This step resets the trigger's current state.
251
+
1.When you're done, [restart your logic app](/azure/logic-apps/manage-logic-apps-visual-studio-code?tabs=consumption#disable-enable-logic-apps).
235
252
236
-
1. Repeat for each workflow.
253
+
### [Standard](#tab/standard)
237
254
238
-
1.When you're done, restart your logic app.
255
+
1.In Visual Studio Code, [open your Standard logic app workflow](#edit-workflow), and edit any part of the workflow trigger.
239
256
240
-
<aname="considerations-delete-logic-apps"></a>
257
+
1. Save your changes. This step resets the trigger's current state.
241
258
242
-
### Considerations for deleting logic apps
259
+
1. Repeat for each existing workflow.
243
260
244
-
Deleting a logic app affects workflow instances in the following ways:
261
+
1. When you're done, [restart your logic app](/azure/logic-apps/manage-logic-apps-visual-studio-code?tabs=standard#disable-enable-logic-apps).
245
262
246
-
* Azure Logic Apps cancels in-progress and pending runs immediately, but doesn't run cleanup tasks on the storage used by the app.
263
+
---
247
264
248
-
* Azure Logic Apps doesn't create or run new workflow instances.
265
+
<aname="delete-logic-apps"></a>
249
266
250
-
* If you delete a workflow and then recreate the same workflow, the recreated workflow doesn't have the same metadata as the deleted workflow. To refresh the metadata, you have to resave any workflow that called the deleted workflow. That way, the caller gets the correct information for the recreated workflow. Otherwise, calls to the recreated workflow fail with an `Unauthorized` error. This behavior also applies to workflows that use artifacts in integration accounts and workflows that call Azure functions.
267
+
## Delete logic apps
251
268
252
-
<aname="add-workflow-portal"></a>
269
+
Deployed Consumption and Standard logic apps have different ways to delete their resources. For considerations around how deleting affects each logic app resource type, see the following documentation:
253
270
254
-
## Add another workflow in the portal
271
+
-[Considerations for deleting Consumption logic apps](/azure/logic-apps/manage-logic-apps-with-azure-portal?tabs=consumption#considerations-delete-consumption-logic-apps)
272
+
-[Considerations for deleting Standard logic apps](/azure/logic-apps/manage-logic-apps-with-azure-portal?tabs=standard#considerations-delete-standard-logic-apps)
273
+
-[Considerations for deleting Standard workflows](/azure/logic-apps/manage-logic-apps-with-azure-portal?tabs=standard#considerations-delete-standard-workflows)
255
274
256
-
Through the Azure portal, you can add blank workflows to a Standard logic app resource that you deployed from Visual Studio Code and build those workflows in the Azure portal.
275
+
### [Consumption](#tab/consumption)
257
276
258
-
1. In the [Azure portal](https://portal.azure.com), select your deployed Standard logic app resource.
277
+
1. In Visual Studio Code, on the Activity Bar, select the Azure icon to open the **Azure** pane.
259
278
260
-
1.On the logic app resource menu, select **Workflows**. On the **Workflows** pane, select **Add**.
279
+
1.In the **Logic Apps (Consumption)** section, expand your Azure subscription, and find your logic app.
261
280
262
-

281
+
1. Open the logic app shortcut menu, and select **Delete**.
263
282
264
-
1. In the **New workflow** pane, provide name for the workflow. Select either **Stateful** or **Stateless****>****Create**.
283
+
### [Standard](#tab/standard)
265
284
266
-
After Azure deploys your new workflow, which appears on the **Workflows** pane, select that workflow so that you can manage and perform other tasks, such as opening the designer or code view.
285
+
In Visual Studio Code, you can only delete an entire Standard logic app. To delete individual workflows, [use the Azure portal](/azure/logic-apps/manage-logic-apps-with-azure-portal?tabs=standard#delete-standard-workflows).
267
286
268
-

287
+
1. In Visual Studio Code, on the Activity Bar, select the Azure icon to open the **Azure** pane.
269
288
270
-
For example, opening the designer for a new workflow shows a blank canvas. You can now build this workflow in the Azure portal.
289
+
1. In the **Resources** section, expand your Azure subscription, expand **Logic App**, and find your logic app.
271
290
272
-

291
+
1. Open the logic app shortcut menu, and select **Delete logic app**.
273
292
274
-
<aname="delete-from-designer"></a>
293
+
---
275
294
276
-
## Delete items from the designer
295
+
<aname="promote-previous-versions"></a>
277
296
278
-
To delete an item in your workflow from the designer, follow any of these steps:
297
+
## Promote previous versions (Consumption only)
279
298
280
-
* Select the item, open the item's shortcut menu (Shift+F10), and select **Delete**. To confirm, select **OK**.
299
+
To publish an earlier Consumption logic app version, you can promote that version over the current version. Your logic app must have at least two versions to make the promote option available.
281
300
282
-
* Select the item, and press the delete key. To confirm, select**OK**.
301
+
1. In Visual Studio Code, on the Activity Bar, select the Azure icon to open the**Azure** pane.
283
302
284
-
* Select the item so that details pane opens for that item. In the pane's upper right corner, open the ellipses (**...**) menu, and select **Delete**. To confirm, select **OK**.
303
+
1. In the **Logic Apps (Consumption)** section, expand your Azure subscription, and find your logic app.
285
304
286
-

305
+
1. Expand your logic app, expand **Versions**, and find the earlier version to promote.
287
306
288
-
> [!TIP]
289
-
> If the ellipses menu isn't visible, expand Visual Studio Code window wide enough so that
290
-
> the details pane shows the ellipses (**...**) button in the upper right corner.
307
+
1. On the version shortcut menu, select **Promote**.
291
308
292
309
## Related content
293
310
294
-
-[Create a Standard logic app workflow ]
311
+
-[Create Standard logic app workflows in Visual Studio Code](/azure/logic-apps/create-standard-workflows-visual-studio-code)
Copy file name to clipboardExpand all lines: articles/logic-apps/manage-logic-apps-with-azure-portal.md
+42-13Lines changed: 42 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,6 +103,30 @@ When you create connections in a workflow using [connectors managed by Microsoft
103
103
104
104
---
105
105
106
+
<aname="add-workflow-portal"></a>
107
+
108
+
## Add a workflow to a Standard logic app
109
+
110
+
You can add blank workflows to a deployed Standard logic app resource continue to build these workflows in the Azure portal.
111
+
112
+
1. In the [Azure portal](https://portal.azure.com), select your deployed Standard logic app resource.
113
+
114
+
1. On the logic app resource menu, under **Workflows**, select **Workflows**.
115
+
116
+
1. On the **Workflows** page toolbar, select **Add**.
117
+
118
+

119
+
120
+
1. In the **New workflow** pane, provide name for the workflow. Select either **Stateful** or **Stateless****>****Create**.
121
+
122
+
After Azure deploys your new workflow, which appears on the **Workflows** pane, select that workflow so that you can manage and perform other tasks, such as opening the designer or code view.
123
+
124
+

125
+
126
+
For example, opening the designer for a new workflow shows a blank canvas. You can now build this workflow in the Azure portal.
127
+
128
+

129
+
106
130
<aname="disable-enable-logic-apps"></a>
107
131
108
132
## Disable or enable logic app resources
@@ -289,16 +313,17 @@ Stopping a Consumption logic app affects workflow instances in the following way
289
313
290
314
You can [delete a single or multiple Standard logic apps at the same time](#delete-standard-logic-apps). Your single-tenant based logic app can include multiple workflows, so you can either delete the entire logic app or [delete only workflows](#delete-standard-workflows).
#### Considerations for deleting Standard logic apps
295
319
296
-
Deleting a Standard logic app resource cancels in-progress and pending runs immediately, but doesn't run cleanup tasks on the storage used by the app.
320
+
-Deleting a Standard logic app resource cancels in-progress and pending runs immediately, but doesn't run cleanup tasks on the storage used by the app.
297
321
298
-
> [!NOTE]
299
-
>
300
-
> Although you can [manually recover deleted Standard logic apps](#recover-deleted-standard-logic-apps),
301
-
> using source control to manage your Standard logic apps makes recovery and redeployment much easier.
322
+
- Although you can [manually recover deleted Standard logic apps](#recover-deleted-standard-logic-apps), using source control to manage your Standard logic apps makes recovery and redeployment much easier.
323
+
324
+
<aname="delete-standard-logic-apps"></a>
325
+
326
+
#### Delete Standard logic apps
302
327
303
328
1. In the [Azure portal](https://portal.azure.com) search box, enter **logic apps**, and select **Logic apps**.
304
329
@@ -310,9 +335,9 @@ Deleting a Standard logic app resource cancels in-progress and pending runs imme
310
335
311
336
1. To confirm whether your operation succeeded or failed, on main Azure toolbar, open the **Notifications** list (bell icon).
#### Considerations for deleting Standard workflows
316
341
317
342
Deleting a Standard workflow affects workflow instances in the following ways:
318
343
@@ -322,6 +347,10 @@ Deleting a Standard workflow affects workflow instances in the following ways:
322
347
323
348
* If you delete a workflow and then recreate the same workflow, the recreated workflow won't have the same metadata as the deleted workflow. To refresh the metadata, you have to resave any workflow that called the deleted workflow. That way, the caller gets the correct information for the recreated workflow. Otherwise, calls to the recreated workflow fail with an **Unauthorized** error. This behavior also applies to workflows that use artifacts in integration accounts and workflows that call Azure functions.
324
349
350
+
<aname="delete-standard-workflows"></a>
351
+
352
+
#### Delete Standard workflows
353
+
325
354
1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
326
355
327
356
1. On the logic app menu, under **Workflows**, select **Workflows**. In the checkbox column, select a single or multiple workflows to delete.
@@ -398,11 +427,11 @@ If you're not using source control, try the following steps to recover a deleted
398
427
399
428
You can [delete a single or multiple Consumption logic apps at the same time](#delete-consumption-logic-apps).
400
429
401
-
> [!IMPORTANT]
402
-
>
403
-
> You can't recover deleted Consumption logic app resources.
0 commit comments