Merge pull request #313106 from ecfan/freshness

[Azure Logic Apps] Freshness - Update dates and metadata

Author: JillGrant615

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

@@ -1,24 +1,25 @@
 ---
-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).
+Both Standard and Consumption logic app workflows offer the SAP *managed* connector hosted and run in multitenant Azure. Standard workflows also offer the SAP *built-in service provider* connector hosted and run in single-tenant Azure Logic Apps. For more information, see [Connector technical reference](sap.md#connector-technical-reference).
 
 ## Prerequisites
 
@@ -77,9 +78,9 @@ Based on whether you have a Consumption workflow in multitenant Azure Logic Apps
    | **ProgramId** | Yes | The registration gateway program ID for the SAP RFC server. <br><br>**Note**: This value is case-sensitive. Make sure that you consistently use the same case format for the **Program ID** value when you configure your logic app workflow and SAP server. Otherwise, when you attempt to send an IDoc to SAP, the tRFC Monitor (T-Code SM58) might show the following errors (links require SAP login): <br><br>- [**Function IDOC_INBOUND_ASYNCHRONOUS not found** (2399329)](https://launchpad.support.sap.com/#/notes/2399329)<br>- [**Non-ABAP RFC client (partner type) not supported** (353597)](https://launchpad.support.sap.com/#/notes/353597) |
    | **DegreeOfParallelism** | No | The number of calls to process in parallel. To add this parameter and change the value, from the **Advanced parameters** list, select **DegreeOfParallelism**, and enter the new value. |
    | **SapActions** | No | Filter the messages that you receive from your SAP server based on a [list of SAP actions](#filter-with-sap-actions). To add this parameter, from the **Advanced parameters** list, select **SapActions**. In the new **SapActions** section, for the **SapActions - 1** parameter, use the file picker to select an SAP action or manually specify an action. For more information about the SAP action, see [Message schemas for IDoc operations](/biztalk/adapters-and-accelerators/adapter-sap/message-schemas-for-idoc-operations). |
-   | **IDoc Format** | No | The format to use for receiving IDocs. To add this parameter, from the **Advanced parameters** list, select **IDoc Format**. <br><br>- To receive IDocs as SAP plain XML, from the **IDoc Format** list, select **SapPlainXml**. <br><br>- To receive IDocs as a flat file, from the **IDoc Format** list, select **FlatFile**. <br><br>- **Note**: If you also use the [Flat File Decode action](../logic-apps-enterprise-integration-flatfile.md) in your workflow, in your flat file schema, you have to use the **early_terminate_optional_fields** property and set the value to **true**. This requirement is necessary because the flat file IDoc data record that's sent by SAP on the tRFC call named `IDOC_INBOUND_ASYNCHRONOUS` isn't padded to the full SDATA field length. Azure Logic Apps provides the flat file IDoc original data without padding as received from SAP. Also, when you combine this SAP trigger with the Flat File Decode action, the schema that's provided to the action must match. |
+   | **IDoc Format** | No | The format to use for receiving IDocs. To add this parameter, from the **Advanced parameters** list, select **IDoc Format**. <br><br>- To receive IDocs as SAP plain XML, from the **IDoc Format** list, select **SapPlainXml**. <br><br>- To receive IDocs as a flat file, from the **IDoc Format** list, select **FlatFile**. <br><br>- **Note**: If you also use the [Flat File Decode action](../logic-apps-enterprise-integration-flatfile.md) in your workflow, in your flat file schema, you have to use the **early_terminate_optional_fields** property and set the value to **true**. This requirement is necessary because the flat file IDoc data record sent by SAP on the tRFC call named `IDOC_INBOUND_ASYNCHRONOUS` isn't padded to the full SDATA field length. Azure Logic Apps provides the flat file IDoc original data without padding as received from SAP. Also, when you combine this SAP trigger with the Flat File Decode action, the schema provided to the action must match. |
    | **Receive IDOCS with unreleased segments** | No | Receive IDocs with or without unreleased segments. To add this parameter and change the value, from the **Advanced parameters** list, select **Receive IDOCS with unreleased segments**, and select **Yes** or **No**. |
-   | **SncPartnerNames** | No | The list of SNC partners that have permissions to call the trigger at the SAP client library level. Only the listed partners are authorized by the SAP server's SNC connection. To add this parameter, from the **Advanced parameters** list, select **SncPartnerNames**. Make sure to enter each name separated by a vertical bar (**\|**). |
+   | **SncPartnerNames** | No | The list of SNC partners that have permissions to call the trigger at the SAP client library level. The list shows only partners that the SAP server's SNC connection authorizes. To add this parameter, from the **Advanced parameters** list, select **SncPartnerNames**. Make sure to enter each name separated by a vertical bar (**\|**). |
 
    The following example shows a minimally configured SAP managed trigger in a workflow:
 
@@ -355,7 +356,7 @@ Next, create an action to send your IDoc to SAP when the workflow's **Request**
 
    1. Browse the SAP action type folders using the arrows to find and select the SAP action that you want to use.
 
-      This example selects the following folders all the way to the SAP action named **Send**: **ORDERS** > **ORDERS05** > **720** > **Send**.
+      This example selects the following folders up to the SAP action named **Send**: **ORDERS** > **ORDERS05** > **720** > **Send**.
 
       :::image type="content" source="media/sap-create-example-scenario-workflows/sap-send-message-find-orders-action-consumption.png" alt-text="Screenshot shows Consumption workflow and selections for folders named Orders, Orders05, 720, and so on.":::
 
@@ -691,23 +692,23 @@ In the following example, the `STFC_CONNECTION` RFC module generates a request a
 
 You've now created a workflow that can send IDocs and communicate with your SAP server. Now that you've set up an SAP connection for your workflow, you can try experimenting with BAPI and RFC.
 
-#### Workflow time-out issues
+#### Workflow timeout issues
 
 Your workflow times out in any of the following scenarios:
 
-- All the steps required for the response don't finish within the [request time-out limit](../logic-apps-limits-and-config.md). If this condition happens, requests might get blocked. To help you diagnose problems, learn [how to check workflow status and view run history for your workflows](/azure/logic-apps/view-workflow-status-run-history).
+- All the steps required for the response don't finish within the [request timeout limit](../logic-apps-limits-and-config.md). If this condition happens, requests might get blocked. To help you diagnose problems, see [how to check workflow status and view run history for your workflows](/azure/logic-apps/view-workflow-status-run-history).
 
 - Your SAP system's processing mode is set to the default **Trigger immediately** setting, which causes your SAP system to block the inbound call for IDoc transmission until an IDoc finishes processing.
 
-  If your SAP system is under load, for example, when your workflow sends a batch of IDocs all at one time to SAP, the queued IDoc calls time out. The default processing mode causes your SAP system to block the inbound call for IDoc transmission until an IDoc finishes processing. In Azure Logic Apps, workflow actions have a 2-minute time out, by default.
+  If your SAP system is under load, for example, when your workflow sends a batch of IDocs all at one time to SAP, the queued IDoc calls time out. The default processing mode causes your SAP system to block the inbound call for IDoc transmission until an IDoc finishes processing. In Azure Logic Apps, workflow actions have a 2-minute timeout, by default.
 
   To resolve this problem, follow the [steps in the **Prerequisites** section that change the setting to **Trigger by background program**](sap.md#prerequisites).
 
 <a name="safe-typing"></a>
 
 ## Safe typing
 
-By default, when you create a connection for the SAP managed operation, strong typing is used to check for invalid values by performing XML validation against the schema. This behavior can help you detect issues earlier. The **Safe Typing** option is available for backward compatibility and only checks the string length. If you choose **Safe Typing**, the DATS type and TIMS type in SAP are treated as strings rather than as their XML equivalents, `xs:date` and `xs:time`, where `xmlns:xs="http://www.w3.org/2001/XMLSchema"`. Safe typing affects the behavior for all schema generation, the send message for both the "been sent" payload and the "been received" response, and the trigger.
+By default, when you create a connection for the SAP managed operation, strong typing is used to check for invalid values by performing XML validation against the schema. This behavior can help you detect issues earlier. The **Safe Typing** option is available for backward compatibility and only checks the string length. If you choose **Safe Typing**, the DATS type and TIMS type in SAP are treated as strings rather than as their XML equivalents, `xs:date` and `xs:time`, where `xmlns:xs="http://www.w3.org/2001/XMLSchema"`. Safe typing affects the behavior for all schema generation, the Send message for both the "sent" payload and the "received" response, and the trigger.
 
 When strong typing is used (**Safe Typing** isn't enabled), the schema maps the DATS and TIMS types to more straightforward XML types:
 

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)