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/create-single-tenant-workflows-visual-studio-code.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -354,7 +354,7 @@ By default, Visual Studio Code creates a logic app project that is extension bun
354
354
>
355
355
> This action is a one-way operation that you can't undo.
356
356
357
-
1. In the Explorer pane, at your project's root, move your mouse pointer over any blank area below all the other files and folders, open the shortcut menu, and select **Convert to NuGet-based Logic App project**.
357
+
1. In the Explorer pane, at your project's root, move your mouse pointer over any blank area below all the other files and folders, open the shortcut menu, and select **Convert to NuGet-based logic app project**.
358
358
359
359

360
360
@@ -474,7 +474,7 @@ If you created your logic app project when assemblies support wasn't available f
474
474
> When Visual Studio Code starts the workflow design-time API, you might get a message
475
475
> that startup might take a few seconds. You can ignore this message or select **OK**.
476
476
>
477
-
> If the designer won't open, review the troubleshooting section, [Designer fails to open](#designer-fails-to-open).
477
+
> If the designer won't open, see the troubleshooting section, [Designer fails to open](#designer-fails-to-open).
478
478
479
479
After the designer appears, the **Add a trigger** prompt appears on the designer.
480
480
@@ -917,17 +917,17 @@ To find the fully qualified domain names (FQDNs) for these connections, follow t
917
917
918
918
From Visual Studio Code, you can directly publish your project to Azure to deploy your Standard logic app resource. You can publish your logic app as a new resource, which automatically creates any necessary resources, such as an [Azure Storage account, similar to function app requirements](../azure-functions/storage-considerations.md). Or, you can publish your logic app to a previously deployed Standard logic app resource, which overwrites that logic app.
919
919
920
-
Deployment for the Standard logic app resource requires a hosting plan and pricing tier, which you select during deployment. For more information, review[Hosting plans and pricing tiers](logic-apps-pricing.md#standard-pricing).
920
+
Deployment for the Standard logic app resource requires a hosting plan and pricing tier, which you select during deployment. For more information, see[Hosting plans and pricing tiers](logic-apps-pricing.md#standard-pricing).
921
921
922
922
<aname="publish-new-logic-app"></a>
923
923
924
924
### Publish to a new Standard logic app resource
925
925
926
926
1. On the Visual Studio Code Activity Bar, select the Azure icon to open the Azure window.
927
927
928
-
1. In the **Azure** window, on the **Workspace** section toolbar, from the **Azure Logic Apps** menu, select **Deploy to Logic App**.
928
+
1. In the **Azure** window, on the **Workspace** section toolbar, from the **Azure Logic Apps** menu, select **Deploy to logic app**.
929
929
930
-

930
+

931
931
932
932
1. If prompted, select the Azure subscription to use for your logic app deployment.
933
933
@@ -953,7 +953,7 @@ Deployment for the Standard logic app resource requires a hosting plan and prici
953
953
954
954
1. Provide a name for your hosting plan, and then select a pricing tier for your selected plan.
955
955
956
-
For more information, review[Hosting plans and pricing tiers](logic-apps-pricing.md#standard-pricing).
956
+
For more information, see[Hosting plans and pricing tiers](logic-apps-pricing.md#standard-pricing).
957
957
958
958
1. For optimal performance, select the same resource group as your project for the deployment.
959
959
@@ -1115,7 +1115,7 @@ In Visual Studio Code, you can view all the deployed logic apps in your Azure su
1115
1115
1116
1116
> [!NOTE]
1117
1117
> The stop logic app and delete logic app operations affect workflow instances in different ways.
1118
-
> For more information, review [Considerations for stopping logic apps](#considerations-stop-logic-apps) and
1118
+
> For more information, see [Considerations for stopping logic apps](#considerations-stop-logic-apps) and
1119
1119
> [Considerations for deleting logic apps](#considerations-delete-logic-apps).
1120
1120
1121
1121

@@ -1313,7 +1313,7 @@ To enable Application Insights on a deployed logic app or to review Application
1313
1313
1314
1314
If Application Insights is enabled, on the **Application Insights** pane, select **View Application Insights data**.
1315
1315
1316
-
After Application Insights opens, you can review various metrics for your logic app. For more information, review these topics:
1316
+
After Application Insights opens, you can review various metrics for your logic app. For more information, see these articles:
1317
1317
1318
1318
*[Azure Logic Apps Running Anywhere - Monitor with Application Insights - part 1](https://techcommunity.microsoft.com/t5/integrations-on-azure/azure-logic-apps-running-anywhere-monitor-with-application/ba-p/1877849)
1319
1319
*[Azure Logic Apps Running Anywhere - Monitor with Application Insights - part 2](https://techcommunity.microsoft.com/t5/integrations-on-azure/azure-logic-apps-running-anywhere-monitor-with-application/ba-p/2003332)
0 commit comments