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/artifact-signing/quickstart.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -277,7 +277,7 @@ To create an identity validation request for an Organization or a DBA:
277
277
| Accuracy | Ensure that you provide the correct information for public identity validation. If you need to make any changes after it's created, you must complete a new identity validation request. This change affects the associated certificates that are being used for signing. |
278
278
| Failed email verification | If email verification fails, you must initiate a new identity validation request. |
279
279
| Identity validation status | You're notified through email when there's an update to the identity validation status. You can also check the status in the Azure portal at any time. |
280
-
| Processing time | Processing your identity validation request takes from 1 to 15 business days (possibly longer if we need to request more documentation from you). |
280
+
| Processing time | Processing your identity validation request takes from 1 to 30 business days (possibly longer if we need to request more documentation from you). |
281
281
| More documentation | If we need more documentation to process the identity validation request, you're notified through email. You can upload the documents in the Azure portal. For documentation upload, there are three attempts. The documentation request email contains information about file size requirements. Ensure that any documents you provide are the most current. <br> - All documents submitted must be issued within the previous 12 months and where the expiration date is a future date that is at least two months away. <br> - If it isn't possible to provide additional documentation, update your account information to match any legal documents already provided or your official Company registration details. <br> - When providing official business document, such as business registration form, business charter, or articles of incorporation that list the company name and address as it is provided at the time of Identity Validation request creation. <br> - Ensure the domain registration or domain invoice from registration or renewal that lists the entity and contact name and all the domains that are included/mentioned in the request.|
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md
+12-19Lines changed: 12 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
-
title: Integration and automation platform options in Azure
2
+
title: Integration and Automation Platform Options in Azure
3
3
description: "Compare Microsoft cloud services that are optimized for integration tasks: Power Automate, Logic Apps, Functions, and WebJobs."
4
4
ms.topic: overview
5
-
ms.date: 02/07/2025
5
+
ms.date: 03/23/2026
6
6
ms.custom: mvc
7
7
#Customer intent: As a developer, I want to understand the choices that Azure offers for hosting and executing my business logic so that I can choose the right set of Azure services.
8
8
---
@@ -21,23 +21,23 @@ All of these services can solve integration problems and automate business proce
21
21
>
22
22
> If you're looking for a more general comparison between Azure Functions and other Azure compute options, see the following articles:
23
23
>
24
-
> -[Criteria for choosing an Azure compute service](/azure/architecture/guide/technology-choices/compute-comparison)
24
+
> -[Choose an Azure compute service](/azure/architecture/guide/technology-choices/compute-comparison)
25
25
> -[Choosing an Azure compute option for microservices](/azure/architecture/microservices/design/compute-options)
26
26
>
27
27
> For a summary and comparison of automation service options in Azure,
28
28
> see [Choose the Automation services in Azure](../automation/automation-services.md).
29
29
30
30
## Compare Azure Logic Apps and Microsoft Power Automate
31
31
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.
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
34
Power Automate empowers business users, office workers, and citizen developers to build simple integrations without 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
38
38
## Compare Azure Functions and Azure Logic Apps
39
39
40
-
These Azure services enable you to build and run serverless workloads. Azure Functions is a serverless compute service, while Azure Logic Apps is a serverless workflow integration platform. Both can create complex *orchestrations*. An orchestration is a collection of functions, which are called *actions* in Azure Logic Apps, that you can run to complete a complex task. For example, to process a batch of orders, you might execute many instances of a function in parallel, wait for all instances to finish, and then execute a function that computes a result on the aggregate.
40
+
These Azure services allow you to build and run serverless workloads. Azure Functions is a serverless compute service, while Azure Logic Apps is a serverless workflow integration platform. Both can create complex *orchestrations*. An orchestration is a collection of functions, which are called *actions* in Azure Logic Apps, that you can run to complete a complex task. For example, to process a batch of orders, you might execute many instances of a function in parallel, wait for all instances to finish, and then execute a function that computes a result on the aggregate.
41
41
42
42
For Azure Functions, you develop orchestrations by writing code and using the [Durable Functions extension](../durable-task/common/what-is-durable-task.md). For Azure Logic Apps, you create orchestrations by using a visual designer or by editing Azure Resource Manager templates.
43
43
@@ -50,7 +50,7 @@ You can mix and match services when you build an orchestration. For example, you
50
50
|**Actions**| Each activity is an Azure function; write code for activity functions |[1,400+ prebuilt connectors with triggers and actions](/connectors/connector-reference/connector-reference-logicapps-connectors)|
51
51
|**Monitoring**|[Azure Application Insights](/azure/azure-monitor/app/app-insights-overview)| - [Azure portal](../logic-apps/view-workflow-status-run-history.md) <br>- [Azure Monitor Logs](../logic-apps/monitor-workflows-collect-diagnostic-data.md) <br>- [Microsoft Defender for Cloud](../logic-apps/healthy-unhealthy-resource.md) <br>- [Azure Application Insights for Standard workflows](/azure/logic-apps/create-single-tenant-workflows-azure-portal#enable-or-open-application-insights-after-deployment) <br>- [Health Check for Standard workflows](/azure/logic-apps/monitor-health-standard-workflows) <br><br>For more information, see [Monitor workflows in Azure Logic Apps](/azure/logic-apps/monitor-logic-apps-overview). |
|**Execution context**| Can run [locally](./functions-kubernetes-keda.md) or in the cloud | Can run in Azure, locally in Visual Studio Code, or in partially connected environments. For more information, see [What is Azure Logic Apps](../logic-apps/logic-apps-overview.md#resource-environment-differences)?|
53
+
|**Execution context**| Can run [locally](./functions-kubernetes-keda.md) or in the cloud | Can run in Azure, locally in Visual Studio Code, or in partially connected environments. For more information, see [What is Azure Logic Apps?](../logic-apps/logic-apps-overview.md#resource-environment-differences)|
54
54
55
55
<aname="function"></a>
56
56
@@ -72,9 +72,9 @@ Azure Functions is built on the WebJobs SDK, so it shares many of the same event
72
72
| --- | --- | --- |
73
73
|**[Serverless app model](https://azure.microsoft.com/solutions/serverless/) with [automatic scaling](event-driven-scaling.md)**|✔||
74
74
|**[Develop and test in browser](./functions-get-started.md)**|✔||
|**[Integration with Logic Apps](functions-twitter-email.md)**|✔||
77
-
|**Trigger events**|[Timer](functions-bindings-timer.md)<br>[Azure Storage queues and blobs](functions-bindings-storage-blob.md)<br>[Azure Service Bus queues and topics](functions-bindings-service-bus.md)<br>[Azure Cosmos DB](functions-bindings-cosmosdb.md)<br>[Azure Event Hubs](functions-bindings-event-hubs.md)<br>[HTTP/WebHook (GitHub, Slack)](functions-bindings-http-webhook.md)<br>[Azure Event Grid](functions-bindings-event-grid.md)|[Timer](functions-bindings-timer.md)<br>[Azure Storage queues and blobs](functions-bindings-storage-blob.md)<br>[Azure Service Bus queues and topics](functions-bindings-service-bus.md)<br>[Azure Cosmos DB](functions-bindings-cosmosdb.md)<br>[Azure Event Hubs](functions-bindings-event-hubs.md)<br>[File system](https://github.com/Azure/azure-webjobs-sdk-extensions/blob/master/src/WebJobs.Extensions/Extensions/Files/FileTriggerAttribute.cs)|
|**Package managers**|npm and NuGet|NuGet<sup>2</sup>|
80
80
@@ -84,7 +84,7 @@ Azure Functions is built on the WebJobs SDK, so it shares many of the same event
84
84
85
85
### Summary
86
86
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.
87
+
Azure Functions offers more developer productivity than Azure App Service WebJobs does. Azure Functions 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
89
Here are two scenarios for which WebJobs might be the best choice:
90
90
@@ -103,17 +103,10 @@ A Power Automate flow can call an Azure Logic Apps workflow. An Azure Logic Apps
103
103
104
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
-
For more information about integration services, see the following articles:
106
+
For more information about integration services, see [Power Automate frequently asked questions](/power-automate/frequently-asked-questions).
107
107
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
-
*[Integrations Made Simple by Charles Lamanna](https://www.biztalk360.com/integrate-2016-resources/integrations-made-simple/)
110
-
*[Azure Logic Apps Live webcast](https://aka.ms/logicappslive)
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments