Fix dates

Author: ecfan

articles/logic-apps/logic-apps-deploy-azure-resource-manager-templates.md

@@ -5,14 +5,16 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 08/04/2021
+ms.date: 08/20/2022
 ms.custom: devx-track-azurepowershell, devx-track-azurecli 
 ms.devlang: azurecli
 ---
 
 # Deploy Azure Resource Manager templates for Azure Logic Apps
 
-After you create an Azure Resource Manager template for your logic app, you can deploy your template in these ways:
+[!INCLUDE [logic-apps-sku-consumption](../../includes/logic-apps-sku-consumption.md)]
+
+After you create an Azure Resource Manager template for your Consumption logic app, you can deploy your template in these ways:
 
 * [Azure portal](#portal)
 * [Visual Studio](#visual-studio)

articles/logic-apps/logic-apps-diagnosing-failures.md

@@ -10,6 +10,8 @@ ms.date: 08/20/2022
 
 # Troubleshoot and diagnose workflow failures in Azure Logic Apps
 
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
 Your logic app workflow generates information that can help you diagnose and debug problems in your app. You can diagnose your workflow by reviewing the inputs, outputs, and other information for each step in the workflow using the Azure portal. Or, you can add some steps to a workflow for runtime debugging.
 
 <a name="check-trigger-history"></a>

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

@@ -7,11 +7,13 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 08/30/2022
+ms.date: 08/23/2022
 ---
 
 # Add agreements between partners in integration accounts for workflows in Azure Logic Apps
 
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
 After you add partners to your integration account, specify how partners exchange messages by defining [*agreements*](logic-apps-enterprise-integration-agreements.md) in your integration account. Agreements help organizations communicate seamlessly with each other by defining the specific industry-standard protocol for exchanging messages and by providing the following shared benefits:
 
 * Enable organizations to exchange information by using a well-known format.

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

@@ -7,11 +7,13 @@ author: S-Jindal
 ms.author: shivamjindal
 ms.reviewer: estfan, azla
 ms.topic: reference
-ms.date: 08/30/2022
+ms.date: 08/23/2022
 ---
 
 # MDN acknowledgments for AS2 messages in Azure Logic Apps
 
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
 In Azure Logic Apps, you can create workflows that handle AS2 messages for Electronic Data Interchange (EDI) communication when you use **AS2** operations. In EDI messaging, acknowledgments provide the status from processing an EDI interchange. When receiving an interchange, the [**AS2 Decode** action](logic-apps-enterprise-integration-as2.md#decode) can return a Message Disposition Notification (MDN) or acknowledgment to the sender. An MDN verifies the following items:
 
 * The receiving partner successfully received the original message.

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

@@ -7,11 +7,13 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: reference
-ms.date: 08/30/2022
+ms.date: 08/23/2022
 ---
 
 # Reference for AS2 message settings in agreements for Azure Logic Apps
 
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
 This reference describes the properties that you can set in an AS2 agreement for specifying how to handle messages between [trading partners](logic-apps-enterprise-integration-partners.md). Set up these properties based on your agreement with the partner that exchanges messages with you.
 
 <a name="AS2-incoming-messages"></a>

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

@@ -7,11 +7,13 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 08/30/2022
+ms.date: 08/23/2022
 ---
 
 # Exchange AS2 messages using workflows in Azure Logic Apps
 
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
 To send and receive AS2 messages in workflows that you create using Azure Logic Apps, use the **AS2** connector, which provides triggers and actions that support and manage AS2 (version 1.2) communication.
 
 * If you're working with the **Logic App (Consumption)** resource type and don't need tracking capabilities, use the **AS2 (v2)** connector, rather than the original **AS2** connector, which is being deprecated.

articles/logic-apps/logic-apps-enterprise-integration-b2b-business-continuity.md

@@ -7,11 +7,13 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 08/20/2022
+ms.date: 08/23/2022
 ---
 
 # Set up cross-region disaster recovery for integration accounts in Azure Logic Apps
 
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
 B2B workloads involve money transactions like orders and invoices. 
 During a disaster event, it's critical for a business to quickly 
 recover to meet the business-level SLAs agreed upon with their partners. 

articles/logic-apps/logic-apps-enterprise-integration-b2b-list-errors-solutions.md

@@ -7,12 +7,14 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: conceptual
-ms.date: 08/20/2022
+ms.date: 08/23/2022
 ---
 
 # B2B errors and solutions for Azure Logic Apps
 
-This article helps you troubleshoot errors that might happen in Logic Apps B2B 
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
+This article helps you troubleshoot errors that might happen in Azure Logic Apps B2B 
 scenarios and suggests appropriate actions for correcting those errors.
 
 ## Agreement resolution

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

@@ -7,11 +7,13 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 08/30/2022
+ms.date: 08/23/2022
 ---
 
 # Exchange B2B messages between partners using workflows in Azure Logic Apps
 
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
 When you have an integration account that defines trading partners and agreements, you can create an automated business-to-business (B2B) workflow that exchanges messages between trading partners by using Azure Logic Apps. Your workflow can use connectors that support industry-standard protocols, such as AS2, X12, EDIFACT, and RosettaNet. You can also include operations provided by other [connectors in Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors), such as Office 365 Outlook, SQL Server, and Salesforce.
 
 This article shows how to create an example logic app workflow that can receive HTTP requests by using a **Request** trigger, decode message content by using the **AS2 Decode** and **Decode X12** actions, and return a response by using the **Response** action. The example uses the workflow designer in the Azure portal, but you can follow similar steps for the workflow designer in Visual Studio.

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

@@ -7,11 +7,13 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 08/30/2022
+ms.date: 08/23/2022
 ---
 
 # Add certificates to integration accounts for securing messages in workflows with Azure Logic Apps
 
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
 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:
 
 * Checks the participants' identities in electronic communications.