You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ All of these services can solve integration problems and automate business proce
31
31
32
32
These services are both *designer-first* integration platforms where you can build and run automated workflows. Both platforms integrate with various Software-as-a-Service (SaaS) and enterprise applications. Both provide similar workflow designers, and while [their connectors share some overlap](/connectors/connector-reference/), each platform also offers their own unique connectors.
33
33
34
-
Power Automate empowers business users, office workers, and citizen developers to build simple integrations, such as an approval workflow for a SharePoint document library, without having to work with IT or developers or to write code. Azure Logic Apps supports integrations ranging from little-to-no-code scenarios to more advanced, codeful, and complex workflows, such as B2B processes or those that require enterprise-level interactions with Azure DevOps. A business workflow can also grow from simple to complext over time.
34
+
Power Automate empowers business users, office workers, and citizen developers to build simple integrationswithout having to work with IT or developers or to write code. One example might be an approval workflow for a SharePoint document library. Azure Logic Apps supports integrations ranging from little-to-no-code scenarios to more advanced, codeful, and complex workflows. Examples include B2B processes or scenarios that require enterprise-level interactions with Azure DevOps. A business workflow can also grow from simple to complete over time.
35
35
36
36
To help you determine whether you want to use Azure Logic Apps or Power Automate for a specific integration, see the [Capability comparison table](/azure/logic-apps/power-automate-migration#compare-capability-details).
37
37
@@ -41,7 +41,7 @@ These Azure services enable you to build and run serverless workloads. Azure Fun
41
41
42
42
For Azure Functions, you develop orchestrations by writing code and using the [Durable Functions extension](durable/durable-functions-overview.md). For Azure Logic Apps, you create orchestrations by using a visual designer or by editing Azure Resource Manager templates.
43
43
44
-
You can mix and match services when you build an orchestration, such as calling functions from logic app workflows and calling logic app workflows from functions. Choose how to build each orchestration based on the services' capabilities or your personal preference. The following table lists some key differences between these services:
44
+
You can mix and match services when you build an orchestration. For example, you can call functions from logic app workflows and call logic app workflows from functions. Choose how to build each orchestration based on the services' capabilities or your personal preference. The following table lists some key differences between these services:
45
45
46
46
|| Durable Functions | Azure Logic Apps |
47
47
| --- | ----------------- | ---------------- |
@@ -86,12 +86,12 @@ Azure Functions is built on the WebJobs SDK, so it shares many of the same event
86
86
87
87
Azure Functions offers more developer productivity than Azure App Service WebJobs does. It also offers more options for programming languages, development environments, Azure service integration, and pricing. For most scenarios, it's the best choice.
88
88
89
-
Here are two scenarios for which WebJobs may be the best choice:
89
+
Here are two scenarios for which WebJobs might be the best choice:
90
90
91
-
* You need more control over the code that listens for events, the `JobHost` object. Functions offers a limited number of ways to customize `JobHost` behavior in the [host.json](functions-host-json.md) file. Sometimes you need to do things that can't be specified by a string in a JSON file. For example, only the WebJobs SDK lets you configure a custom retry policy for Azure Storage.
91
+
* You need more control over the code that listens for events, the `JobHost` object. Functions offers a limited number of ways to customize `JobHost` behavior in the [host.json](functions-host-json.md) file. Sometimes you need to do things that you can't specify by using a string in a JSON file. For example, only the WebJobs SDK lets you configure a custom retry policy for Azure Storage.
92
92
* You have an App Service app for which you want to run code snippets, and you want to manage them together in the same Azure DevOps environment.
93
93
94
-
For other scenarios where you want to run code snippets for integrating Azure or third-party services, choose Azure Functions over WebJobs with the WebJobs SDK.
94
+
For other scenarios where you want to run code snippets for integrating Azure or external services, choose Azure Functions over WebJobs with the WebJobs SDK.
95
95
96
96
<aname="together"></a>
97
97
@@ -101,13 +101,13 @@ You don't have to choose just one of these services. They integrate with each ot
101
101
102
102
A Power Automate flow can call an Azure Logic Apps workflow. An Azure Logic Apps workflow can call a function in Azure Functions, and vice versa. For example, see [Create a function that integrates with Azure Logic Apps](functions-twitter-email.md).
103
103
104
-
Between Power Automate, Logic Apps, and Functions, the integration experience between these services continues to improve over time. You can build a component in one service and use that component in the other services.
104
+
Between Power Automate, Azure Logic Apps, and Functions, the integration experience between these services continues to improve over time. You can build a component in one service and use that component in the other services.
105
105
106
-
You can get more information on integration services by using the following links:
106
+
For more information about integration services, see the following articles:
107
107
108
108
*[Leveraging Azure Functions & Azure App Service for integration scenarios by Christopher Anderson](https://www.biztalk360.com/integrate-2016-resources/leveraging-azure-functions-azure-app-service-integration-scenarios/)
109
109
*[Integrations Made Simple by Charles Lamanna](https://www.biztalk360.com/integrate-2016-resources/integrations-made-simple/)
110
-
*[Logic Apps Live webcast](https://aka.ms/logicappslive)
110
+
*[Azure Logic Apps Live webcast](https://aka.ms/logicappslive)
0 commit comments