Update dates and metadata

Author: ecfan

articles/logic-apps/connectors/sap-create-example-scenario-workflows.md

@@ -1,22 +1,23 @@
 ---
-title: Create common SAP workflows
-description: Build workflows for common SAP scenarios in Azure Logic Apps.
-services: logic-apps
+title: Create Common SAP Integration Workflows
+description: Build integration workflows for common SAP integration scenarios by using workflows in Azure Logic Apps.
+services: azure-logic-apps
 ms.suite: integration
 author: daviburg
 ms.author: daviburg
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 02/12/2025
+ms.update-cycle: 1095-days
+ms.date: 03/13/2026
 ms.custom: sfi-ropc-nochange
-#As an integration solution developer, I want to learn how I can build automated workflows that perform tasks with SAP resources.
+#Customer intent: As an SAP integration solution developer who works with Azure Logic Apps, I want to create automation and integration workflows that perform tasks with SAP resources.
 ---
 
 # Create workflows for common SAP integration scenarios in Azure Logic Apps
 
-[!INCLUDE [logic-apps-sku-consumption-standard](../../../includes/logic-apps-sku-consumption-standard.md)]
+[!INCLUDE [logic-apps-sku-consumption-standard](../includes/logic-apps-sku-consumption-standard.md)]
 
-This how-to guide shows how to create example logic app workflows for some common SAP integration scenarios using Azure Logic Apps and the SAP connector.
+This guide shows how to create example logic app workflows for some common SAP integration scenarios using Azure Logic Apps and the SAP connector.
 
 Both Standard and Consumption logic app workflows offer the SAP *managed* connector that's hosted and run in multitenant Azure. Standard workflows also offer the SAP *built-in service provider* connector that's hosted and run in single-tenant Azure Logic Apps. For more information, see [Connector technical reference](sap.md#connector-technical-reference).
 

articles/logic-apps/healthy-unhealthy-resource.md

@@ -1,25 +1,33 @@
 ---
-title: Set up logging to monitor logic apps in Azure Security Center
-description: Monitor health for Azure Logic Apps resources in Azure Security Center by setting up diagnostic logging. 
-services: logic-apps
+title: Monitor Resource Health with Defender for Cloud
+description: Monitor resource health for Azure Logic Apps by setting up diagnostic logging with Microsoft Defender for Cloud in Azure Security Center.
+services: azure-logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 02/20/2025
+ms.update-cycle: 1095-days
+ms.date: 03/13/2026
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to set up resource health monitoring and diagnostic logging with Microsoft Defender for Cloud in Azure Security Center.
 ---
 
-# Set up logging to monitor logic apps in Microsoft Defender for Cloud
+# Monitor resource health for Azure Logic Apps by setting up logging in Azure Security Center
 
-When you monitor your Azure Logic Apps resources in [Microsoft Azure Security Center](../security-center/security-center-introduction.md), you can [review whether your logic apps are following the default policies](#view-logic-apps-health-status). Azure shows the health status for an Azure Logic Apps resource after you enable logging and correctly set up the logs' destination. This article explains how to configure diagnostic logging and make sure that all your logic apps are healthy resources.
+When you monitor your Azure Logic Apps resources by using with Microsoft Defender for Cloud in Microsoft Azure Security Center, you can check whether your logic apps follow default policies. Azure shows the health status for a resource in Azure Logic Apps after you enable logging and correctly set up the logs' destination.
+
+This guide shows how to configure diagnostic logging and make sure that all your logic apps are healthy resources.
+
+For more information, see:
+
+- [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)
+- [Microsoft Azure Security Center](../security-center/security-center-introduction.md)
 
 > [!TIP]
-> 
-> To find the current status for the Azure Logic Apps service, review the
-> [Azure status page](https://azure.status.microsoft/), which lists the status for different products and services in each available region.
+>
+> To find the current status for the Azure Logic Apps service, visit the [Azure status page](https://azure.status.microsoft/). This page lists the statuses for different products and services in each available region.
 
 ## Prerequisites
 
-* An Azure subscription. If you don't have a subscription, [create a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+* An Azure subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
 * Existing logic apps with [diagnostic logging enabled](#enable-diagnostic-logging).
 
@@ -30,28 +38,31 @@ When you monitor your Azure Logic Apps resources in [Microsoft Azure Security Ce
 Before you can view the resource health status for your logic apps, you must first [set up diagnostic logging](monitor-workflows-collect-diagnostic-data.md). If you already have a Log Analytics workspace, you can enable logging either when you create your logic app or on existing logic apps.
 
 > [!TIP]
+>
 > The default recommendation is to enable diagnostic logs for Azure Logic Apps. However, you control this setting for your logic apps. When you enable diagnostic logs for your logic apps, you can use the information to help analyze security incidents.
 
 ### Check diagnostic logging setting
 
 If you're not sure whether your logic apps have diagnostic logging enabled, you can check in Defender for Cloud:
 
-1. Sign in to the [Azure portal](https://portal.azure.com).
-1. In the search bar, enter and select **Defender for Cloud**.
+1. In the [Azure portal](https://portal.azure.com) search bar, enter and select **Defender for Cloud**.
 1. On the workload protection dashboard menu, under **General**, select **Recommendations**.
-1. In the table of security suggestions, find and select **Enable auditing and logging** > **Diagnostic logs in Logic Apps should be enabled** in the table of security controls.
-1. On the recommendation page, expand the **Remediation steps** section and review the options. You can enable Azure Logic Apps diagnostics by selecting the **Quick Fix!** button, or by following the manual remediation instructions.
+1. In the table of security suggestions, find the table of security controls.
+1. Find and select **Enable auditing and logging** > **Diagnostic logs in Logic Apps should be enabled**.
+1. On the recommendation page, expand the **Remediation steps** section and review the options.
+1. Enable Azure Logic Apps diagnostics by selecting the **Quick Fix!** button, or by following the manual remediation instructions.
 
 ## View logic apps' health status
 
-After you've [enabled diagnostic logging](#enable-diagnostic-logging), you can see the health status of your logic apps in Defender for Cloud.
+After you [enable diagnostic logging](#enable-diagnostic-logging), you can see the health status of your logic apps in Defender for Cloud.
 
-1. Sign in to the [Azure portal](https://portal.azure.com).
-1. In the search bar, enter and select **Defender for Cloud**.
+1. In the [Azure portal](https://portal.azure.com) search bar, enter and select **Defender for Cloud**.
 1. On the workload protection dashboard menu,  under **General**, select **Inventory**.
-1. On the inventory page, filter your assets list to show only Azure Logic Apps resources. In the page menu, select **Resource types** > **logic apps**.
+1. On the inventory page, filter your assets list to show only Azure Logic Apps resources.
+1. From the page menu, select **Resource types** > **logic apps**.
 
    The **Unhealthy Resources** counter shows the number of logic apps that Defender for Cloud considers unhealthy.
+
 1.  In the list of logic apps resources, review the **Recommendations** column. To review the health details for a specific logic app, select a resource name, or select the ellipses button (**...**) > **View resource**.
 1.  To remediate any potential resource health issues, follow the steps listed for your logic apps.
 
@@ -123,3 +134,8 @@ If you use a storage account as the destination for your Azure Logic Apps diagno
     }
 ]
 ```
+
+# Related content
+
+- [Monitor Standard workflow health with Health Check](monitor-health-standard-workflows.md)
+- [Monitor workflows in Azure Logic Apps](monitor-logic-apps-overview.md)

articles/logic-apps/logic-apps-batch-process-send-receive-messages.md

@@ -133,7 +133,7 @@ Now create one or more batch sender logic app workflows that send messages to th
 
 * Make sure that you previously [created and deployed your batch receiver](#batch-receiver) so when you create your batch sender, you can select the existing batch receiver as the destination batch. While batch receivers don't need to know anything about batch senders, batch senders must know where to send messages.
 
-* Make sure that your batch receiver and batch sender share the same Azure region *and* Azure subscription. If they don't, you can't select the batch receiver when you create the batch sender because they're not visible to each other.
+* Make sure that your batch receiver and batch sender both share the same Azure region *and* Azure subscription. If they don't, you can't select the batch receiver when you create the batch sender because they're not visible to each other.
 
 1. Create another logic app resource and workflow named **BatchSender**.
 

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

@@ -1,13 +1,15 @@
 ---
-title: Define agreements between partners in workflows
-description: Add agreements between partners in your integration account for workflows in Azure Logic Apps using the Enterprise Integration Pack.
-services: logic-apps
+title: Define Agreements Between Partners in B2B Workflows
+description: Add agreements between partners to your integration account for B2B workflows in Azure Logic Apps.
+services: azure-logic-apps
 ms.suite: integration
 author: divyaswarnkar
 ms.author: divswa
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 02/20/2025
+ms.update-cycle: 1095-days
+ms.date: 03/13/2026
+# Customer intent: As a B2B integration developer who works with Azure Logic Apps, I want to define agreements between the trading partners as artifacts in an integration account.
 ---
 
 # Add agreements between partners in integration accounts for workflows in Azure Logic Apps
@@ -24,34 +26,32 @@ After you add partners to your integration account, specify how partners exchang
 
 An agreement requires a *host partner*, which is always your organization, and a *guest partner*, which is the organization that exchanges messages with your organization. The guest partner can be another company, or even a department in your own organization. Using this agreement, you specify how to handle inbound and outbound messages from the host partner's perspective.
 
-This article shows how to create and manage an agreement, which you can then use to exchange B2B messages with another partner by using the AS2, X12, EDIFACT, or RosettaNet operations.
+This guide shows how to create and manage an agreement, which you can then use to exchange B2B messages with another partner by using the AS2, X12, EDIFACT, or RosettaNet operations.
 
-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).
+For more information, see:
 
-## Prerequisites
+- [B2B enterprise integration workflows with Azure Logic Apps](logic-apps-enterprise-integration-overview.md)
+- [Create and manage integration accounts for B2B workflows](enterprise-integration/create-integration-account.md)
+- [Add agreements between partners](logic-apps-enterprise-integration-agreements.md)
 
-* 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).
+## Prerequisites
 
-* 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:
+* An Azure account and subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
-  * Is associated with the same Azure subscription as your logic app resource.
+* 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.
 
-  * Exists in the same location or Azure region as your logic app resource.
+  This resource needs to meet the following requirements:
 
-  * 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.
+  * Use the same Azure subscription and location or Azure region as your logic app resource.
 
-  * 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.
+  * 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.
 
-  > [!NOTE]
-  > Currently, only the **Logic App (Consumption)** resource type supports [RosettaNet](logic-apps-enterprise-integration-rosettanet.md) operations. 
-  > The **Logic App (Standard)** resource type doesn't include [RosettaNet](logic-apps-enterprise-integration-rosettanet.md) operations.
+  * 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.
 
 * At least two [trading partners](logic-apps-enterprise-integration-partners.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.
 
 * Optionally, the logic app resource and workflow where you want to use the agreement to exchange messages. The workflow requires any trigger that starts your logic app's workflow.
 
-If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overview.md) and [Create an example Consumption logic app workflow](quickstart-create-example-consumption-workflow.md).
-
 ## Add an agreement
 
 1. In the [Azure portal](https://portal.azure.com) search box, enter `integration accounts`, and select **Integration accounts**.

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

@@ -1,14 +1,16 @@
 ---
-title: Disaster recovery for integration accounts
-description: Set up integration accounts and B2B artifacts for cross-region disaster recovery in Azure Logic Apps.
+title: Disaster Recovery for Integration Accounts
+description: Set up cross-region disaster recovery for integration accounts and B2B artifacts in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
 author: divyaswarnkar
 ms.author: divswa
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 02/20/2025
+ms.update-cycle: 1095-days
+ms.date: 03/13/2026
 ms.custom: sfi-image-nochange
+# Customer intent: As a B2B integration developer who works with Azure Logic Apps, I want to set up cross-region disaster recovery for my integration accounts and B2B artifacts.
 ---
 
 # Set up cross-region disaster recovery for integration accounts in Azure Logic Apps
@@ -310,6 +312,7 @@ and choose **Create**.
    Based on the time interval, the trigger polls the primary region 
    table and pulls the new records. The action updates them to the 
    secondary region integration account. 
+
    If there are no updates, the trigger status appears as **Skipped**.  
 
    ![Primary region table](./media/logic-apps-enterprise-integration-b2b-business-continuity/as2messageid8.png)
@@ -319,6 +322,6 @@ replicates from the primary region to the secondary region.
 During a disaster event, when the primary region is not available, 
 direct traffic to the secondary region for business continuity. 
 
-## Next steps
+## Related content
 
 [Monitor B2B messages with Azure Monitor logs](../logic-apps/monitor-b2b-messages-log-analytics.md)