Merge pull request #312953 from ecfan/freshness

[Azure Logic Apps] Freshness edits

Author: JillGrant615

articles/connectors/built-in.md

@@ -1,12 +1,14 @@
 ---
-title: Built-in connector overview
+title: Built-In Connectors Overview
 description: Learn about connectors that run natively with the runtime in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: concept-article
+ms.update-cycle: 1095-days
+ms.date: 03/09/2026
 ms.custom: engagement-fy23
-ms.date: 03/18/2025
+#Customer intent: As an integration developer who works with Azure Logic Apps, I want to learn about built-in connectors, which directly run alongside the runtime to provide better performance and throughput, compared to their counterparts that run in multitenant Azure.
 ---
 
 # Built-in connectors in Azure Logic Apps
@@ -486,10 +488,9 @@ For more information, review the following documentation:
     :::column-end:::
 :::row-end:::
 
-## Next steps
+## Related content
 
-> [!div class="nextstepaction"]
-> [Create custom APIs that you can call from Azure Logic Apps](../logic-apps/logic-apps-create-api-app.md)
+- [Create custom APIs that you can call from Azure Logic Apps](../logic-apps/logic-apps-create-api-app.md)
 
 <!-- Built-in icons -->
 [azure-ai-search-icon]: ./media/apis-list/azure-ai-search.png
@@ -600,7 +601,7 @@ For more information, review the following documentation:
 [scope-doc]: ../logic-apps/logic-apps-control-flow-run-steps-group-scopes.md "Organize actions into groups, which get their own status after the actions in group finish running"
 [sftp-doc]: /azure/logic-apps/connectors/built-in/reference/sftp/ "Connect to your SFTP account by using SSH. Upload, get, delete files, and more"
 [smtp-doc]: /azure/logic-apps/connectors/built-in/reference/smtp/ "Connect to your SMTP server so you can send email"
-[sql-server-doc]: /azure/logic-apps/connectors/built-in/reference/sql/ "Connect to Azure SQL Database or SQL Server. Create, update, get, and delete entries in an SQL database table"
+[sql-server-doc]: /azure/logic-apps/connectors/built-in/reference/sql/ "Connect to Azure SQL Database or SQL Server. Create, update, get, and delete entries in a SQL database table"
 [switch-doc]: ../logic-apps/logic-apps-control-flow-switch-statement.md "Organize actions into cases, which are assigned unique values. Run only the case whose value matches the result from an expression, object, or token. If no matches exist, run the default case"
 [swift-doc]: https://techcommunity.microsoft.com/t5/azure-integration-services-blog/announcement-public-preview-of-swift-message-processing-using/ba-p/3670014 "Encode and decode SWIFT transactions in flat-file XML format"
 [terminate-doc]: ../logic-apps/logic-apps-workflow-actions-triggers.md#terminate-action "Stop or cancel an actively running workflow for your logic app workflow"

articles/connectors/connectors-azure-application-insights.md

@@ -3,25 +3,22 @@ title: Connect to Azure Application Insights
 description: Connect to Application Insights from a workflow in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 03/21/2025
-# Customer intent: As a developer, I want to get telemetry from an Application Insights resource to use with my workflow in Azure Logic Apps.
+ms.update-cycle: 1095-days
+ms.date: 03/10/2026
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to get telemetry from an Application Insights resource to use with my workflow in Azure Logic Apps.
 ---
 
 # Connect to Azure Application Insights from workflows in Azure Logic Apps
 
 > [!NOTE]
 > 
-> The [Azure Monitor Logs connector](/connectors/azuremonitorlogs/) replaces the [Azure Log Analytics connector](/connectors/azureloganalytics/) 
-> and the [Azure Application Insights connector](/connectors/applicationinsights/). This combined connector provides the same functionality as 
-> the other connectors and is the preferred method for running a query against a Log Analytics workspace or an Application Insights resource.
+> The [Azure Monitor Logs connector](/connectors/azuremonitorlogs/) replaces both the [Azure Application Insights connector](/connectors/applicationinsights/) and the [Azure Log Analytics connector](/connectors/azureloganalytics/). This combined connector provides the same functionality as the other connectors and is the preferred way to run a query against an Application Insights resource or Log Analytics workspace.
 > 
-> For example, when you connect to your Application Insights resource, you don't have to create or provide an application ID and API key. 
-> Authentication is integrated with Microsoft Entra ID. For the how-to guide to use the Azure Monitor Logs connector, see 
-> [Connect to Log Analytics or Application Insights from workflows in Azure Logic Apps](connectors-azure-monitor-logs.md).
+> For example, when you connect to your Application Insights resource, you don't have to create or provide an application ID and API key. Authentication is integrated with Microsoft Entra ID. For the how-to guide to use the Azure Monitor Logs connector, see [Connect to Log Analytics or Application Insights from workflows in Azure Logic Apps](connectors-azure-monitor-logs.md).
 
-For more information, see the following documentation:
+For more information, see:
 
 - [Azure Monitor Logs connector](/connectors/azuremonitorlogs/)
 - [Connect to Log Analytics or Application Insights from workflows in Azure Logic Apps](connectors-azure-monitor-logs.md)

articles/connectors/connectors-create-api-cosmos-db.md

@@ -5,13 +5,15 @@ services: logic-apps
 ms.suite: integration
 author: jcocchi
 ms.author: jucocchi
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 04/15/2025
+ms.update-cycle: 365-days
+ms.date: 03/10/2026
 ms.custom: sfi-image-nochange
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to access and manage documents in Azure Cosmos DB from my workflows.
 ---
 
-# Access, create, or process documents in Azure Cosmos DB with workflows in Azure Logic Apps
+# Access, create, or process documents in Azure Cosmos DB from workflows in Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 
@@ -27,7 +29,7 @@ You can connect to Azure Cosmos DB from both Consumption and Standard logic app
 
 ## Prerequisites
 
-- An Azure account and subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+- An Azure account and subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
 - An [Azure Cosmos DB account](/azure/cosmos-db/sql/create-cosmosdb-resources-portal).
 
@@ -66,7 +68,7 @@ To add an Azure Cosmos DB built-in trigger to a Standard workflow, follow these
    | **Database Id** | Yes | <*database-name*> | The name of the database with the container to monitor. This database should also have the lease container. If you don't have a lease container, the connector creates one for you in a later step. |
    | **Monitored Container Id** | Yes | <*container-name*> | The name of the container to monitor. This container should exist in the specified database. |
    | **Lease Container Id** |  Yes | <*lease-container-name*> | The name of either an existing container or a new container to create. The trigger automatically populates with **`leases`** as the default name. |
-   | **Create Lease Container** | No | **No** or **Yes** | If the lease container exists in the specified database, select **No**. To create this container, select **Yes**. If you select **Yes** and are using manual throughput dedicated for each container, make sure to open the **Advanced parameters** list to select the **Lease Container Throughput** parameter. Enter the number of [request units (RUs)](/azure/cosmos-db/request-units) to provision for this container. |
+   | **Create Lease Container** | No | **No** or **Yes** | If the lease container exists in the specified database, select **No**. To create this container, select **Yes**. If you select **Yes** and are using manual throughput dedicated for each container, make sure to open the **Advanced parameters** list to select the **Lease Container Throughput** parameter. Enter the number of [request units (RUs)](/azure/cosmos-db/request-units) to deploy for this container. |
 
    > [!NOTE]
    >
@@ -99,7 +101,7 @@ To add an Azure Cosmos DB action to a Consumption workflow, follow these steps:
 
 1. If the workflow is blank, add any trigger that you want.
 
-   This example starts with the [**When a HTTP request is received** trigger](connectors-native-reqres.md#add-request-trigger).
+   This example starts with the [**When an HTTP request is received** trigger](connectors-native-reqres.md#add-request-trigger).
 
 1. Under the trigger or action where you want to add the Azure Cosmos DB action, follow [these general steps to add the **Azure Cosmos DB** action that you want](/azure/logic-apps/create-workflow-with-trigger-or-action?tabs=consumption#add-action).
 
@@ -136,9 +138,9 @@ To add an Azure Cosmos DB built-in action to a Standard workflow, follow these s
 
 1. If the workflow is blank, add any trigger that you want.
 
-   This example starts with the [**When a HTTP request is received** trigger](connectors-native-reqres.md#add-request-trigger), which uses a basic schema definition to represent the item that you want to create:
+   This example starts with the [**When an HTTP request is received** trigger](connectors-native-reqres.md#add-request-trigger), which uses a basic schema definition to represent the item that you want to create:
 
-   :::image type="content" source="./media/connectors-create-api-cosmos-db/http-trigger-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard workflow, and trigger named When a HTTP request is received.":::
+   :::image type="content" source="./media/connectors-create-api-cosmos-db/http-trigger-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard workflow, and trigger named When an HTTP request is received.":::
 
 1. Under the trigger or action where you want to add the Azure Cosmos DB action, follow [these general steps to add the **Azure Cosmos DB** action that you want](/azure/logic-apps/create-workflow-with-trigger-or-action?tabs=standard#add-action).
 
@@ -159,7 +161,7 @@ To add an Azure Cosmos DB built-in action to a Standard workflow, follow these s
    | **Container Id** | Yes | <*container-ID*> | The container to query. |
    | **Item** | Yes | <*JSON-document*> | The JSON document to create. This example uses the **id** output from the Request trigger. <br><br>**Note**: If you use the **body** trigger output, make sure that the body content is well-formed JSON, and at a minimum, contains the **`id`** attribute and the **`partitionKey`** attribute for your document. If a document with these attributes exists, the document is updated. Otherwise, a new document is created. |
 
-   The following example shows the action named **Create or update item**, which includes the **Item** and **Partition Key** parameter values from the output for the trigger named **When a HTTP request is received**:
+   The following example shows the action named **Create or update item**, which includes the **Item** and **Partition Key** parameter values from the output for the trigger named **When an HTTP request is received**:
 
    :::image type="content" source="media/connectors-create-api-cosmos-db/create-action-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard workflow, and Azure Cosmos DB built-in action named Create or update item.":::
 
@@ -215,7 +217,7 @@ For a Standard workflow, an Azure Cosmos DB connection (built-in) requires the f
 
 ### Get iterable results from the Query items action
 
-The **Query items** built-in action in a Standard workflow has many dynamic content outputs available for use in subsequent actions. To get the query result items or item metadata as an iterable object, follow these steps:
+In a Standard workflow, the **Query items** built-in action produces many dynamic content output items for use in subsequent actions. To get the query result items or item metadata as an iterable object, follow these steps:
 
 1. In the [Azure portal](https://portal.azure.com), open your Standard workflow in the designer.
 

articles/connectors/integrate-3270-apps-ibm-mainframe.md

@@ -7,9 +7,10 @@ author: haroldcampos
 ms.author: hcampos
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 01/26/2026
+ms.update-cycle: 1095-days
+ms.date: 03/10/2026
 ms.custom: sfi-image-nochange
-#Customer intent: As an integration developer who works with Azure Logic Apps, I need to connect my workflows with 3270 screen-driven apps on IBM mainframes.
+#Customer intent: As an integration developer who works with Azure Logic Apps, I need to connect my workflows to 3270 screen-driven apps on IBM mainframes.
 ---
 
 # Integrate 3270 screen-driven apps on IBM mainframes with workflows in Azure Logic Apps

articles/connectors/integrate-cics-apps-ibm-mainframe.md

@@ -5,12 +5,11 @@ services: logic-apps
 ms.suite: integration
 author: haroldcampos
 ms.author: hcampos
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 04/08/2025
+ms.date: 03/10/2026
 ms.custom: sfi-image-nochange
-
-#customer intent: As a developer, I want to use the IBM CICS connector so I can integrate CICS programs with Standard workflows in Azure Logic Apps.
+#Customer intent: As an integration developer who works with Azure Logic Apps, I need to use the IBM CICS connector in Standard workflows so I can integrate CICS programs.
 ---
 
 # Integrate CICS programs on IBM mainframes with Standard workflows in Azure Logic Apps
@@ -97,7 +96,7 @@ Follow these steps to add a CICS action and configure the necessary parameters:
 
 1. If you don't have a trigger to start your workflow, follow [these general steps to add the trigger that you want](../logic-apps/create-workflow-with-trigger-or-action.md?tabs=standard#add-trigger).
 
-   This example continues with the **Request** trigger named **When a HTTP request is received**:
+   This example continues with the **Request** trigger named **When an HTTP request is received**:
 
    :::image type="content" source="media/integrate-cics-apps-ibm-mainframe/request-trigger.png" alt-text="Screenshot shows Azure portal, Standard workflow designer, and Request trigger." lightbox="media/integrate-cics-apps-ibm-mainframe/request-trigger.png":::
 

articles/connectors/integrate-host-files-ibm-mainframe.md

@@ -5,11 +5,11 @@ services: logic-apps
 ms.suite: integration
 author: haroldcampos
 ms.author: hcampos
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 04/08/2025
-
-#customer intent: As a developer, I want to use the IBM Host File connector so I can parse and generate offline IBM host files from IBM mainframes with Standard workflows in Azure Logic Apps.
+ms.update-cycle: 1095-days
+ms.date: 03/10/2026
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to use the IBM Host File connector in Standard workflows so I can parse and generate offline IBM host files from IBM mainframes.
 ---
 
 # Parse and generate host files from IBM mainframes for Standard workflows in Azure Logic Apps

articles/connectors/integrate-ibmi-apps-distributed-program-calls.md

@@ -5,12 +5,12 @@ services: logic-apps
 ms.suite: integration
 author: haroldcampos
 ms.author: hcampos
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 04/08/2025
+ms.update-cycle: 1095-days
+ms.date: 03/10/2026
 ms.custom: sfi-image-nochange
-
-#customer intent: As a developer, I want to use the IBM i connector so I can integrate COBOL and RPG programs on IBM midrange systems with Standard workflows in Azure Logic Apps.
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to use the IBM i connector in Standard workflows so I can integrate COBOL and RPG programs on IBM midrange systems.
 ---
 
 # Integrate COBOL and RPG programs on IBM midrange systems with Standard workflows in Azure Logic Apps
@@ -27,11 +27,11 @@ This article describes the following aspects about the IBM i connector:
 
 ## Review the connector usage scenarios
 
-More than 50 years ago, IBM released the first midrange systems. IBM advertised them as "Small in size, small in price and Big in performance. It is a system for now and for the future." Over the years, the midrange systems evolved and became pervasive in medium-sized businesses or in large enterprises to extend mainframe environments. Midrange systems that run IBM i, typically Power Systems, support TCP/IP and SNA.
+More than 50 years ago, IBM released the first midrange systems. IBM advertised them as "Small in size, small in price and Big in performance. It's a system for now and for the future." Over the years, the midrange systems evolved and became pervasive in medium-sized businesses or in large enterprises to extend mainframe environments. Midrange systems that run IBM i, typically Power Systems, support TCP/IP, and SNA.
 
 The IBM i system includes the DPC server feature that allows most IBM i applications to interact with clients like Azure Logic Apps by using the client-initiated only request-reply pattern with minimum modifications. DPC is a documented protocol that supports program-to-program integration on an IBM i system, which client applications can easily access by using the TCP/IP networking protocol.
 
-Microsoft [Host Integration Server (HIS)](/host-integration-server/what-is-his) provides connectivity to IBM i systems by using TCP/IP and APPC LU6.2. For many years, customers have used the HIS Transaction Integrator to integrate on-premises IBM i systems and Windows. The **IBM i Program Call** connector uses the TCP/IP [programming model](/host-integration-server/core/choosing-the-appropriate-programming-model1) to interact with IBM i COBOL and RPG programs.
+Microsoft [Host Integration Server (HIS)](/host-integration-server/what-is-his) provides connectivity to IBM i systems by using TCP/IP and APPC LU6.2. For many years, customers used the HIS Transaction Integrator to integrate on-premises IBM i systems and Windows. The **IBM i Program Call** connector uses the TCP/IP [programming model](/host-integration-server/core/choosing-the-appropriate-programming-model1) to interact with IBM i COBOL and RPG programs.
 
 The following diagram shows how the IBM i connector interacts with an IBM i system:
 
@@ -103,7 +103,7 @@ Follow these steps to add an IBM i action and configure the necessary parameters
 
 1. If you don't have a trigger to start your workflow, follow [these general steps to add the trigger that you want](../logic-apps/create-workflow-with-trigger-or-action.md?tabs=standard#add-trigger).
 
-   This example continues with the **Request** trigger named **When a HTTP request is received**:
+   This example continues with the **Request** trigger named **When an HTTP request is received**:
 
    :::image type="content" source="media/integrate-ibmi-apps-dpc/request-trigger.png" alt-text="Screenshot shows Azure portal, Standard workflow designer, and Request trigger." lightbox="media/integrate-ibmi-apps-dpc/request-trigger.png":::
 
@@ -119,7 +119,7 @@ Follow these steps to add an IBM i action and configure the necessary parameters
    | **Password** | No | <*password*> | The optional user password for connection authentication. |
    | **Port Number** | Yes | <*port-number*> | The port number to use for connection authentication. |
    | **Server Name** | Yes | <*server-name*> | The server name. |
-   | **Timeout** | No | <*timeout*> | The time-out period in seconds while waiting for responses from the server. |
+   | **Timeout** | No | <*timeout*> | The timeout period in seconds while waiting for responses from the server. |
    | **User Name** | No | <*user-name*> | The optional username for connection authentication. |
    | **Use TLS** | No | True or false | Secure the connection with Transport Security Layer (TLS). |
    | **Validate Server certificate** | No | True or false | Validate the server's certificate. |