Clarity updates and minor restructuring

Author: ecfan

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

@@ -12,26 +12,23 @@ ms.date: 01/24/2025
 
 # What is Azure Logic Apps?
 
-Azure Logic Apps is a cloud platform where you build and run automated workflows that complete tasks inside, across, and outside the software ecosystems in your enterprise or organization. These workflows bring together disparate components so that they can work more easily together in the solutions that you build.
+Azure Logic Apps is a cloud platform where you can create and run automated workflows in, across, and outside the software ecosystems in your enterprise or organization. This platform greatly reduces or removes the need to write code when your workflows must connect and work with resources from different components, such as services, systems, apps, and data sources.
 
-The platform includes a visual designer for creating workflows along with prebuilt operations that work with commonly used services, systems, apps, and data sources. You use these operations as the building blocks for your workflows.
+Azure Logic Apps includes low-code-no-code tools for you to work with legacy, modern, and cutting-edge systems that exist in the cloud, on premises, or in hybrid environments. For example, you use a visual designer along with prebuilt operations to make building workflows as easy as possible. These prebuilt operations act as the building blocks in your workflows by giving you access to various resources and completing common tasks, such as getting data, sending data, and managing data. With Azure Logic Apps, you can build integration solutions that scale and support the business scenarios for your enterprise or organization's needs.
 
-Azure Logic Apps simplifies the way that you connect legacy, modern, and cutting-edge systems across cloud, on premises, and partially connected environments. You can use low-code-no-code tools to develop highly scalable integration solutions that support your enterprise and business-to-business (B2B) scenarios.
-
-The following list describes just some example tasks, business processes, and workloads that you can automate using Azure Logic Apps:
+The following examples describe only a sample of tasks, business processes, and workloads that you can automate with Azure Logic Apps:
 
 * Schedule and send email notifications using Office 365 when a specific event happens, for example, a new file is uploaded.
-
 * Route and process customer orders across on-premises systems and cloud services.
+* Move uploaded files from an SFTP or FTP server to Azure Blob Storage.
+* Monitor social media activity, analyze the sentiment, and create alerts or tasks for items that need review.
 
-* Move uploaded files from an SFTP or FTP server to Azure Storage.
-
-* Monitor tweets, analyze the sentiment, and create alerts or tasks for items that need review.
-
-The following partial example enterprise workflow uses conditions and switches to determine the next action. Suppose you have an order system, and your workflow processes incoming orders. You want to manually review orders above a certain cost. Your workflow already has previous steps that determine how much an incoming order costs. So, you create an initial condition based on that cost value, for example:
+The following example workflow uses conditions and switches to determine the next action. Suppose you have an order system, and your workflow processes incoming orders. You want to manually review orders above a certain cost. Your workflow already has steps that determine the cost from an incoming order. So, you add a condition that compares each order to your cost threshold, for example:
 
 :::image type="content" source="./media/logic-apps-overview/example-enterprise-workflow.png" alt-text="Screenshot shows the workflow designer and a sample enterprise workflow that uses switches and conditions." lightbox="./media/logic-apps-overview/example-enterprise-workflow.png":::
 
+For more information about the logic behind this workflow, see [How logic apps work](#how-logic-apps-work).
+
 > [!TIP]
 >
 > To learn more, you can ask Azure Copilot these questions:
@@ -41,29 +38,27 @@ The following partial example enterprise workflow uses conditions and switches t
 >
 > To find Azure Copilot, on the [Azure portal](https://portal.azure.com) toolbar, select **Copilot**.
 
-If you're ready to try creating your first logic app workflow, see [Get started](#get-started).
-
-To continue learning more, try this video:
+To try creating your first workflow, see [Get started](#get-started). To continue learning more, watch this video:
 
 > [!VIDEO https://learn-video.azurefd.net/vod/player?show=azure-friday&ep=integrate-your-mainframes-and-midranges-with-azure-logic-apps]
 
-For more information, visit [Azure Logic Apps on the Azure website](https://azure.microsoft.com/services/logic-apps) and other [Azure Integration Services](https://azure.microsoft.com/product-categories/integration/).
+For more information, visit [Azure Logic Apps](https://azure.microsoft.com/services/logic-apps) and other [Azure Integration Services](https://azure.microsoft.com/product-categories/integration/) on the Microsoft Azure website.
 
 ## Why use Azure Logic Apps
 
-The Azure Logic Apps platform provides [1,400+ prebuilt connectors](/connectors/connector-reference/connector-reference-logicapps-connectors) that you can use to connect and integrate services, systems, apps, and data. This constantly expanding connector ecosystem helps you reduce the effort around getting access to your resources. Instead, you can focus more on designing and developing the business logic and functionality required for your solutions to meet your company's business needs.
+The Azure Logic Apps platform provides [1,400+ prebuilt connectors](/connectors/connector-reference/connector-reference-logicapps-connectors) that connects and integrates your workflows with various services, systems, apps, and data. This constantly expanding connector ecosystem helps you reduce or eliminate the work required to access your resources. Instead, you can focus more on designing and developing the business logic and functionality required for your solutions to meet your business needs.
 
-To communicate with any service endpoint, run your own code, control your workflow structure, manipulate data, or connect to commonly used services with increased capacity, throughput, and speed, you can use [built-in connector operations](#logic-app-concepts). These operations natively run on the Azure Logic Apps runtime for better performance.
+To communicate with any service endpoint, run your own code, control your workflow structure, manipulate data, or connect to commonly used resources with increased speed, capacity, and throughput, you can use [built-in connector operations](#logic-app-concepts). These operations natively run on the Azure Logic Apps runtime, rather than in Azure, for better performance.
 
-To access and work with resources created and managed using services such as Azure, Microsoft, external web apps and services, or on-premises systems, you can use [Microsoft-managed (Azure-hosted) connector operations](#logic-app-concepts). You can choose from [1,400+ connectors](/connectors/connector-reference/connector-reference-logicapps-connectors), for example:
+To access and work with resources created and managed using services such as Azure, Microsoft, external web apps and services, or on-premises systems, you can use [managed connector operations](#logic-app-concepts). These operations are hosted and run in global, multitenant Azure. You can choose from [1,400+ connectors](/connectors/connector-reference/connector-reference-logicapps-connectors), for example:
 
 * Azure services such as Blob Storage and Service Bus
 * Office 365 services such as Outlook, Excel, and SharePoint
 * Database servers such as SQL and Oracle
 * Enterprise systems such as SAP and IBM MQ
 * File shares such as FTP and SFTP
 
-For more information, see the following documentation:
+For more information, see the following articles:
 
 * [What are connectors in Azure Logic Apps](../connectors/introduction.md)
 * [Built-in connectors](../connectors/built-in.md)
@@ -101,15 +96,7 @@ The following table briefly defines core terminology and concepts in Azure Logic
 | **Managed connector** | This connector or operation type is Microsoft-published, managed, hosted, and run in Azure and is a prebuilt proxy or wrapper for a service or system's REST API, which you can use to access a specific app, data, service, or system. Before you can use most managed connectors, you must first create a connection from your workflow and authenticate your identity. <br><br>For example, you can start your workflow with a trigger or run an action that works with a service such as Office 365, Salesforce, or file servers. For more information, see [Managed connectors for Azure Logic Apps](../connectors/managed.md). |
 | **Integration account** | Create this Azure resource when you want to define and store B2B artifacts for use in your workflows. After you [create and link an integration account](logic-apps-enterprise-integration-create-integration-account.md) to your logic app, your workflows can use these B2B artifacts. Your workflows can also exchange messages that follow Electronic Data Interchange (EDI) and Enterprise Application Integration (EAI) standards. <br><br>For example, you can define trading partners, agreements, schemas, maps, and other B2B artifacts. You can create workflows that use these artifacts and exchange messages over protocols such as AS2, EDIFACT, X12, and RosettaNet. |
 
-## How does Azure Logic Apps differ from Functions, WebJobs, and Power Automate?
-
-All these services help you connect and bring together disparate systems. Each service has their advantages and benefits, so combining their capabilities is the best way to quickly build a scalable, full-featured integration system. For more information, see [Choose between Azure Logic Apps, Azure Functions, Azure WebJobs, and Microsoft Power Automate](../azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md).
-
-## How does Azure Logic Apps differ from Azure Automation Runbooks?
-
-[Azure Automation Runbooks](/azure/automation/automation-runbook-types) provide a lightweight and cost-effective solution for straightforward remediations, such as restarting virtual machines. In contrast, the Azure Logic Apps platform is ideal for automated workflows or orchestrations that involve multiple services, systems, apps, and data. These scenarios also include workloads that run custom code or that require complex logic that uses control structures such as loops, branching, conditions, and more.
-
-## How quickly can I ramp up my solutions with Azure Logic Apps?
+## How fast can I ramp up with Azure Logic Apps?
 
 You can start small with your current systems and services, and then grow incrementally at your own pace. When you're ready, Azure Logic Apps helps you implement and scale up to more mature integration scenarios by providing the following capabilities and benefits.
 
@@ -167,35 +154,40 @@ Azure Logic Apps (Standard) provides the following benefits:
 
 * Increased limits on run duration, storage retention, throughput, HTTP request and response timeouts, message sizes, and custom connector requests. For more information, review [Limits and configuration for Azure Logic Apps](logic-apps-limits-and-config.md).
 
-<a name="how-do-logic-apps-work"></a>
+<a name="how-logic-apps-work"></a>
 
 ## How logic apps work
 
 A logic app workflow always starts with a single [trigger](#logic-app-concepts). The trigger fires when a condition is met, for example, when a specific event happens or when data meets specific criteria. Many triggers include [scheduling capabilities](concepts-schedule-automated-recurring-tasks-workflows.md) that control how often your workflow runs. After the trigger fires, one or more [actions](#logic-app-concepts) run operations that process, handle, or convert data that travels through the workflow, or that advance the workflow to the next step.
 
-Azure Logic Apps implements and uses the "at-least-once" message delivery semantic. Rarely does the service deliver a message more than one time, but no messages are lost. If your business doesn't handle or can't handle duplicate messages, you need to implement *idempotence*, which is the capability to accept identical or duplicate messages, while preserving data integrity and system stability. That way, repeats of the same operation don't change the result after the first execution.
-
-The following section describes the logic for the example enterprise workflow, which is part of an order system where the workflow processes incoming orders. The workflow already has steps that determine how much an incoming order costs. Your goal is to manually review orders above a certain cost, so you create an initial condition based on that cost value, for example:
+Based on the earlier example, the following section explains the logic behind the example workflow, which processes incoming orders for an order system. As a reminder, your goal is to manually review orders above a certain cost. The workflow already has steps that determine the cost from an incoming order. So, you add a condition that compares each order to your cost threshold, for example:
 
 * If the order is below a certain amount, the condition is false. So, the workflow processes the order.
-
 * If the condition is true, the workflow sends an email for manual review. A switch determines the next step.
 
   * If the reviewer approves, the workflow continues to process the order.
-
   * If the reviewer escalates, the workflow sends an escalation email to get more information about the order.
 
     * If the escalation requirements are met, the response condition is true. So, the order is processed.
-
     * If the response condition is false, an email is sent regarding the problem.
 
 :::image type="content" source="./media/logic-apps-overview/example-enterprise-workflow.png" alt-text="Screenshot shows the workflow designer and a sample enterprise workflow that uses switches and conditions.":::
 
+Azure Logic Apps uses the "at-least-once" message delivery semantic. Rarely does the service deliver a message more than one time, but no messages are lost. If your business doesn't handle or can't handle duplicate messages, you need to implement *idempotence*, which is the capability to accept identical or duplicate messages, while preserving data integrity and system stability. That way, repeats of the same operation don't change the result after the first execution.
+
 You can visually create workflows using the Azure Logic Apps workflow designer in the Azure portal or Visual Studio Code. Each workflow also has an underlying definition that uses JavaScript Object Notation (JSON) format. If you prefer, you can edit workflows by changing this JSON definition. For some creation and management tasks, Azure Logic Apps provides Azure PowerShell and Azure CLI command support. For automated deployment, Azure Logic Apps supports Azure Resource Manager templates.
 
 ## Pricing options
 
-Each logic app resource hosting option (multitenant, single-tenant, App Service Environment (ASE) v3, or partially connected environment) has a different [pricing model](logic-apps-pricing.md). For example, multitenant Consumption logic app workflows follow the Consumption pricing model, while single-tenant Standard logic app workflows follow the Standard pricing model. Learn more about [pricing and metering](logic-apps-pricing.md) for Azure Logic Apps.
+Each logic app hosting option (multitenant, single-tenant, App Service Environment (ASE) v3, or partially connected environment) has a different [pricing model](logic-apps-pricing.md). For example, multitenant Consumption logic app workflows follow the Consumption pricing model, while single-tenant Standard logic app workflows follow the Standard pricing model. Learn more about [pricing and metering for Azure Logic Apps](logic-apps-pricing.md).
+
+## How does Azure Logic Apps differ from Functions, WebJobs, and Power Automate?
+
+All these services help you connect and bring together disparate systems. Each service has their advantages and benefits, so combining their capabilities is the best way to quickly build a scalable, full-featured integration system. For more information, see [Choose between Azure Logic Apps, Azure Functions, Azure WebJobs, and Microsoft Power Automate](../azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md).
+
+## How does Azure Logic Apps differ from Azure Automation Runbooks?
+
+[Azure Automation Runbooks](/azure/automation/automation-runbook-types) provide a lightweight and cost-effective solution for straightforward remediations, such as restarting virtual machines. In contrast, the Azure Logic Apps platform is ideal for automated workflows or orchestrations that involve multiple services, systems, apps, and data. These scenarios also include workloads that run custom code or that require complex logic that uses control structures such as loops, branching, conditions, and more.
 
 ## Get started