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-hybrid-deployment.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,7 +118,7 @@ After you meet the prerequisites, create your Standard logic app for hybrid depl
118
118
> use either the Workflow Service Plan or App Service Environment V3 hosting option. For more information,
119
119
> see [Known issues and troubleshooting - Azure portal](#known-issues-portal).
120
120
121
-
1. In the Azure portal, on the logic app menu, under **Workflows**, select **Workflows**. add an empty stateful or stateless workflow. You then build your workflow by adding a trigger and actions. For more information, see [Build a workflow with a trigger and actions](create-workflow-with-trigger-or-action.md).
121
+
1. In the Azure portal, on the resource menu, under **Workflows**, select **Workflows**. add an empty stateful or stateless workflow. You then build your workflow by adding a trigger and actions. For more information, see [Build a workflow with a trigger and actions](create-workflow-with-trigger-or-action.md).
122
122
123
123
> [!NOTE]
124
124
>
@@ -280,7 +280,22 @@ You can control the automatic scaling for the range of replicas that deploy in r
280
280
281
281
## Control inbound traffic to your logic app in Azure portal
282
282
283
+
You can expose your logic app to the public web, your virtual network, and other logic apps in your environment by enabling ingress. Azure enforces ingress settings through a set of rules that control the routing of external and internal traffic to your logic app. When you enable ingress, you don't need to create an Azure Load Balancer, public IP address, or any other Azure resources to enable incoming HTTP requests or TCP traffic. For more information, see [Ingress in Container Apps](../container-apps/ingress-overview.md).
283
284
285
+
> [!NOTE]
286
+
>
287
+
> When you enable ingress, all of the traffic will be directed to your latest revision by default. Go to Revision management page to change traffic settings.
288
+
289
+
1. On the resource menu, under **Settings**, select **Ingress**.
290
+
291
+
1. On the **Ingress** page, next to **Igress**, select the **Enabled** box.
292
+
293
+
1. Based on your scenario, configure the remaining options.
294
+
295
+
For more information, see the following documentation:
296
+
297
+
-[Configure ingress for your app in Azure Container Apps](../container-apps/ingress-how-to.md?pivots=azure-portal)
298
+
-[Set up IP ingress restrictions in Azure Container Apps](../container-apps/ip-restrictions.md?pivots=azure-portal)
0 commit comments