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
> Throttling happens at the connection level, so reusing the same connection across multiple logic apps might increase the potential for throttling problems.
124
124
125
-
* Unless your scenario involves services and systems that require multi-factor authentication, you can use a PowerShell script to provide consent for each OAuth connection by running a continuous integration worker as a standard user account on a virtual machine that has active browser sessions with the authorizations and consent already provided. For example, you can repurpose the sample script provided by the [LogicAppConnectionAuth project in the Logic Apps GitHub repo](https://github.com/logicappsio/LogicAppConnectionAuth).
125
+
* Unless your scenario involves services and systems that require multifactor authentication, you can use a PowerShell script to provide consent for each OAuth connection by running a continuous integration worker as a standard user account on a virtual machine that has active browser sessions with the authorizations and consent already provided. For example, you can repurpose the sample script provided by the [LogicAppConnectionAuth project in the Logic Apps GitHub repo](https://github.com/logicappsio/LogicAppConnectionAuth).
126
126
127
127
* If you use a Microsoft Entra [service principal](/azure/active-directory/develop/app-objects-and-service-principals) instead to authorize connections, learn how to [specify service principal parameters in your logic app template](/azure/logic-apps/logic-apps-azure-resource-manager-templates-overview.md#authenticate-connections).
Copy file name to clipboardExpand all lines: articles/logic-apps/manage-logic-apps-with-visual-studio.md
+32-21Lines changed: 32 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ You can create, edit, manage, and deploy automated workflows that integrate serv
22
22
23
23
## Prerequisites
24
24
25
-
* An Azure subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/).
25
+
* An Azure subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
26
26
27
27
* Download and install these tools, if you don't have them already:
28
28
@@ -65,7 +65,7 @@ In Visual Studio, you can find all the logic apps that are associated with your
65
65
66
66
1. In Cloud Explorer, select the **Account Management** icon. Select the Azure subscription associated with your logic apps, and select **Apply**. For example:

69
69
70
70
1. Next to the **Account Management** icon, select **Resource Types**. Under your Azure subscription, expand **Logic Apps** so that you can view all the deployed logic apps that are associated with your subscription.
71
71
@@ -82,9 +82,10 @@ In Visual Studio, you can open logic apps previously created and deployed either
82
82
1. From the logic app's shortcut menu, select **Open with Logic App Editor**.
83
83
84
84
> [!TIP]
85
+
>
85
86
> If you don't have this command in Visual Studio 2019, check that you have the latest updates for Visual Studio.
86
87
87
-

88
+

88
89
89
90
After the logic app opens in Logic Apps Designer, at the bottom of the designer, you can select **Code View** so that you can review the underlying logic app definition structure. If you want to create a deployment template for the logic app, learn [how to download an Azure Resource Manager template](#download-logic-app) for that logic app. Learn more about [Resource Manager templates](../azure-resource-manager/templates/overview.md).
90
91
@@ -99,17 +100,18 @@ You can [download](../azure-resource-manager/templates/export-template-portal.md
99
100
1. From the logic app's shortcut menu, select **Open with Logic App Editor**.
100
101
101
102
> [!TIP]
103
+
>
102
104
> If you don't have this command in Visual Studio 2019, check that you have the latest updates for Visual Studio.
103
105
104
106
The logic app opens in the workflow designer.
105
107
106
108
1. On the designer toolbar, select **Download**.
107
109
108
-

110
+

109
111
110
112
1. When you're prompted for a location, browse to that location and save the Resource Manager template for the logic app definition in JSON (.json) file format.
111
113
112
-
Your logic app definition appears in the `resources` subsection inside the Resource Manager template. You can now edit the logic app definition and Resource Manager template with Visual Studio. You can also add the template as an [Azure Resource Group project](../azure-resource-manager/templates/create-visual-studio-deployment-project.md) to a Visual Studio solution. Learn about [Azure Resource Group projects for logic apps in Visual Studio](../logic-apps/quickstart-create-logic-apps-with-visual-studio.md).
114
+
Your logic app definition appears in the **`resources`** subsection inside the Resource Manager template. You can now edit the logic app definition and Resource Manager template with Visual Studio. You can also add the template as an [Azure Resource Group project](../azure-resource-manager/templates/create-visual-studio-deployment-project.md) to a Visual Studio solution. Learn about [Azure Resource Group projects for logic apps in Visual Studio](../logic-apps/quickstart-create-logic-apps-with-visual-studio.md).
113
115
114
116
<aname="link-integration-account"></a>
115
117
@@ -121,21 +123,23 @@ To build logic apps for business-to-business (B2B) enterprise integration scenar
121
123
122
124
1. In Solution Explorer, open the **\<logic-app-name\>.json** file's shortcut menu, and select **Open With Logic App Designer**. (Keyboard: Ctrl + L)
123
125
124
-

126
+

125
127
126
128
> [!TIP]
129
+
>
127
130
> If you don't have this command in Visual Studio 2019, check that you have the latest updates to Visual Studio and the Azure Logic Apps Tools extension.
128
131
129
132
1. Make sure that the workflow designer has focus by selecting the designer's tab or surface so that the Properties window shows the **Integration Account** property for your logic app.

132
135
133
136
> [!TIP]
137
+
>
134
138
> If the Properties window isn't already open, from the **View** menu, select **Properties Window**. (Keyboard: Press F4)
135
139
136
140
1. Open the **Integration Account** property list, and select the integration account that you want to link to your logic app, for example:

139
143
140
144
1. When you're done, remember to save your Visual Studio solution.
141
145
@@ -153,21 +157,25 @@ To change your logic app's location type or location, you have to open your logi
153
157
154
158
1. In Solution Explorer, open the `<logic-app-name>.json` file's shortcut menu, and select **Open With Logic App Designer**. (Keyboard: Ctrl + L)
155
159
156
-

160
+

157
161
158
162
> [!TIP]
163
+
>
159
164
> If you don't have this command in Visual Studio 2019, check that you have the latest updates to Visual Studio and the Azure Logic Apps Tools extension.
160
165
161
-
1. Make sure that the workflow designer has focus by selecting the designer's tab or surface so that the Properties window shows the **Choose Location Type** and **Location** properties for your logic app. The project's location type is set to **Region**.
166
+
1. Make sure that the workflow designer has focus by selecting the designer's tab or surface so that the Properties window shows the **Choose Location Type** and **Location** properties for your logic app.

164
171
165
172
> [!TIP]
173
+
>
166
174
> If the Properties window isn't already open, from the **View** menu, select **Properties Window**. (Keyboard: Press F4)
167
175
168
176
1. To change the specific location, open the **Location** property list. Based on the location type, select the location that you want, for example:
169
177
170
-

178
+

171
179
172
180
1. When you're done, remember to save your Visual Studio solution.
173
181
@@ -185,38 +193,39 @@ If you edit your logic app in the Azure portal and want to keep those changes, m
185
193
186
194
* In Visual Studio Cloud Explorer, open your logic app's shortcut menu, and select **Refresh**.
187
195
188
-

196
+

189
197
190
198
## Publish logic app updates
191
199
192
200
When you're ready to deploy your logic app updates from Visual Studio to Azure, on the workflow designer toolbar, select **Publish**.
193
201
194
-

202
+

195
203
196
204
## Manually run your logic app
197
205
198
206
You can manually trigger a logic app deployed in Azure from Visual Studio. On the workflow designer toolbar, select **Run Trigger**.
199
207
200
-

208
+

201
209
202
210
## Review run history
203
211
204
212
To check the status and diagnose problems with logic app runs, you can review the details, such as inputs and outputs, for those runs in Visual Studio.
205
213
206
214
1. In Cloud Explorer, open your logic app's shortcut menu, and select **Open run history**.
207
215
208
-

216
+

209
217
210
218
1. To view the details for a specific run, double-click a run. For example:
211
219
212
-

220
+

213
221
214
222
> [!TIP]
223
+
>
215
224
> To sort the table by property, select the column header for that property.
216
225
217
226
1. Expand the steps whose inputs and outputs you want to review, for example:
218
227
219
-

228
+

220
229
221
230
<aname="disable-enable-logic-apps"></a>
222
231
@@ -235,7 +244,9 @@ To stop the trigger from firing the next time when the trigger condition is met,
235
244
To stop the trigger from firing on unprocessed items since the last run, clear the trigger's state before you reactivate the logic app:
236
245
237
246
1. In the logic app, edit any part of the workflow's trigger.
247
+
238
248
1. Save your changes. This step resets your trigger's current state.
249
+
239
250
1.[Reactivate your logic app](#enable-logic-apps).
240
251
241
252
* When a workflow is disabled, you can still resubmit runs.
@@ -254,7 +265,7 @@ In Cloud Explorer, open your logic app's shortcut menu, and select **Disable**.
254
265
255
266
In Cloud Explorer, open your logic app's shortcut menu, and select **Enable**.
256
267
257
-

268
+

258
269
259
270
<aname="delete-logic-apps"></a>
260
271
@@ -268,11 +279,11 @@ Deleting a logic app affects workflow instances in following ways:
268
279
269
280
* Azure Logic Apps doesn't create or run new workflow instances.
270
281
271
-
* If you delete a workflow and then recreate the same workflow, the recreated workflow won't have the same metadata as the deleted workflow. 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.
282
+
* If you delete a workflow and then recreate the same workflow, the recreated workflow won't have the same metadata as the deleted workflow. 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.
272
283
273
284
To delete your logic app from the Azure portal, in Cloud Explorer, open your logic app's shortcut menu, and select **Delete**.
274
285
275
-

286
+

0 commit comments