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-standard-workflows-visual-studio-code.md
+28-34Lines changed: 28 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.suite: integration
6
6
ms.reviewer: estfan, azla
7
7
ms.topic: how-to
8
8
ms.date: 03/17/2025
9
-
ms.custom: engagement-fy23, devx-track-dotnet
9
+
ms.custom: devx-track-dotnet
10
10
# Customer intent: As a logic apps developer, I want to create a Standard logic app workflow that runs in single-tenant Azure Logic Apps using Visual Studio Code.
11
11
---
12
12
@@ -769,54 +769,48 @@ Before you deploy your Standard logic app to the Azure portal, review this secti
769
769
770
770
### Set up firewall access
771
771
772
-
If your environment has strict network requirements or firewalls that limit traffic, you have to set up permissions for any connections in your workflow.
772
+
If your environment has strict network requirements or firewalls that limit traffic, you have to set up permissions for any connections created by [Azure managed, hosted, and shared connectors](/azure/connectors/managed) and used in your workflow.
773
773
774
774
To find the fully qualified domain names (FQDNs) for these connections, follow these steps:
775
775
776
-
1. In your logic app project, open the **connections.json** file, and find the **`managedApiConnections`** object.
776
+
1. In your logic app project, open the **local.settings.json** file.
777
777
778
-
The **connections.json** file is created after you add the first connection-based trigger or action to your workflow.
778
+
1. For each connection that you created, find the property named **`<connection-name>-ConnectionRuntimeUrl`**, which uses the following syntax:
779
779
780
-
1. For each connection that you created, copy and save the **`connectionRuntimeUrl`** property value somewhere safe so that you can set up your firewall with this information.
The following example **connections.json** file contains two connections, an Office 365 connection and an AS2 connection. Both use managed identities for authentication and have the following **`connectionRuntimeUrl`** values, respectively:
782
+
1. Copy and save this connection property value somewhere safe so that you can set up your firewall with this information.
For example, suppose you have a sample **local.settings.json** file that contains these connections: an Office 365 connection and an AS2 connection. These connections use the following respective sample values for the **`<connection-name>-ConnectionRuntimeUrl`** properties:
0 commit comments