Merge pull request #312977 from ecfan/freshness

[Azure Logic Apps] Updates for freshness

Author: Carolyn135

articles/connectors/connectors-create-api-mq.md

@@ -1,17 +1,19 @@
 ---
-title: Connect to IBM MQ
-description: Connect to an MQ server on premises or in Azure from a workflow in Azure Logic Apps.
+title: Connect to IBM MQ from Workflows
+description: Connect to MQ servers on-premises or in Azure from workflows in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 01/08/2025
+ms.update-cycle: 365-days
+ms.date: 03/10/2026
 ms.custom:
   - engagement-fy23
   - sfi-image-nochange
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to connect my integration workflows to MQ servers either on-premises or in Azure.
 ---
 
-# Connect to an IBM MQ server from a workflow in Azure Logic Apps
+# Connect to IBM MQ servers from workflows in Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 

articles/connectors/connectors-native-http-swagger.md

@@ -1,14 +1,16 @@
 ---
-title: Call REST API endpoints from workflows
-description: Call REST API endpoints from workflows in Azure Logic Apps.
+title: Call REST API Endpoints from Workflows
+description: Call the endpoint URL for a REST API from workflows in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 12/13/2024
+ms.update-cycle: 365-days
+ms.date: 03/10/2026
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to call a REST endpoint from my workflow.
 ---
 
-# Call REST API endpoints from workflows in Azure Logic Apps
+# Call endpoints for REST APIs from workflows in Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 
@@ -20,7 +22,7 @@ The **HTTP + Swagger** built-in operations currently support only OpenAPI 2.0, n
 
 ## 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).
 
 * The URL for the Swagger file that describes the target REST API endpoint that you want to call
 

articles/logic-apps/deploy-single-tenant-logic-apps-private-storage-account.md

@@ -1,24 +1,25 @@
 ---
-title: Deploy Standard logic apps to private storage accounts
+title: Deploy Standard Workflows to Private Storage
 description: Deploy Standard logic app workflows to Azure storage accounts that use private endpoints and deny public access.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
+ms.update-cycle: 365-days
+ms.date: 03/10/2026
 ms.custom: engagement-fy23, devx-track-arm-template
-ms.date: 02/24/2025
-# Customer intent: As a developer, I want to deploy Standard logic apps to Azure storage accounts that use private endpoints.
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to deploy Standard logic apps to Azure storage accounts that use private endpoints and deny public access.
 ---
 
-# Deploy single-tenant Standard logic apps to private storage accounts using private endpoints
+# Deploy Standard logic apps to Azure storage that use private endpoints
 
 [!INCLUDE [logic-apps-sku-standard](../../includes/logic-apps-sku-standard.md)]
 
 When you create a single-tenant Standard logic app resource, you're required to have a storage account for storing logic app artifacts. You can restrict access to this storage account so that only the resources inside a virtual network can connect to your logic app workflow. Azure Storage supports adding private endpoints to your storage account.
 
-This article describes the steps to follow for deploying such logic apps to protected private storage accounts.
+This guide shows how to deploy Standard logic apps to Azure storage accounts protected by private endpoints.
 
-For more information, review the following documentation:
+For more information, see:
 
 - [Secure traffic between Standard logic apps and Azure virtual networks using private endpoints](secure-single-tenant-workflow-virtual-network-private-endpoint.md)
 - [Use private endpoints for Azure Storage](../storage/common/storage-private-endpoints.md)
@@ -63,9 +64,9 @@ This deployment method requires temporary public access to your storage account.
 
    1. On the logic app resource menu, under **Settings**, select **Environment variables**.
 
-   1. On the **App settings** tab, add the **WEBSITE_CONTENTOVERVNET** app setting, if none exist, and set the value to **1**.
+   1. On the **App settings** tab, add the **WEBSITE_CONTENTOVERVNET** app setting, if none exists, and set the value to **1**.
 
-   1. If you use your own domain name server (DNS) with your virtual network, add the **WEBSITE_DNS_SERVER** app setting, if none exist, and set the value to the IP address for your DNS. If you have a secondary DNS, add another app setting named **WEBSITE_DNS_ALT_SERVER**, and set the value to the IP for your secondary DNS.
+   1. If you use your own domain name server (DNS) with your virtual network, add the **WEBSITE_DNS_SERVER** app setting, if none exists, and set the value to the IP address for your DNS. If you have a secondary DNS, add another app setting named **WEBSITE_DNS_ALT_SERVER**, and set the value to the IP for your secondary DNS.
 
 1. After you apply these app settings, you can remove public access from your storage account.
 

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

@@ -1,24 +1,26 @@
 ---
-title: B2B enterprise integration workflows
-description: Learn about building automated B2B workflows for enterprise integration by using Azure Logic Apps and Enterprise Integration Pack.
+title: B2B Enterprise Integration Workflows
+description: Learn about automated B2B workflows for enterprise integration 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: overview
-ms.date: 02/19/2025
+ms.update-cycle: 365-days
+ms.date: 03/10/2026
+# Customer intent: As a B2B enterprise integration developer, I want to learn about building B2B workflows in Azure Logic Apps.
 ---
 
-# B2B enterprise integration workflows with Azure Logic Apps and Enterprise Integration Pack
+# B2B enterprise integration workflows with Azure Logic Apps
 
-For business-to-business (B2B) solutions and seamless communication between organizations, you can build automated, scalable, enterprise integration workflows by using Azure Logic Apps with the Enterprise Integration Pack (EIP).
+For business-to-business (B2B) solutions and seamless communication between organizations, you can build automated, scalable, enterprise integration workflows by using Azure Logic Apps, which includes the Enterprise Integration Pack (EIP).
 
 ## What is the Enterprise Integration Pack?
 
 If you're familiar with Microsoft BizTalk Server, the EIP follows similar concepts and makes B2B capabilities easy to use. However, one major difference is that the EIP is architecturally based on *integration accounts*. These accounts are cloud-based containers in Azure that simplify how you store, manage, and use B2B artifacts for B2B communication, including trading partners, agreements, maps, schemas, certificates, and so on.
 
-With these artifacts, you can build B2B workflows and integration solutions that include cloud services, such as Azure, Microsoft, and other software-as-service (SaaS) apps, on-premises systems, and custom apps by using Azure Logic Apps and choosing from [hundreds of connectors](/connectors/connector-reference/connector-reference-logicapps-connectors). For example, you can create and run custom code from your workflows using the built-in and Azure Functions connectors. You can also use [enterprise integration connectors](../connectors/managed.md#enterprise-connectors) that support the following industry standards:
+With these artifacts, you can build B2B workflows and integration solutions that include cloud services, such as Azure, Microsoft, and other software-as-service (SaaS) apps, on-premises systems, and custom apps by using Azure Logic Apps and choosing from [1,400+ connectors](/connectors/connector-reference/connector-reference-logicapps-connectors). For example, you can create and run custom code from your workflows using the built-in and Azure Functions connectors. You can also use [enterprise integration connectors](../connectors/managed.md#enterprise-connectors) that support the following industry standards:
 
 * Electronic Data Interchange (EDI)
 * Enterprise Application Integration (EAI)
@@ -27,13 +29,13 @@ Although organizations use different protocols and formats for B2B communication
 
 ## What do I need to get started?
 
-* 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 [integration account](logic-apps-enterprise-integration-create-integration-account.md) to store the B2B artifacts that you define and want to use.
 
 * B2B artifacts, such as [trading partners](logic-apps-enterprise-integration-partners.md), [agreements](logic-apps-enterprise-integration-agreements.md), [maps](logic-apps-enterprise-integration-maps.md), [schemas](logic-apps-enterprise-integration-schemas.md), [certificates](logic-apps-enterprise-integration-certificates.md), and so on.
 
-* To create maps and schemas, you can use Visual Studio 2019 and the [Microsoft Azure Logic Apps Enterprise Integration Tools Extension](https://aka.ms/vsenterpriseintegrationtools). The extension is currently unavailable for Visual Studio 2022.
+* To create maps and schemas, you can use Visual Studio 2019 and the [Microsoft Azure Logic Apps Enterprise Integration Tools Extension](https://aka.ms/vsenterpriseintegrationtools). The extension is currently unavailable for Visual Studio 2022 and later.
 
    > [!NOTE]
    > Don't install this extension alongside the BizTalk Server extension. Having both extensions might 
@@ -74,7 +76,7 @@ The following diagram shows the high-level steps to start building B2B logic app
 
 To try this [sample](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.logic/logic-app-as2-send-receive), which deploys logic apps that send and receive AS2 messages through Azure, select **Deploy to Azure**. Before you run the sample, make sure that you manually update **FabrikamSales-AS2Send** logic app workflow so that the **HTTP** action's **URI** property uses the URI that's dynamically generated for the **Request** trigger in the **Contoso-AS2Receive** logic app.
 
-## Next steps
+## Related content
 
 * [Create trading partners](logic-apps-enterprise-integration-partners.md)
 * [Create agreements](logic-apps-enterprise-integration-agreements.md)