Skip to content

Commit f4aaae5

Browse files
author
ecfan
committed
Draft updates
1 parent 7ce9385 commit f4aaae5

File tree

2 files changed

+8
-15
lines changed

2 files changed

+8
-15
lines changed

articles/logic-apps/create-single-tenant-workflows-azure-portal.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ In single-tenant Azure Logic Apps, workflows in the same logic app resource and
6161

6262
* To deploy your Standard logic app resource to an [App Service Environment v3 (ASEv3) - Windows plan only](../app-service/environment/overview.md), you have to create this environment resource first. You can then select this environment as the deployment location when you create your logic app resource. For more information, review [Resources types and environments](single-tenant-overview-compare.md#resource-environment-differences) and [Create an App Service Environment](../app-service/environment/creation.md).
6363

64-
* To enable communication from your Standard logic app workflows to a private endpoint on a Premium integration account, you must have an existing Azure virtual network. Both your logic app and virtual network must use the same Azure region. For more information, see [Create a virtual network](../virtual-network/quick-create-portal.md).
64+
* To enable communication from your Standard logic app workflows to a private endpoint on a Premium integration account, you must have an existing Azure virtual network. Both your logic app, virtual network, and integration account must use the same Azure region. Both your logic app and integration account must exist inside the same virtual network. For more information, see [Create a virtual network](../virtual-network/quick-create-portal.md).
6565

6666
* Starting mid-October 2022, new Standard logic app workflows in the Azure portal automatically use Azure Functions v4. Throughout November 2022, existing Standard workflows in the Azure portal are automatically migrating to Azure Functions v4. Unless you deployed your Standard logic apps as NuGet-based projects or pinned your logic apps to a specific bundle version, this upgrade is designed to require no action from you nor have a runtime impact. However, if the exceptions apply to you, or for more information about Azure Functions v4 support, see [Azure Logic Apps Standard now supports Azure Functions v4](https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/azure-logic-apps-standard-now-supports-azure-functions-v4/ba-p/3656072).
6767

@@ -141,8 +141,8 @@ More workflows in your logic app raise the risk of longer load times, which nega
141141

142142
| Enable public access | Behavior |
143143
|----------------------|----------|
144-
| **On** | Your logic app has a public endpoint with an inbound address that's open to the internet and can't access an Azure virtual network. <br><br>To enable communication between a Standard logic app and a private endpoint on a Premium integration account, select this option, but make sure to also set **Enable network injection** to **On**. |
145-
| **Off** | Your logic app has no public endpoint, but has a private endpoint instead for communication within an Azure virtual network, and is isolated to that virtual network. The private endpoint can communicate with endpoints in the virtual network, but only from clients within that network. This configuration also means that logic app traffic can be governed by network security groups or affected by virtual network routes. |
144+
| **On** | Your logic app has a public endpoint with an inbound address that's open to the internet and can't access an Azure virtual network. |
145+
| **Off** | Your logic app has no public endpoint, but has a private endpoint instead for communication within an Azure virtual network, and is isolated within that virtual network. The private endpoint can communicate with endpoints in the virtual network, but only from clients within that network. This configuration also means that logic app traffic can be governed by network security groups or affected by virtual network routes. <br><br>To enable communication between a Standard logic app and a private endpoint on a Premium integration account, select this option, but also make sure to set **Enable network injection** to **On**. |
146146

147147
The following settings control Standard logic app access to endpoints in a virtual network:
148148

articles/logic-apps/enterprise-integration/create-integration-account.md

Lines changed: 5 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.author: estfan
99
ms.reviewer: estfan, divyaswarnkar, azla
1010
ms.topic: how-to
1111
ms.custom: devx-track-azurecli
12-
ms.date: 06/31/2024
12+
ms.date: 06/18/2024
1313
---
1414

1515
# Create and manage integration accounts for B2B workflows in Azure Logic Apps with the Enterprise Integration Pack
@@ -31,16 +31,6 @@ You also need an integration account to electronically exchange B2B messages wit
3131
* [RosettaNet](../logic-apps-enterprise-integration-rosettanet.md)
3232
* [X12](../logic-apps-enterprise-integration-x12.md)
3333

34-
This guide shows how to complete the following tasks:
35-
36-
* Create an integration account.
37-
* Set up storage access for a Premium integration account.
38-
* Link your integration account to a logic app resource.
39-
* Change the pricing tier for your integration account.
40-
* Unlink your integration account from a logic app resource.
41-
* Move an integration account to another Azure resource group or subscription.
42-
* Delete an integration account.
43-
4434
If you're new to creating B2B enterprise integration workflows in Azure Logic Apps, see [B2B enterprise integration workflows with Azure Logic Apps and Enterprise Integration Pack](../logic-apps-enterprise-integration-overview.md).
4535

4636
## Prerequisites
@@ -63,6 +53,8 @@ If you're new to creating B2B enterprise integration workflows in Azure Logic Ap
6353

6454
To create an example Standard logic app workflow, see [Create an example Standard logic app workflow in single-tenant Azure Logic Apps](../create-single-tenant-workflows-azure-portal.md).
6555

56+
* The Premium integration account supports using a [private endpoint](../../private-link/private-endpoint-overview.md) to securely communicate with Standard logic app workflows. To enable this capability, you need to have an Azure virtual network. Your integration account, virtual network, and logic app must all use the same Azure region. Both your integration account and logic app must also exist inside the same virtual network. For more information, see [Create a virtual network](../../virtual-network/quick-create-portal.md) and the steps in this guide to set up your Premium integration account. To set up your Standard logic app, see [Create an example Standard logic app workflow in single-tenant Azure Logic Apps](../create-single-tenant-workflows-azure-portal.md).
57+
6658
## Create integration account
6759

6860
Integration accounts are available in different tiers that [vary in pricing](https://azure.microsoft.com/pricing/details/logic-apps/). Based on the tier you choose, creating an integration account might incur costs. For more information, see [Azure Logic Apps pricing and billing models](../logic-apps-pricing.md#integration-accounts) and [Azure Logic Apps pricing](https://azure.microsoft.com/pricing/details/logic-apps/).
@@ -209,7 +201,8 @@ To create a private connection between your Premium integration account and Azur
209201

210202
### Limitations
211203

212-
Only Standard logic app workflows can use private endpoints on a Premium integration account.
204+
- Only Standard logic app workflows can use private endpoints on a Premium integration account.
205+
213206

214207
### Best practices for private endpoints
215208

0 commit comments

Comments
 (0)