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/logic-apps-batch-process-send-receive-messages.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,17 @@
1
1
---
2
-
title: Batch process messages as a group
3
-
description: Send and receive messages in groups between your workflows by using batch processing in Azure Logic Apps.
4
-
services: logic-apps
2
+
title: Batch Process Messages in Groups
3
+
description: Exchange messages between workflows in groups with batch processing in Azure Logic Apps.
4
+
services: azure-logic-apps
5
5
ms.suite: integration
6
-
ms.reviewer: estfan, azla
6
+
ms.reviewers: estfan, azla
7
7
ms.topic: how-to
8
-
ms.date: 02/05/2025
8
+
ms.update-cycle: 1095-days
9
+
ms.date: 03/13/2026
9
10
ms.custom: sfi-image-nochange
11
+
# Customer intent: As an integration developer who works with Azure Logic Apps, I want to exchange groups of messages between workflows by setting up batch processing.
10
12
---
11
13
12
-
# Send, receive, and batch process messages in Azure Logic Apps
14
+
# Batch process and exchange messages in groups between workflows in Azure Logic Apps
@@ -27,7 +29,7 @@ Your batch receiver and batch sender need to share the same Azure subscription *
27
29
28
30
## Prerequisites
29
31
30
-
* An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
32
+
* An Azure account and subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
31
33
32
34
* An email account with any [email provider supported by Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors)
Copy file name to clipboardExpand all lines: articles/logic-apps/logic-apps-enterprise-integration-partners.md
+16-13Lines changed: 16 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,21 @@
1
1
---
2
-
title: Define trading partners for workflows
3
-
description: Add trading partners to your integration account for workflows in Azure Logic Apps using the Enterprise Integration Pack.
4
-
services: logic-apps
2
+
title: Define Trading Partners for B2B Workflows
3
+
description: Add trading partners to your integration account to build B2B workflows in Azure Logic Apps.
4
+
services: azure-logic-apps
5
5
ms.suite: integration
6
6
author: divyaswarnkar
7
7
ms.author: divswa
8
-
ms.reviewer: estfan, azla
8
+
ms.reviewers: estfan, azla
9
9
ms.topic: how-to
10
-
ms.date: 02/20/2025
10
+
ms.update-cycle: 1095-days
11
+
ms.date: 03/13/2026
12
+
# Customer intent: As a B2B integration developer who works with Azure Logic Apps, I want to define trading partners who exchange messages in my workflows as artifacts in an integration account.
11
13
---
12
14
13
15
# Add trading partners to integration accounts for workflows in Azure Logic Apps
To represent your organization and others in business-to-business (B2B) enterprise integration workflows, create a *trading partner* in your [integration account](logic-apps-enterprise-integration-create-integration-account.md) to represent each participant in a business relationship. Partners are business entities that participate in B2B transactions and exchange messages with each other.
16
20
17
21
> [!IMPORTANT]
@@ -27,17 +31,18 @@ If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overvi
27
31
28
32
* An Azure account and subscription. If you don't have a subscription yet, [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
29
33
30
-
* An [integration account resource](logic-apps-enterprise-integration-create-integration-account.md) where you define and store artifacts, such as trading partners, agreements, certificates, and so on, for use in your enterprise integration and B2B workflows. This resource has to meet the following requirements:
34
+
* An [integration account resource](logic-apps-enterprise-integration-create-integration-account.md) where you define and store artifacts, such as trading partners, agreements, certificates, and so on, for use in your enterprise integration and B2B workflows.
31
35
32
-
* Is associated with the same Azure subscription as your logic app resource.
36
+
This resource has the following requirements:
33
37
34
-
*Exists in the same location or Azure region as your logic app resource.
38
+
*Use the same Azure subscription and location or Azure region as your logic app resource.
35
39
36
-
* If you're using the [**Logic App (Consumption)** resource type](logic-apps-overview.md#resource-environment-differences), your integration account requires a [link to your logic app resource](logic-apps-enterprise-integration-create-integration-account.md#link-account) before you can use artifacts in your workflow.
40
+
* If you have a [Consumption logic app resource](logic-apps-overview.md#resource-environment-differences), your integration account requires a [link to your logic app resource](logic-apps-enterprise-integration-create-integration-account.md#link-account) before you can use artifacts in your workflow.
37
41
38
-
* If you're using the [**Logic App (Standard)** resource type](logic-apps-overview.md#resource-environment-differences), your integration account doesn't need a link to your logic app resource but is still required to store other artifacts, such as partners, agreements, and certificates, along with using the [AS2](logic-apps-enterprise-integration-as2.md), [X12](logic-apps-enterprise-integration-x12.md), and [EDIFACT](logic-apps-enterprise-integration-edifact.md) operations. Your integration account still has to meet other requirements, such as using the same Azure subscription and existing in the same location as your logic app resource.
42
+
* If you have a [Standard logic app resource](logic-apps-overview.md#resource-environment-differences), your integration account doesn't need a link to your logic app resource but is still required to store other artifacts, such as partners, agreements, and certificates, along with using the [AS2](logic-apps-enterprise-integration-as2.md), [X12](logic-apps-enterprise-integration-x12.md), and [EDIFACT](logic-apps-enterprise-integration-edifact.md) operations. Your integration account still has to meet other requirements, such as using the same Azure subscription and existing in the same location as your logic app resource.
39
43
40
44
> [!NOTE]
45
+
>
41
46
> Currently, only the **Logic App (Consumption)** resource type supports [RosettaNet](logic-apps-enterprise-integration-rosettanet.md) operations.
42
47
> The **Logic App (Standard)** resource type doesn't include [RosettaNet](logic-apps-enterprise-integration-rosettanet.md) operations.
43
48
@@ -60,7 +65,6 @@ If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overvi
60
65
|**Name**| Yes | The partner's name |
61
66
|**Qualifier**| Yes | The authenticating body that provides unique business identities to organizations, for example, **D-U-N-S (Dun & Bradstreet)**. <p>Partners can opt for a mutually defined business identity. For these scenarios, select **Mutually Defined** for EDIFACT or **Mutually Defined (X12)** for X12. <p>For RosettaNet, select only **DUNS**, which is the standard. <p>**Important**: For partners in your integration account to participate in an agreement and exchange messages with each other, they have to use the same or compatible qualifier. |
62
67
|**Value**| Yes | A value that identifies the documents that your logic apps receive. <p>For partners that use RosettaNet, this value must be a nine-digit number that corresponds to the DUNS number. You can provide more information for RosettaNet partners, such as their classification and contact information, by creating the partners first and then [editing their definitions afterwards](#edit-partner). |
63
-
||||
64
68
65
69
1. When you're done, select **OK**.
66
70
@@ -86,7 +90,6 @@ If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overvi
86
90
|**Email**| No | The partner's email address |
87
91
|**Fax**| No | The partner's fax number |
88
92
|**Telephone**| No | The partner's phone number |
89
-
||||
90
93
91
94
1. When you're done, select **OK**.
92
95
@@ -102,6 +105,6 @@ If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overvi
102
105
103
106
1. To confirm that you want to delete the partner, select **Yes**.
104
107
105
-
## Next steps
108
+
## Related content
106
109
107
110
*[Add agreements between partners](logic-apps-enterprise-integration-agreements.md)
0 commit comments