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-with-visual-studio.md
+31-31Lines changed: 31 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Quickstart - Create integration workflows with multi-tenant Azure Logic A
3
3
description: Create automated integration workflows with multi-tenant Azure Logic Apps and Visual Studio Code.
4
4
services: logic-apps
5
5
ms.suite: integration
6
-
ms.reviewer: logicappspm
6
+
ms.reviewer: azla
7
7
ms.topic: quickstart
8
8
ms.custom: mvc, mode-ui
9
9
ms.date: 07/21/2022
@@ -16,11 +16,11 @@ ms.date: 07/21/2022
16
16
17
17
This quickstart shows how to design, develop, and deploy automated workflows that integrate apps, data, systems, and services across enterprises and organizations by using multi-tenant [Azure Logic Apps](../logic-apps/logic-apps-overview.md) and Visual Studio. Although you can perform these tasks in the Azure portal, Visual Studio lets you add your logic apps to source control, publish different versions, and create Azure Resource Manager templates for different deployment environments. For more information about multi-tenant versus single-tenant model, review [Single-tenant versus multi-tenant and integration service environment](single-tenant-overview-compare.md).
18
18
19
-
If you're new to Azure Logic Apps and just want the basic concepts, try the [quickstart for creating a logic app in the Azure portal](../logic-apps/quickstart-create-first-logic-app-workflow.md). The Logic App Designer works similarly in both the Azure portal and Visual Studio.
19
+
If you're new to Azure Logic Apps and just want the basic concepts, try the [quickstart for creating a logic app workflow in the Azure portal](quickstart-create-first-logic-app-workflow.md). The workflow designer works similarly in both the Azure portal and Visual Studio.
20
20
21
-
In this quickstart, you create the same logic app with Visual Studio as the Azure portal quickstart. You can also learn to [create an example app in Visual Studio Code](quickstart-create-logic-apps-visual-studio-code.md), and [create and manage logic apps via the Azure CLI](quickstart-logic-apps-azure-cli.md).This logic app monitors a website's RSS feed and sends email for each new item in that feed. Your finished logic app looks like this high-level workflow:
21
+
In this quickstart, you create the same logic app workflow with Visual Studio as the Azure portal quickstart. You can also learn to [create an example logic app workflow in Visual Studio Code](quickstart-create-logic-apps-visual-studio-code.md), and [create and manage logic app workflows using the Azure CLI](quickstart-logic-apps-azure-cli.md).This logic app workflow monitors a website's RSS feed and sends email for each new item in that feed. Your finished logic app workflow looks like the following high-level workflow:
22
22
23
-

23
+

24
24
25
25
<aname="prerequisites"></a>
26
26
@@ -49,19 +49,19 @@ In this quickstart, you create the same logic app with Visual Studio as the Azur
49
49
50
50
You can either download and install Azure Logic Apps Tools directly from the Visual Studio Marketplace, or learn [how to install this extension from inside Visual Studio](/visualstudio/ide/finding-and-using-visual-studio-extensions). Make sure that you restart Visual Studio after you finish installing.
51
51
52
-
* Access to the web while using the embedded Logic App Designer
52
+
* Access to the web while using the embedded workflow designer
53
53
54
54
The designer needs an internet connection to create resources in Azure and to read properties and data from connectors in your logic app.
55
55
56
-
* An email account that's supported by Logic Apps, such as Outlook for Microsoft 365, Outlook.com, or Gmail. For other providers, review the [connectors list here](/connectors/). This example uses Office 365 Outlook. If you use a different provider, the overall steps are the same, but your UI might slightly differ.
56
+
* An email account that's supported by Azure Logic Apps, such as Outlook for Microsoft 365, Outlook.com, or Gmail. For other providers, review the [connectors list here](/connectors/). This example uses Office 365 Outlook. If you use a different provider, the overall steps are the same, but your UI might slightly differ.
57
57
58
58
> [!IMPORTANT]
59
59
> If you want to use the Gmail connector, only G-Suite business accounts can use this connector without restriction in logic apps.
60
60
> If you have a Gmail consumer account, you can use this connector with only specific Google-approved services, or you can
61
61
> [create a Google client app to use for authentication with your Gmail connector](/connectors/gmail/#authentication-and-bring-your-own-application).
62
62
> For more information, see [Data security and privacy policies for Google connectors in Azure Logic Apps](../connectors/connectors-google-data-security-privacy-policy.md).
63
63
64
-
* If your logic app needs to communicate through a firewall that limits traffic to specific IP addresses, that firewall needs to allow access for *both* the [inbound](logic-apps-limits-and-config.md#inbound) and [outbound](logic-apps-limits-and-config.md#outbound) IP addresses used by the Logic Apps service or runtime in the Azure region where your logic app exists. If your logic app also uses [managed connectors](../connectors/managed.md), such as the Office 365 Outlook connector or SQL connector, or uses [custom connectors](/connectors/custom-connectors/), the firewall also needs to allow access for *all* the [managed connector outbound IP addresses](logic-apps-limits-and-config.md#outbound) in your logic app's Azure region.
64
+
* If your logic app workflow needs to communicate through a firewall that limits traffic to specific IP addresses, that firewall needs to allow access for *both* the [inbound](logic-apps-limits-and-config.md#inbound) and [outbound](logic-apps-limits-and-config.md#outbound) IP addresses used by the Azure Logic Apps service or runtime in the Azure region where your logic app resource exists. If your logic app workflow also uses [managed connectors](../connectors/managed.md), such as the Office 365 Outlook connector or SQL connector, or uses [custom connectors](/connectors/custom-connectors/), the firewall also needs to allow access for *all* the [managed connector outbound IP addresses](logic-apps-limits-and-config.md#outbound) in your logic app resource's Azure region.
65
65
66
66
<aname="azure-government"></a>
67
67
@@ -101,11 +101,11 @@ To get started, create an [Azure Resource Group project](../azure-resource-manag
101
101
102
102
1. On the **File** menu, select **New** > **Project**. (Keyboard: Ctrl + Shift + N)

105
105
106
106
1. Under **Installed**, select **Visual C#** or **Visual Basic**. Select **Cloud** > **Azure Resource Group**. Name your project, for example:
107
107
108
-

108
+

109
109
110
110
> [!NOTE]
111
111
> Resource group names can contain only letters, numbers,
@@ -123,19 +123,19 @@ To get started, create an [Azure Resource Group project](../azure-resource-manag
123
123
124
124
1. From the template list, select the **Logic App** template. Select **OK**.

127
127
128
128
After Visual Studio creates your project, Solution Explorer opens and shows your solution. In your solution, the **LogicApp.json** file not only stores your logic app definition but is also an Azure Resource Manager template that you can use for deployment.
129
129
130
-

130
+

131
131
132
132
## Create blank logic app
133
133
134
134
When you have your Azure Resource Group project, create your logic app with the **Blank Logic App** template.
135
135
136
136
1. In Solution Explorer, open the **LogicApp.json** file's shortcut menu. Select **Open With Logic App Designer**. (Keyboard: Ctrl + L)
137
137
138
-

138
+

139
139
140
140
> [!TIP]
141
141
> If you don't have this command in Visual Studio 2019, check that you have the latest updates for Visual Studio.
@@ -154,21 +154,21 @@ When you have your Azure Resource Group project, create your logic app with the
154
154
|**Location**|**Same as Resource Group**| The location type and specific location for deploying your logic app. The location type is either an Azure region or an existing [integration service environment (ISE)](connect-virtual-network-vnet-isolated-environment.md). <p>For this quickstart, keep the location type set to **Region** and the location set to **Same as Resource Group**. <p>**Note**: After you create your resource group project, you can [change the location type and the location](manage-logic-apps-with-visual-studio.md#change-location), but different location type affects your logic app in various ways. |
155
155
||||
156
156
157
-
1. The Logic Apps Designer opens a page that shows an introduction video and commonly used triggers. Scroll down past the video and triggers to **Templates**, and select **Blank Logic App**.
157
+
1. The workflow designer opens a page that shows an introduction video and commonly used triggers. Scroll down past the video and triggers to **Templates**, and select **Blank Logic App**.
Next, add an RSS [trigger](../logic-apps/logic-apps-overview.md#logic-app-concepts) that fires when a new feed item appears. Every logic app starts with a trigger, which fires when specific criteria is met. Each time the trigger fires, the Logic Apps engine creates a logic app instance that runs your workflow.
163
+
Next, add an RSS [trigger](../logic-apps/logic-apps-overview.md#logic-app-concepts) that fires when a new feed item appears. Every logic app starts with a trigger, which fires when specific criteria is met. Each time the trigger fires, the Azure Logic Apps engine creates a logic app instance that runs your workflow.
164
164
165
-
1. In Logic App Designer, under the search box, select **All**. In the search box, enter "rss". From the triggers list, select this trigger: **When a feed item is published**
165
+
1. In workflow designer, under the search box, select **All**. In the search box, enter "rss". From the triggers list, select this trigger: **When a feed item is published**
166
166
167
-

167
+

168
168
169
169
1. After the trigger appears in the designer, finish building the logic app by following the workflow steps in the [Azure portal quickstart](../logic-apps/quickstart-create-first-logic-app-workflow.md#add-rss-trigger), then return to this article. When you're done, your logic app looks like this example:

184
184
185
185
1. For this deployment, keep the default Azure subscription, resource group, and other settings. Select **Deploy**.
186
186
187
-

187
+

188
188
189
189
1. If the **Edit Parameters** box appears, provide a resource name for your logic app. Save your settings.
190
190
191
-

191
+

192
192
193
193
When deployment starts, your app's deployment status appears in the Visual Studio **Output** window. If the status doesn't appear, open the **Show output from** list, and select your Azure resource group.
194
194
195
-

195
+

196
196
197
197
If your selected connectors need input from you, a PowerShell window opens in the background and prompts for any necessary passwords or secret keys. After you enter this information, deployment continues.

200
200
201
-
After deployment finishes, your logic app is live in the Azure portal and runs on your specified schedule (every minute). If the trigger finds new feed items, the trigger fires, which creates a workflow instance that runs your logic app's actions. Your logic app sends email for each new item. Otherwise, if the trigger doesn't find new items, the trigger doesn't fire and "skips" instantiating the workflow. Your logic app waits until the next interval before checking.
201
+
After deployment finishes, your logic app is live in the Azure portal and runs on your specified schedule (every minute). If the trigger finds new feed items, the trigger fires and creates a workflow instance that runs your logic app workflow's actions. Your workflow sends email for each new item. Otherwise, if the trigger doesn't find new items, the trigger doesn't fire and "skips" instantiating the workflow. Your workflow waits until the next interval before checking.
202
202
203
-
Here are sample emails that this logic app sends. If you don't get any emails, check your junk email folder.
203
+
Here are sample emails that this workflow sends. If you don't get any emails, check your junk email folder.
204
204
205
205

206
206
207
-
Congratulations, you've successfully built and deployed your logic app with Visual Studio. To manage your logic app and review its run history, see [Manage logic apps with Visual Studio](../logic-apps/manage-logic-apps-with-visual-studio.md).
207
+
Congratulations, you've successfully built and deployed your logic app workflow with Visual Studio. To manage your logic app workflow and review its run history, see [Manage logic apps with Visual Studio](manage-logic-apps-with-visual-studio.md).
208
208
209
209
## Add new logic app
210
210
@@ -216,11 +216,11 @@ When you have an existing Azure Resource Group project, you can add a new blank
216
216
217
217
1. To add a resource to the template file, select **Add Resource** at the top of the JSON Outline window. Or in the JSON Outline window, open the **resources** shortcut menu, and select **Add New Resource**.

220
220
221
-
1. In the **Add Resource** dialog box, in the search box, find `logic app`, and select **Logic App**. Name your logic app, and select **Add**.
221
+
1. In the **Add Resource** dialog box, in the search box, find `logic app`, and select **Logic App**. Name your logic app resource, and select **Add**.
1. Delete the Visual Studio solution from your local computer.
238
238
239
239
## Next steps
240
240
241
-
In this article, you built, deployed, and ran your logic app with Visual Studio. To learn about managing and performing advanced deployment for logic apps with Visual Studio, see these articles:
241
+
In this article, you built, deployed, and ran your logic app workflow with Visual Studio. To learn about managing and performing advanced deployment for logic apps with Visual Studio, see these articles:
242
242
243
243
> [!div class="nextstepaction"]
244
244
> [Manage logic apps with Visual Studio](../logic-apps/manage-logic-apps-with-visual-studio.md)
0 commit comments