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-enterprise-integration-certificates.md
+22-22Lines changed: 22 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,36 +1,34 @@
1
1
---
2
-
title: Add certificates to secure B2B messages in workflows
3
-
description: Add certificates to your integration account for securing B2B messages in workflows with Azure Logic Apps and the Enterprise Integration Pack.
2
+
title: Add Certificates to Integration Accounts to Secure B2B Messages in Workflows
3
+
description: Add certificates to your integration account to secure business-to-business (B2B) messages in workflows with Azure Logic Apps and the Enterprise Integration Pack.
4
4
services: logic-apps
5
5
ms.suite: integration
6
6
author: divyaswarnkar
7
7
ms.author: divswa
8
8
ms.reviewers: estfan, azla
9
9
ms.topic: how-to
10
-
ms.date: 04/03/2026
10
+
ms.date: 04/06/2026
11
11
ms.custom: sfi-im6ge-nochange
12
-
Customer intent: As a logic app workflow developer, I want to improve my logic app's security by adding a certificate to my integration account.
12
+
Customer intent: As a logic app workflow developer, I want to improve my logic app's communication security by adding certificates to my integrations account to secure B2B messages in workflows and integration solutions.
13
13
---
14
14
15
-
# Add certificates to integration accounts for securing messages in workflows with Azure Logic Apps
15
+
# Add certificates to integration accounts to secure messages in workflows with Azure Logic Apps
When you need to exchange confidential messages in a logic app business-to-business (B2B) workflow, you can increase the security around this communication by using certificates. A certificate is a digital document that helps secure communication in the following ways:
20
20
21
21
* Checks the participants' identities in electronic communications.
22
-
23
22
* Encrypts message content.
24
-
25
23
* Digitally signs messages.
26
24
27
25
You can use the following certificate types in your workflows:
28
26
29
27
*[Public certificates](https://en.wikipedia.org/wiki/Public_key_certificate), which you must purchase from a public internet [certificate authority (CA)](https://en.wikipedia.org/wiki/Certificate_authority). These certificates don't require any keys.
30
28
31
-
* Private certificates or [*self-signed certificates*](https://en.wikipedia.org/wiki/Self-signed_certificate), which you create and issue yourself. However, these certificates require [private keys in an Azure key vault](#prerequisites).
29
+
* Private certificates or [*self-signed certificates*](https://en.wikipedia.org/wiki/Self-signed_certificate), which you create and issue yourself. These certificates require [private keys in an Azure key vault](#prerequisites).
32
30
33
-
If you're new to logic apps, review[What is Azure Logic Apps](logic-apps-overview.md)? For more information about B2B enterprise integration, review[B2B enterprise integration workflows with Azure Logic Apps and Enterprise Integration Pack](logic-apps-enterprise-integration-overview.md).
31
+
If you're new to logic apps, see[What is Azure Logic Apps](logic-apps-overview.md)? For more information about B2B enterprise integration, see[B2B enterprise integration workflows with Azure Logic Apps and Enterprise Integration Pack](logic-apps-enterprise-integration-overview.md).
34
32
35
33
## Prerequisites
36
34
@@ -46,32 +44,34 @@ If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overvi
46
44
47
45
To create and add certificates for use in **Logic App (Consumption)** workflows, you don't need a logic app resource. However, when you're ready to use those certificates in your workflows, your logic app resource requires a linked integration account that stores those certificates.
48
46
49
-
* 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. However, it must 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 needs to meet other requirements, such as using the same Azure subscription and existing in the same location as your logic app resource.
47
+
* 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. However, it must store other artifacts, such as partners, agreements, and certificates. It also uses 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 needs to use the same Azure subscription and exist in the same location as your logic app resource.
50
48
51
49
* For private certificates, you must meet the following prerequisites:
52
50
53
-
* Add a private key in [Azure Key Vault](/azure/key-vault/general/overview) and have the **Key Name**. For more information, review[Add your private key to Azure Key Vault](/azure/key-vault/certificates/certificate-scenarios#import-a-certificate).
51
+
* Add a private key in [Azure Key Vault](/azure/key-vault/general/overview) and know the key name. For more information, see[Add your private key to Azure Key Vault](/azure/key-vault/certificates/certificate-scenarios#import-a-certificate).
54
52
55
-
* Authorize the Azure Logic Apps service to perform operations on your key vault. To grant access to the Azure Logic Apps service principal, use Azure role-based access control to manage access to your key vault. For more information, see [Provide access to Key Vault keys, certificates, and secrets with an Azure role-based access control](/azure/key-vault/general/rbac-guide).
53
+
* Authorize the Azure Logic Apps service to perform operations on your key vault. To grant access to the Azure Logic Apps service principal, use Azure role-based access control to manage access to your key vault. For more information, see [Provide access to Key Vault keys, certificates, and secrets with Azure role-based access control](/azure/key-vault/general/rbac-guide).
56
54
57
55
> [!NOTE]
58
56
>
59
57
> If you're using access policies with your key vault, consider
60
58
> [migrating to the Azure role-based access control permission model](/azure/key-vault/general/rbac-migration).
61
59
>
62
-
> If you receive the error **"Please authorize logic apps to perform operations on key vault by granting access for the logic apps service principal '7cd684f4-8a78-49b0-91ec-6a35d38739ba' for 'list', 'get', 'decrypt' and 'sign' operations."**, your certificate might not have the **Key Usage** property set to **Data Encipherment**. If so, you might need to recreate the certificate with the **Key Usage** property set to **Data Encipherment**. To check your certificate, open the certificate, select the **Details** tab, and review the **Key Usage** property.
60
+
> If you receive the error **"Please authorize logic apps to perform operations on key vault by granting access for the logic apps service principal '7cd684f4-8a78-49b0-91ec-6a35d38739ba' for 'list', 'get', 'decrypt' and 'sign' operations."**, your certificate might not have the **Key Usage** property set to **Data Encipherment**. If so, you might need to recreate the certificate and set the **Key Usage** property to **Data Encipherment**.
61
+
>
62
+
> To check your certificate. open the certificate, select the **Details** tab, and review the **Key Usage** property.
63
63
64
-
*[Add the corresponding public certificate](#add-public-certificate) to your key vault. This certificate appears in your [agreement's **Send** and **Receive** settings for signing and encrypting messages](logic-apps-enterprise-integration-agreements.md). For example, review[Reference for AS2 messages settings in Azure Logic Apps](logic-apps-enterprise-integration-as2-message-settings.md).
64
+
*[Add the corresponding public certificate](#add-public-certificate) to your key vault. This certificate appears in your [agreement's **Send** and **Receive** settings for signing and encrypting messages](logic-apps-enterprise-integration-agreements.md). For more information, see[Reference for AS2 messages settings in Azure Logic Apps](logic-apps-enterprise-integration-as2-message-settings.md).
65
65
66
-
* At least two [trading partners](logic-apps-enterprise-integration-partners.md) and an [agreement between those partners](logic-apps-enterprise-integration-agreements.md) in your integration account. An agreement requires a host partner and a guest partner. Also, an agreement requires that both partners use the same or compatible *business identity* qualifier that's appropriate for an AS2, X12, EDIFACT, or RosettaNet agreement.
66
+
* At least two [trading partners](logic-apps-enterprise-integration-partners.md) and an [agreement between those partners](logic-apps-enterprise-integration-agreements.md) in your integration account. An agreement requires a host partner and a guest partner. It also requires that both partners use the same or a compatible *business identity* qualifier that's appropriate for an AS2, X12, EDIFACT, or RosettaNet agreement.
67
67
68
68
* Optionally, the logic app resource and workflow where you want to use the certificate. The workflow requires any trigger that starts your logic app's workflow. For more information, see [Quickstart: Create an example Consumption logic app workflow](quickstart-create-example-consumption-workflow.md).
69
69
70
70
<aname="add-public-certificate"></a>
71
71
72
72
## Use a public certificate
73
73
74
-
To use a *public certificate* in your workflow, you first add the certificate to your integration account.
74
+
To use a *public certificate* in your workflow, you first add the certificate to your integration account:
75
75
76
76
1. In the [Azure portal](https://portal.azure.com) search box, enter **integration accounts**, and then select **Integration accounts**.
77
77
@@ -101,7 +101,7 @@ To use a *public certificate* in your workflow, you first add the certificate to
101
101
102
102
## Use a private certificate
103
103
104
-
To use a *private certificate* in your workflow, you must meet the [prerequisites for private keys](#prerequisites), and add a public certificate to your integration account.
104
+
To use a *private certificate* in your workflow, you must meet the [prerequisites for private keys](#prerequisites), and add a public certificate to your integration account:
105
105
106
106
1. In the [Azure portal](https://portal.azure.com) search box, enter **integration accounts**, and then select **Integration accounts**.
107
107
@@ -130,9 +130,9 @@ To use a *private certificate* in your workflow, you must meet the [prerequisite
130
130
131
131
:::image type="content" source="media/logic-apps-enterprise-integration-certificates/new-private-certificate.png" alt-text="Screenshot that shows the Azure portal and integration account with the private certificate in the Certificates list.":::
0 commit comments