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/quickstart-create-logic-apps-visual-studio-code.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Quickstart - Create Consumption Workflows by using Visual Studio Code
3
-
description: Create and publish Consumption automation and integration workflows in multitenant Azure Logic Apps by using Visual Studio Code.
3
+
description: Create and publish Consumption workflows in multitenant Azure Logic Apps for automation and integration solutions by using Visual Studio Code.
As an integration developer, you often need to automate business processes across SaaS apps, enterprise systems, and data sources without managing infrastructure. You also need a code-first way to build workflows so you can more efficiently version definitions, make updates, and review changes.
21
+
As an integration developer, you often need to automate business processes across SaaS apps, enterprise systems, and data sources without managing infrastructure. You also need a code-first way to build workflows so you can version definitions, make updates, and review changes efficiently.
22
22
23
23
This quickstart shows how to create and manage Consumption workflows in multitenant Azure Logic Apps by using the local, code-first tools in Visual Studio Code. Consumption workflows provide a serverless integration model for event-driven and scheduled workflows, so you can connect services and automate processes while paying only for the actions that run.
24
24
25
-
In Visual Studio Code, you can edit workflow definitions in JavaScript Object Notation (JSON) by using the code editor, use the visual designer when needed, and manage deployed workflows in Azure. You can also work on workflows and integration accounts from any development platform where Visual Studio Code runs, such as Linux, Windows, and Mac.
25
+
In Visual Studio Code, you can edit workflow definitions in JavaScript Object Notation (JSON) by using the code editor, use the visual designer when needed, and manage deployed workflows in Azure. You can also work on workflows and integration accounts from any development platform where Visual Studio Code runs, such as Linux, Windows, and macOS.
26
26
27
27
The following screenshot shows how an example Consumption workflow definition might look:
28
28
@@ -37,17 +37,17 @@ For more information, see:
37
37
38
38
- An Azure account and subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
39
39
40
-
- Basic knowledge about [logic app workflow definitions](logic-apps-workflow-definition-language.md) and their structure in JSON format
40
+
- Basic knowledge about [logic app workflow definitions](logic-apps-workflow-definition-language.md) and their structure in JSON format.
41
41
42
-
The example in this article creates the same logic app workflow in this [quickstart](quickstart-create-example-consumption-workflow.md) that focuses more on the basic concepts. You can also [learn to create and manage workflows through the Azure CLI](quickstart-logic-apps-azure-cli.md).
42
+
The example in this article creates the same logic app workflow as in this [quickstart](quickstart-create-example-consumption-workflow.md) that focuses more on the basic concepts. You can also [learn to create and manage workflows through the Azure CLI](quickstart-logic-apps-azure-cli.md).
43
43
44
-
- Access to the web for signing in to Azure and your Azure subscription
44
+
- Access to the web for signing in to Azure and your Azure subscription.
45
45
46
46
- Download and install the following tools, if you don't have them already:
47
47
48
-
-[Visual Studio Code version 1.25.1 or later](https://code.visualstudio.com/), which is free
48
+
-[Visual Studio Code version 1.25.1 or later](https://code.visualstudio.com/), which is free.
49
49
50
-
- Visual Studio Code extension for Azure Logic Apps (Consumption)
50
+
- Visual Studio Code extension for Azure Logic Apps (Consumption).
51
51
52
52
1. Install this extension from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-logicapps) or directly from inside Visual Studio Code.
53
53
@@ -67,7 +67,7 @@ For more information, see:
67
67
68
68
1. In Visual Studio Code, [sign in to your Azure account](https://code.visualstudio.com/docs/azure/resourcesextension#_how-to-sign-in-to-your-azure-account).
69
69
70
-
If sign in takes longer than usual, Visual Studio Code prompts you to sign in through a Microsoft authentication website by providing you with a device code. To sign in with the code instead, follow these steps:
70
+
If sign in takes longer than usual, Visual Studio Code prompts you to sign in through a Microsoft authentication website by providing you with a device code. To sign in by using the code instead, follow these steps:
71
71
72
72
1. Select **Use Device Code**, and then select **Copy & Open**.
73
73
@@ -214,7 +214,7 @@ The read-only designer opens in a separate tab and shows the logic app workflow,
214
214
215
215
To review your logic app workflow definition in Azure portal, follow these steps:
216
216
217
-
1. In the [Azure portal](https://portal.azure.com), sign in with the same Azure account and subscription associated with your logic app.
217
+
1. In the [Azure portal](https://portal.azure.com), sign in by using the same Azure account and subscription associated with your logic app.
218
218
219
219
1. In the Azure portal search box, enter the logic app name. From the results list, select the logic app.
220
220
@@ -240,11 +240,11 @@ In Visual Studio Code, you can open and edit the workflow definition for an alre
240
240
241
241
:::image type="content" source="media/quickstart-create-logic-apps-visual-studio-code/open-editor-existing-logic-app.png" alt-text="Screenshot that shows Azure window, logic app shortcut menu, and Open in Editor selected.":::
242
242
243
-
Visual Studio Code opens the *.logicapp.json file* in your local temporary folder so you can view the workflow definition.
243
+
Visual Studio Code opens the *.logicapp.json* file in your local temporary folder so you can view the workflow definition.
244
244
245
245
:::image type="content" source="media/quickstart-create-logic-apps-visual-studio-code/edit-published-logic-app-workflow-definition.png" alt-text="Screenshot that shows Visual Studio Code and the opened logic app workflow definition file.":::
246
246
247
-
1. Make your changes in the workflow definition file
247
+
1. Make your changes in the workflow definition file.
248
248
249
249
1. When you finish, save your changes (**File** > **Save** or press Ctrl+S).
250
250
@@ -256,11 +256,11 @@ In Visual Studio Code, you can open and edit the workflow definition for an alre
256
256
257
257
## View or promote other versions
258
258
259
-
In Visual Studio Code, you can open and review the earlier versions for your logic app workflow. You can also promote an earlier version to the current version.
259
+
In Visual Studio Code, you can open and review earlier versions for your logic app workflow. You can also promote an earlier version to the current version.
260
260
261
261
> [!IMPORTANT]
262
262
>
263
-
> Before you change an actively running logic app workflow in production, you can minimize disruption and avoid the risk of breaking that logic app if you first [disable your logic app resource](#disable-enable-logic-apps).
263
+
> Before you change an actively running logic app workflow in production, minimize disruption and avoid the risk of breaking that logic app by first [disabling your logic app resource](#disable-enable-logic-apps).
264
264
265
265
1. In the Azure window, in the **Logic Apps (Consumption)** section, expand your Azure subscription to view the associated logic apps.
266
266
@@ -332,13 +332,13 @@ To disable or enable a logic app resource in Visual Studio Code, follow these st
332
332
333
333
Deleting a logic app affects workflow instances in the following ways:
334
334
335
-
- Azure Logic Apps makes a best effort to cancel any in-progress and pending workflow runs.
335
+
- Azure Logic Apps tries to cancel any in-progress and pending workflow runs.
336
336
337
-
Even with a large volume or backlog, most runs are canceled before they finish or start. However, the cancelation process might take time to complete. Meanwhile, some runs might get picked up for execution while the service works through the cancelation process.
337
+
Even with a large volume or backlog, most runs are canceled before they finish or start. However, the cancellation process might take time to complete. Meanwhile, the service might pick up some runs for execution while it works through the cancellation process.
338
338
339
339
- Azure Logic Apps doesn't create or run new workflow instances.
340
340
341
-
- If you delete a workflow and then recreate the same workflow, the recreated workflow has different metadata. You need 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.
341
+
- If you delete a workflow and then recreate the same workflow, the recreated workflow has different metadata. You need to resave any workflow that called the deleted workflow. When you resave, 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.
342
342
343
343
To delete a logic app resource from Visual Studio Code, follow these steps:
0 commit comments