Merge pull request #105561 from ecfan/ise-message-limits

Clarify ISE connector message limits

Author: American-Dipper

articles/connectors/connectors-create-api-azure-event-hubs.md

@@ -226,10 +226,12 @@ or [Add Event Hubs action](#add-action).
 
 ## Connector reference
 
-For technical details, such as triggers, actions, and limits, 
-as described by the connector's OpenAPI (formerly Swagger) file, 
-see the [connector's reference page](/connectors/eventhubs/).
+For technical details, such as triggers, actions, and limits, as described by the connector's Swagger file, see the [connector's reference page](https://docs.microsoft.com/connectors/eventhubs/).
+
+> [!NOTE]
+> For logic apps in an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), 
+> this connector's ISE-labeled version uses the [ISE message limits](../logic-apps/logic-apps-limits-and-config.md#message-size-limits) instead.
 
 ## Next steps
 
-Learn about other [Logic Apps connectors](../connectors/apis-list.md)
+* Learn about other [Logic Apps connectors](../connectors/apis-list.md)

articles/connectors/connectors-create-api-azureblobstorage.md

@@ -134,7 +134,11 @@ This example only gets the contents for a blob. To view the contents, add anothe
 
 ## Connector reference
 
-For technical details, such as triggers, actions, and limits, as described by the connector's Open API (formerly Swagger) file, see the [connector's reference page](https://docs.microsoft.com/connectors/azureblobconnector/).
+For more technical details about this connector, such as triggers, actions, and limits as described by the connector's Swagger file, see the [connector's reference page](https://docs.microsoft.com/connectors/azureblobconnector/).
+
+> [!NOTE]
+> For logic apps in an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), 
+> this connector's ISE-labeled version uses the [ISE message limits](../logic-apps/logic-apps-limits-and-config.md#message-size-limits) instead.
 
 <a name="storage-firewalls"></a>
 

articles/connectors/connectors-create-api-db2.md

@@ -429,9 +429,11 @@ Expand the **Delete row** action.
 
 ## Connector reference
 
-For technical details, such as triggers, actions, and limits, 
-as described by the connector's OpenAPI (formerly Swagger) file, 
-see the [connector's reference page](/connectors/db2/).
+For more technical details about this connector, such as triggers, actions, and limits as described by the connector's Swagger file, see the [connector's reference page](https://docs.microsoft.com/connectors/db2/).
+
+> [!NOTE]
+> For logic apps in an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), 
+> this connector's ISE-labeled version uses the [ISE message limits](../logic-apps/logic-apps-limits-and-config.md#message-size-limits) instead.
 
 ## Next steps
 

articles/connectors/connectors-create-api-ftp.md

@@ -166,7 +166,11 @@ To check that your workflow returns the content that you expect, add another act
 
 ## Connector reference
 
-For technical details about triggers, actions, and limits, which are described by the connector's OpenAPI (formerly Swagger) description, review the [connector's reference page](/connectors/ftpconnector/).
+For more technical details about this connector, such as triggers, actions, and limits as described by the connector's Swagger file, see the [connector's reference page](https://docs.microsoft.com/connectors/ftpconnector/).
+
+> [!NOTE]
+> For logic apps in an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), 
+> this connector's ISE-labeled version uses the [ISE message limits](../logic-apps/logic-apps-limits-and-config.md#message-size-limits) instead.
 
 ## Next steps
 

articles/connectors/connectors-create-api-mq.md

@@ -129,9 +129,11 @@ When you add the **Send messages** action, the first previously configured conne
 
 ## Connector reference
 
-For technical details about actions and limits, which are 
-described by the connector's OpenAPI (formerly Swagger) description, 
-review the connector's [reference page](/connectors/mq/).
+For more technical details about this connector, such as triggers, actions, and limits as described by the connector's Swagger file, see the [connector's reference page](https://docs.microsoft.com/connectors/mq/).
+
+> [!NOTE]
+> For logic apps in an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), 
+> this connector's ISE-labeled version uses the [ISE message limits](../logic-apps/logic-apps-limits-and-config.md#message-size-limits) instead.
 
 ## Next steps
 

articles/connectors/connectors-create-api-smtp.md

@@ -79,14 +79,11 @@ Under the actions list, select the action you want.
 
 ## Connector reference
 
-For technical details about triggers, actions, and limits, which are 
-described by the connector's OpenAPI (formerly Swagger) description, 
-review the connector's [reference page](/connectors/smtpconnector/).
+For more technical details about this connector, such as triggers, actions, and limits as described by the connector's Swagger file, see the [connector's reference page](https://docs.microsoft.com/connectors/smtpconnector/).
 
-## Get support
-
-* For questions, visit the [Azure Logic Apps forum](https://social.msdn.microsoft.com/Forums/en-US/home?forum=azurelogicapps).
-* To submit or vote on feature ideas, visit the [Logic Apps user feedback site](https://aka.ms/logicapps-wish).
+> [!NOTE]
+> For logic apps in an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), 
+> this connector's ISE-labeled version uses the [ISE message limits](../logic-apps/logic-apps-limits-and-config.md#message-size-limits) instead.
 
 ## Next steps
 

articles/connectors/connectors-run-3270-apps-ibm-mainframe-create-api-3270.md

@@ -629,9 +629,11 @@ and choose **Create**.
 
 ## Connector reference
 
-For technical details about triggers, actions, and limits, which are described 
-by the connector's OpenAPI (formerly Swagger) description, review the 
-[connector's reference page](/connectors/si3270/).
+For more technical details about this connector, such as triggers, actions, and limits as described by the connector's Swagger file, see the [connector's reference page](https://docs.microsoft.com/connectors/si3270/).
+
+> [!NOTE]
+> For logic apps in an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), 
+> this connector's ISE-labeled version uses the [ISE message limits](../logic-apps/logic-apps-limits-and-config.md#message-size-limits) instead.
 
 ## Next steps
 

articles/connectors/connectors-sftp-ssh.md

@@ -183,7 +183,11 @@ This action gets the content from a file on an SFTP server. So for example, you
 
 ## Connector reference
 
-For technical details about triggers, actions, and limits, which are described by the connector's OpenAPI (formerly Swagger) description, review the connector's [reference page](/connectors/sftpconnector/).
+For more technical details about this connector, such as triggers, actions, and limits as described by the connector's Swagger file, see the [connector's reference page](https://docs.microsoft.com/connectors/sftpwithssh/).
+
+> [!NOTE]
+> For logic apps in an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), 
+> this connector's ISE-labeled version uses the [ISE message limits](../logic-apps/logic-apps-limits-and-config.md#message-size-limits) instead.
 
 ## Next steps
 

articles/logic-apps/logic-apps-enterprise-integration-as2.md

@@ -7,11 +7,18 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: jonfan, estfan, logicappspm
 ms.topic: article
-ms.date: 08/22/2019
+ms.date: 02/27/2020
 ---
 
 # Exchange AS2 messages for B2B enterprise integration in Azure Logic Apps with Enterprise Integration Pack
 
+> [!IMPORTANT]
+> The original AS2 connector is being deprecated, so make sure that you use the **AS2 (v2)** connector instead. 
+> This version provides the same capabilities as the original version, is native to the Logic Apps runtime, and provides 
+> significant performance improvements in terms of throughput and message size. Also, the native v2 connector doesn't 
+> require that you create a connection to your integration account. Instead, as described in the prerequisites, 
+> make sure that you link your integration account to the logic app where you plan to use the connector.
+
 To work with AS2 messages in Azure Logic Apps, you can use the AS2 connector, which provides triggers and actions for managing AS2 communication. For example, to establish security and reliability when transmitting messages, you can use these actions:
 
 * [**AS2 Encode** action](#encode) for providing encryption, digital signing, and acknowledgments through Message Disposition Notifications (MDN), which help support non-repudiation. For example, this action applies AS2/HTTP headers and performs these tasks when configured:
@@ -41,13 +48,6 @@ To work with AS2 messages in Azure Logic Apps, you can use the AS2 connector, wh
 
 This article shows how to add the AS2 encoding and decoding actions to an existing logic app.
 
-> [!IMPORTANT]
-> The original AS2 connector is going to be deprecated, so make sure that you use the **AS2 (v2)** connector instead. 
-> This version provides the same capabilities as the original version, is native to the Logic Apps runtime, and provides 
-> significant performance improvements in terms of throughput and message size. Also, the native v2 connector doesn't 
-> require that you create a connection to your integration account. Instead, as described in the prerequisites, 
-> make sure that you link your integration account to the logic app where you plan to use the connector.
-
 ## Prerequisites
 
 * An Azure subscription. If you don't have an Azure subscription yet, [sign up for a free Azure account](https://azure.microsoft.com/free/).
@@ -62,9 +62,9 @@ This article shows how to add the AS2 encoding and decoding actions to an existi
 
 * If you use [Azure Key Vault](../key-vault/key-vault-overview.md) for certificate management, check that your vault keys permit the **Encrypt** and **Decrypt** operations. Otherwise, the encoding and decoding actions fail.
 
-  In the Azure portal, go to your key vault, view your vault key's **Permitted operations**, and confirm that the **Encrypt** and **Decrypt** operations are selected.
+  In the Azure portal, go to the key in your key vault, review your key's **Permitted operations**, and confirm that the **Encrypt** and **Decrypt** operations are selected, for example:
 
-  ![Check vault key operations](media/logic-apps-enterprise-integration-as2/vault-key-permitted-operations.png)
+  ![Check vault key operations](media/logic-apps-enterprise-integration-as2/key-vault-permitted-operations.png)
 
 <a name="encode"></a>
 
@@ -91,6 +91,10 @@ This article shows how to add the AS2 encoding and decoding actions to an existi
 
    ![Message encoding properties](./media/logic-apps-enterprise-integration-as2/as2-message-encoding-details.png)
 
+> [!TIP]
+> If you experience problems when sending signed or encrypted messages, consider trying different SHA256 algorithm formats. 
+> The AS2 specification doesn't provide any information about SHA256 formats, so each provider uses their own implementation or format.
+
 <a name="decode"></a>
 
 ## Decode AS2 messages
@@ -115,8 +119,12 @@ To try deploying a fully operational logic app and sample AS2 scenario, see the
 
 ## Connector reference
 
-For technical details, such as triggers, actions, and limits, as described by the connector's OpenAPI (formerly Swagger) file, see the [connector's reference page](/connectors/as2/).
+For more technical details about this connector, such as actions and limits as described by the connector's Swagger file, see the [connector's reference page](https://docs.microsoft.com/connectors/as2/). 
+
+> [!NOTE]
+> For logic apps in an [integration service environment (ISE)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), 
+> this connector's original ISE-labeled version uses the [ISE message limits](../logic-apps/logic-apps-limits-and-config.md#message-size-limits) instead.
 
 ## Next steps
 
-Learn more about the [Enterprise Integration Pack](logic-apps-enterprise-integration-overview.md)
+* Learn about other [Logic Apps connectors](../connectors/apis-list.md)