Merge pull request #294981 from ecfan/patch-1

JillGrant615 · web-flow · commit 564880090e3b · 2025-02-20T12:34:08.000-07:00
[BULK (mostly)] Freshness review
diff --git a/articles/connectors/compare-built-in-azure-connectors.md b/articles/connectors/compare-built-in-azure-connectors.md
@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: conceptual
-ms.date: 01/04/2024
+ms.date: 02/20/2025
 # Customer intent: As a developer, I want to understand the differences between built-in and Azure connectors in Azure Logic Apps (Standard).
 ---
 
diff --git a/articles/connectors/connectors-create-api-crmonline.md b/articles/connectors/connectors-create-api-crmonline.md
@@ -5,12 +5,13 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: jdaly, estfan, azla
 ms.topic: how-to
-ms.date: 01/04/2024
+ms.date: 02/20/2025
 ---
 
 # Connect to Dynamics 365 from workflows in Azure Logic Apps (Deprecated)
 
 > [!IMPORTANT]
+> 
 > The Dynamics 365 connector is officially deprecated and is no longer available. Instead, use the 
 > [Microsoft Dataverse connector](/connectors/commondataserviceforapps/) to access Microsoft Dataverse 
 > used for Microsoft Dynamics 365 Sales, Microsoft Dynamics 365 Customer Service, Microsoft Dynamics 365 
diff --git a/articles/connectors/connectors-create-api-smtp.md b/articles/connectors/connectors-create-api-smtp.md
@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 01/04/2024
+ms.date: 02/19/2025
 ---
 
 # Connect to your SMTP account from Azure Logic Apps
@@ -43,23 +43,18 @@ such as a Salesforce trigger, if you have a Salesforce account.
   record is created, your logic app sends an email 
   from your SMTP account about the new record.
 
+## Connector reference
+
+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](/connectors/smtpconnector/).
+
 ## Connect to SMTP
 
 [!INCLUDE [Create connection general intro](../../includes/connectors-create-connection-general-intro.md)]
 
 1. Sign in to the [Azure portal](https://portal.azure.com), 
-and open your logic app in Logic App Designer, if not open already.
-
-1. Under the last step where you want to add an SMTP action, 
-choose **New step**. 
+and open your logic app resource and workflow in the designer, if not open already.
 
-   To add an action between steps, 
-   move your pointer over the arrow between steps. 
-   Choose the plus sign (**+**) that appears, 
-   and then select **Add an action**.
-
-1. In the search box, enter "smtp" as your filter. 
-Under the actions list, select the action you want.
+1. [Follow these general steps to add the **SMTP** action that you want](/azure/logic-apps/create-workflow-with-trigger-or-action#add-action). 
 
 1. When prompted, provide this connection information:
 
@@ -71,16 +66,11 @@ Under the actions list, select the action you want.
    | **Password** | Yes | Your password for your SMTP account | 
    | **SMTP Server Port** | No | A specific port on your SMTP server you want to use | 
    | **Enable SSL?** | No | Turn on or turn off TLS/SSL encryption. | 
-   |||| 
 
 1. Provide the necessary details for your selected action. 
 
 1. Save your logic app or continue building your logic app's workflow.
 
-## Connector reference
-
-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](/connectors/smtpconnector/).
-
 ## Next steps
 
 * [Managed connectors for Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors)
diff --git a/articles/connectors/integrate-cics-apps-ibm-mainframe.md b/articles/connectors/integrate-cics-apps-ibm-mainframe.md
@@ -7,7 +7,7 @@ author: haroldcampos
 ms.author: hcampos
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 11/01/2023
+ms.date: 02/20/2025
 ---
 
 # Integrate CICS programs on IBM mainframes with Standard workflows in Azure Logic Apps
diff --git a/articles/connectors/integrate-host-files-ibm-mainframe.md b/articles/connectors/integrate-host-files-ibm-mainframe.md
@@ -7,7 +7,7 @@ author: haroldcampos
 ms.author: hcampos
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 11/02/2023
+ms.date: 02/20/2025
 ---
 
 # Parse and generate host files from IBM mainframes for Standard workflows in Azure Logic Apps
@@ -229,4 +229,4 @@ Later in this guide, when you add the **Parse Host File Contents** action to you
 * [Monitor workflow run status, review trigger and workflow run history, and set up alerts in Azure Logic Apps](../logic-apps/monitor-logic-apps.md?tabs=standard)
 * [View metrics for workflow health and performance in Azure Logic Apps](../logic-apps/view-workflow-metrics.md?tabs=standard)
 * [Monitor and collect diagnostic data for workflows in Azure Logic Apps](../logic-apps/monitor-workflows-collect-diagnostic-data.md?tabs=standard)
-* [Enable and view enhanced telemetry in Application Insights for Standard workflows in Azure Logic Apps](../logic-apps/enable-enhanced-telemetry-standard-workflows.md)
+* [Enable and view enhanced telemetry in Application Insights for Standard workflows in Azure Logic Apps](../logic-apps/enable-enhanced-telemetry-standard-workflows.md)
diff --git a/articles/connectors/integrate-ibmi-apps-distributed-program-calls.md b/articles/connectors/integrate-ibmi-apps-distributed-program-calls.md
@@ -7,7 +7,7 @@ author: haroldcampos
 ms.author: hcampos
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 03/07/2024
+ms.date: 02/20/2025
 ---
 
 # Integrate COBOL and RPG programs on IBM midrange systems with Standard workflows in Azure Logic Apps
diff --git a/articles/connectors/integrate-ims-apps-ibm-mainframe.md b/articles/connectors/integrate-ims-apps-ibm-mainframe.md
@@ -7,7 +7,7 @@ author: haroldcampos
 ms.author: hcampos
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 01/10/2024
+ms.date: 02/20/2025
 ---
 
 # Integrate IMS programs on IBM mainframes with Standard workflows in Azure Logic Apps
diff --git a/articles/logic-apps/add-run-csharp-scripts.md b/articles/logic-apps/add-run-csharp-scripts.md
@@ -5,7 +5,7 @@ ms.service: azure-logic-apps
 ms.suite: integration
 ms.reviewer: estfan, shahparth, azla
 ms.topic: how-to
-ms.date: 06/26/2024
+ms.date: 02/19/2025
 # Customer intent: As a logic app workflow developer, I want to write and run my own C# scripts so that I can perform custom integration tasks in Standard workflows for Azure Logic Apps.
 ---
 
diff --git a/articles/logic-apps/azure-arc-enabled-logic-apps-overview.md b/articles/logic-apps/azure-arc-enabled-logic-apps-overview.md
@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, kewear, rohithah, archidda, azla
 ms.topic: overview
-ms.date: 01/04/2024
+ms.date: 02/19/2025
 #Customer intent: As a developer, I want to learn about automated Azure Arc-enabled logic app workflows that can run anywhere that Kubernetes can run.
 ---
 
diff --git a/articles/logic-apps/custom-connector-overview.md b/articles/logic-apps/custom-connector-overview.md
@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, daviburg, apseth, psrivas, azla
 ms.topic: conceptual
-ms.date: 01/04/2024
+ms.date: 02/19/2025
 # Customer intent: As a developer, I want learn about the capability to create custom connectors with operations that I can use in my Azure Logic Apps workflows.
 ---
 
diff --git a/articles/logic-apps/export-from-consumption-to-standard-logic-app.md b/articles/logic-apps/export-from-consumption-to-standard-logic-app.md
@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, wsilveira
 ms.topic: how-to
-ms.date: 07/05/2024
+ms.date: 02/19/2025
 #Customer intent: As a developer, I want to export one or more Consumption workflows to a Standard workflow.
 ---
 
diff --git a/articles/logic-apps/export-from-ise-to-standard-logic-app.md b/articles/logic-apps/export-from-ise-to-standard-logic-app.md
@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, wsilveira
 ms.topic: how-to
-ms.date: 12/11/2023
+ms.date: 02/20/2025
 ms.custom: engagement-fy23
 #Customer intent: As a developer, I want to export one or more ISE workflows to a Standard workflow.
 ---
diff --git a/articles/logic-apps/healthy-unhealthy-resource.md b/articles/logic-apps/healthy-unhealthy-resource.md
@@ -5,15 +5,17 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 01/04/2024
+ms.date: 02/20/2025
 ---
 
 # Set up logging to monitor logic apps in Microsoft Defender for Cloud
 
 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.
 
 > [!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, review the
+> [Azure status page](https://azure.status.microsoft/), which lists the status for different products and services in each available region.
 
 ## Prerequisites
 
diff --git a/articles/logic-apps/logic-apps-create-azure-resource-manager-templates.md b/articles/logic-apps/logic-apps-create-azure-resource-manager-templates.md
@@ -6,7 +6,7 @@ ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
 ms.custom: devx-track-azurepowershell, devx-track-arm-template
-ms.date: 01/04/2024
+ms.date: 02/19/2025
 ---
 
 # Create Azure Resource Manager templates to automate Consumption logic app deployment for Azure Logic Apps
diff --git a/articles/logic-apps/logic-apps-deploy-azure-resource-manager-templates.md b/articles/logic-apps/logic-apps-deploy-azure-resource-manager-templates.md
@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 01/04/2024
+ms.date: 02/19/2025
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, engagement-fy23, devx-track-arm-template
 ms.devlang: azurecli
 ---
diff --git a/articles/logic-apps/logic-apps-enterprise-integration-agreements.md b/articles/logic-apps/logic-apps-enterprise-integration-agreements.md
@@ -7,7 +7,7 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 01/04/2024
+ms.date: 02/20/2025
 ---
 
 # Add agreements between partners in integration accounts for workflows in Azure Logic Apps
diff --git a/articles/logic-apps/logic-apps-enterprise-integration-b2b-business-continuity.md b/articles/logic-apps/logic-apps-enterprise-integration-b2b-business-continuity.md
@@ -7,7 +7,7 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 01/04/2024
+ms.date: 02/20/2025
 ---
 
 # Set up cross-region disaster recovery for integration accounts in Azure Logic Apps
diff --git a/articles/logic-apps/logic-apps-enterprise-integration-b2b-list-errors-solutions.md b/articles/logic-apps/logic-apps-enterprise-integration-b2b-list-errors-solutions.md
@@ -7,51 +7,34 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: conceptual
-ms.date: 01/04/2024
+ms.date: 02/20/2025
 ---
 
 # B2B errors and solutions for Azure Logic Apps
 
 [!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.
+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
 
-### No agreement found
-
-**Error description**: No agreement found with Agreement Resolution Parameters.
-
-**User action**: The agreement should be added to the integration account with agreed business identities. The business identities should match to the input message IDs.
-
-### No agreement found with identities
-
-**Error description**: No agreement found with identities: 'AS2Identity'::'Partner1' and'AS2Identity'::'Partner3'
-
-**User action**: Invalid AS2-From or AS2-To configured for agreement. Correct the AS2 message's "AS2-From" or "AS2-To" headers or the agreement to match the AS2 IDs in the AS2 message headers with agreement configurations.
+| Error summary | Error | Resolution |
+|---------------|-------|------------|
+| No agreement found. | **No agreement found with Agreement Resolution Parameters.** | Add an agreement with the appropriate business identities to your integration account. Make sure that the business identities match to the input message IDs. |
+| No agreement found with identities. | **No agreement found with identities: 'AS2Identity'::'Partner1' and'AS2Identity'::'Partner3'** | The agreement has invalid **AS2-From** or **AS2-To** values. To match the AS2 IDs in the AS2 message headers for your agreement setup, correct the AS2 message header values **AS2-From** or **AS2-To** or the agreement. |
 
 ## AS2
 
-### Missing AS2 message headers  
-
-**Error description**: Invalid AS2 headers. One of the "AS2-To" or "AS2-From" headers is empty.
-
-**User action**: An AS2 message was received that did not contain the AS2-From or AS2-To or both headers. Check AS2 message AS2-From and AS2-To headers and correct them based on agreement configuration.
-
-### Missing AS2 message body and headers    
+| Error summary | Error | Resolution |
+|---------------|-------|------------|
+| Missing AS2 message headers | **Invalid AS2 headers. One of the "AS2-To" or "AS2-From" headers is empty.** | A received AS2 message didn't contain the headers for **AS2-From**, **AS2-To**, or both. Check the AS2 message headers for **AS2-From** and **AS2-To**, and correct them based on your agreement setup. |
+| Missing AS2 message body and headers | **The request content is null or empty.** | A received AS2 message didn't contain a message body. Make sure that a message body exists. |
+| AS2 message decryption failure | **`[processed/Error: decryption-failed]`** | Apply the `@base64ToBinary()` function to the AS2Message before sending the message to the trading partner. See [Example - AS2 message decryption failure example](#as2-decryption-failure). |
+| Message Disposition Notification (MDN) decryption failure | **`[processed/Error: decryption-failed]`** | Apply the `@base64ToBinary()` function to the MDN before sending the notification to the partner. See [Example - Message Disposition Notification (MDN) decryption failure](#mdn-decryption-failure). |
+| Missing signing certificate | **The Signing Certificate has not been configured for AS2 party. AS2-From: partner1 AS2-To: partner2** | Set the AS2 agreement settings with the correct certificate for the signature. |
 
-**Error description**: The request content is null or empty.
-
-**User action**: An AS2 message was received that did not contain the message body.
-
-### AS2 message decryption failure
-
-**Error description**:  [processed/Error: decryption-failed]
-
-**User action**: Add @base64ToBinary to AS2Message before sending to partner.
-
-For example:
+<a name="as2-decryption-failure"></a>
+### Example - AS2 message decryption failure
 
 ```json
 "HTTP": {
@@ -63,13 +46,8 @@ For example:
 },
 ``` 
 
-### MDN decryption failure
-
-**Error description**:  [processed/Error: decryption-failed]
-
-**User action**: Add @base64ToBinary to MDN before sending to partner.
-
-For example:
+<a name="mdn-decryption-failure"></a>
+### Example - Message Disposition Notification (MDN) decryption failure
 
 ```json
 "Response": {
@@ -80,44 +58,26 @@ For example:
 },               
 ``` 
 
-### Missing signing certificate
-
-**Error description**: The Signing Certificate has not been configured for AS2 party. AS2-From: partner1 AS2-To: partner2
-
-**User action**: Configure AS2 agreement settings with correct certificate for signature.
-
 ## X12 and EDIFACT
 
-### Leading or trailing space found    
-
-**Error description**: Error encountered during parsing. The EDIFACT transaction set with ID '123456' contained in interchange (without group) with ID '987654', with sender ID 'Partner1', receiver ID 'Partner2' is being suspended with following errors: "Leading Trailing separator found"
-
-**User action**: The agreement settings to be configured to allow leading and trailing space. Edit agreement settings to allow leading and trailing space.
-
-![allow space](./media/logic-apps-enterprise-integration-b2b-list-errors-solutions/leadingandtrailing.png)
-
-### Duplicate check has enabled in the agreement
-
-**Error description**: Duplicate Control Number
-
-**User action**: This error indicates the received message has duplicate control numbers. Correct the control number and resend the message.
-
-### Missing schema in the agreement
-
-**Error description**: Error encountered during parsing. The X12 transaction set with ID '564220001' contained in functional group with ID '56422', in interchange with ID '000056422', with sender ID '12345678', receiver ID '87654321' is being suspended with following errors: "The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement"
-
-**User action**: Configure schema in the agreement settings.
-
-### Incorrect schema in the agreement
+| Error summary | Error | Resolution |
+|---------------|-------|------------|
+| Duplicate check is enabled in the agreement. | **Duplicate Control Number** | This error indicates that the received message has duplicate control numbers. Correct the control number, and resend the message. |
+| Missing schema in the agreement | **Error encountered during parsing. The X12 transaction set with ID '564220001' contained in functional group with ID '56422', in interchange with ID '000056422', with sender ID '12345678', receiver ID '87654321' is being suspended with following errors: "The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement"** | Set up the schema in the agreement settings. |
+| Incorrect schema in the agreement | **The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement.** | Set up the correct schema in the agreement settings. |
+| Leading or trailing space found | **Error encountered during parsing. The EDIFACT transaction set with ID '123456' contained in interchange (without group) with ID '987654', with sender ID 'Partner1', receiver ID 'Partner2' is being suspended with following errors: "Leading Trailing separator found"** | Set up or edit the agreement settings to allow leading and trailing whitespace. See [Example - Allow leading and trailing whitespace](#allow-leading-trailing-whitespace). |
 
-**Error description**: The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement.
+<a name="allow-leading-trailing-whitespace"></a>
+### Example - Set up agreement settings to allow leading and trailing whitespace
 
-**User action**: Configure correct schema in the agreement settings.
+![Screenshot shows example for setting to allow leading and trailing whitespace.](./media/logic-apps-enterprise-integration-b2b-list-errors-solutions/leadingandtrailing.png)
 
 ## Flat file
 
-### Input message with no body
+| Error summary | Error | Resolution |
+|---------------|-------|------------|
+| Input message with no body | **InvalidTemplate. Unable to process template language expressions in action 'Flat_File_Decoding' inputs at line '1' and column '1902': 'Required property 'content' expects a value but got null. Path ''.'.** | This error indicates that the input message doesn't contain a body. Make sure that the input message contains a body. |
 
-**Error description**: InvalidTemplate. Unable to process template language expressions in action 'Flat_File_Decoding' inputs at line '1' and column '1902': 'Required property 'content' expects a value but got null. Path ''.'.
+## Related content
 
-**User action**: This error indicates the input message does not contain a body.
+- [Exchange B2B messages between partners using workflows in Azure Logic Apps](/azure/logic-apps/logic-apps-enterprise-integration-b2b)
diff --git a/articles/logic-apps/logic-apps-enterprise-integration-overview.md b/articles/logic-apps/logic-apps-enterprise-integration-overview.md
@@ -7,7 +7,7 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: overview
-ms.date: 01/04/2024
+ms.date: 02/19/2025
 ---
 
 # B2B enterprise integration workflows with Azure Logic Apps and Enterprise Integration Pack
diff --git a/articles/logic-apps/logic-apps-enterprise-integration-partners.md b/articles/logic-apps/logic-apps-enterprise-integration-partners.md
@@ -7,7 +7,7 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 01/04/2024
+ms.date: 02/20/2025
 ---
 
 # Add trading partners to integration accounts for workflows in Azure Logic Apps
@@ -104,4 +104,4 @@ If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overvi
 
 ## Next steps
 
-* [Add agreements between partners](logic-apps-enterprise-integration-agreements.md)
+* [Add agreements between partners](logic-apps-enterprise-integration-agreements.md)
diff --git a/articles/logic-apps/logic-apps-enterprise-integration-schemas.md b/articles/logic-apps/logic-apps-enterprise-integration-schemas.md
diff --git a/articles/logic-apps/logic-apps-serverless-overview.md b/articles/logic-apps/logic-apps-serverless-overview.md
diff --git a/articles/logic-apps/mainframe-modernization-overview.md b/articles/logic-apps/mainframe-modernization-overview.md
diff --git a/articles/logic-apps/move-logic-app-resources.md b/articles/logic-apps/move-logic-app-resources.md
diff --git a/articles/logic-apps/quickstart-create-deploy-azure-resource-manager-template.md b/articles/logic-apps/quickstart-create-deploy-azure-resource-manager-template.md
diff --git a/articles/logic-apps/quickstart-create-deploy-bicep.md b/articles/logic-apps/quickstart-create-deploy-bicep.md
diff --git a/articles/logic-apps/quickstart-logic-apps-azure-cli.md b/articles/logic-apps/quickstart-logic-apps-azure-cli.md
diff --git a/articles/logic-apps/quickstart-logic-apps-azure-powershell.md b/articles/logic-apps/quickstart-logic-apps-azure-powershell.md
diff --git a/articles/logic-apps/sample-logic-apps-cli-script.md b/articles/logic-apps/sample-logic-apps-cli-script.md
diff --git a/articles/logic-apps/update-workflow-definition-language-schema.md b/articles/logic-apps/update-workflow-definition-language-schema.md
