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/connectors/built-in.md
+58-34Lines changed: 58 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Overview about built-in connectors in Azure Logic Apps
3
-
description: Learn about built-in connectors that run natively to create automated integration workflows in Azure Logic Apps.
2
+
title: Built-in connector overview
3
+
description: Learn about built-in connectors that run natively in Azure Logic Apps.
4
4
services: logic-apps
5
5
ms.suite: integration
6
6
ms.reviewer: estfan, azla
@@ -24,22 +24,46 @@ This article provides a general overview about built-in connectors in Consumptio
24
24
25
25
## Built-in connectors in Consumption versus Standard
26
26
27
-
The following table lists the current and expanding galleries of built-in connectors available for Consumption versus Standard logic app workflows. An asterisk (**\***) marks [service provider-based built-in connectors](../logic-apps/custom-connector-overview.md#service-provider-interface-implementation).
27
+
The following table lists the current and expanding galleries of built-in connectors available for Consumption versus Standard logic app workflows. For Standard workflows, an asterisk (**\***) marks [built-in connectors based on the *service provider* model](#service-provider-interface-implementation), which is described in more detail later.
In Standard logic app workflows, a built-in connector that has the following attributes is informally known as a *service provider*:
39
+
40
+
* Is based on the [Azure Functions extensibility model](../azure-functions/functions-bindings-register.md).
41
+
42
+
* Provides access from a Standard logic app workflow to a service, such as Azure Blob Storage, Azure Service Bus, Azure Event Hubs, SFTP, and SQL Server.
43
+
44
+
Some built-in connectors support only a single way to authenticate a connection to the underlying service. Other built-in connectors can offer a choice, such as using a connection string, Azure Active Directory (Azure AD), or a managed identity.
45
+
46
+
* Runs in the same process as the redesigned Azure Logic Apps runtime.
47
+
48
+
These service provider-based built-in connectors are available alongside their [managed connector versions](managed.md).
49
+
50
+
In contrast, a built-in connector that's *not a service provider* has the following attributes:
51
+
52
+
* Isn't based on the Azure Functions extensibility model.
53
+
54
+
* Is directly implemented as a job within the Azure Logic Apps runtime, such as Schedule, HTTP, Request, and XML operations.
55
+
34
56
<aname="custom-built-in"></a>
35
57
36
58
## Custom built-in connectors
37
59
38
-
For Standard logic apps, if a built-connector isn't available for your scenario, you can create your own built-in connector. You can use the same [*service provider interface implementation*](../logic-apps/custom-connector-overview.md#service-provider-interface-implementation) that's used by service provider-based built-in connectors, such as SQL Server, Service Bus, Blob Storage, Event Hubs, and Blob Storage. This interface implementation is based on the [Azure Functions extensibility model](../azure-functions/functions-bindings-register.md) and provides the capability for you to create custom built-in connectors that anyone can use in Standard logic apps.
60
+
For Standard logic apps, you can create your own built-in connector with the same [built-in connector extensibility model](../logic-apps/custom-connector-overview.md#built-in-connector-extensibility-model) that's used by service provider-based built-in connectors, such as Azure Blob, Azure Event Hubs, Azure Service Bus, SQL Server, and more. This interface implementation is based on the [Azure Functions extensibility model](../azure-functions/functions-bindings-register.md) and provides the capability for you to create custom built-in connectors that anyone can use in Standard logic apps.
61
+
62
+
For Consumption logic apps, you can't create your own built-in connectors, but you create your own managed connectors.
39
63
40
64
For more information, review the following documentation:
41
65
42
-
*[Custom connectors for Standard logic apps](../logic-apps/custom-connector-overview.md#custom-connector-standard)
66
+
*[Custom connectors in Azure Logic Apps](../logic-apps/custom-connector-overview.md#custom-connector-standard)
43
67
*[Create custom built-in connectors for Standard logic apps](../logic-apps/create-custom-built-in-connector-standard.md)
44
68
45
69
<aname="general-built-in"></a>
@@ -120,19 +144,19 @@ You can use the following built-in connectors to perform general tasks, for exam
120
144
:::row-end:::
121
145
:::row:::
122
146
:::column:::
123
-
[![FTP icon][ftp-icon]][ftp-doc]
147
+
![FTP icon][ftp-icon]
124
148
\
125
149
\
126
-
[**FTP**][ftp-doc]<br>(*Standard logic app only*)
150
+
**FTP**<br>(*Standard logic app only*)
127
151
\
128
152
\
129
153
Connect to FTP or FTPS servers you can access from the internet so that you can work with your files and folders.
Connect to SFTP servers that you can access from the internet by using SSH so that you can work with your files and folders.
@@ -145,9 +169,9 @@ You can use the following built-in connectors to perform general tasks, for exam
145
169
146
170
<aname="service-built-in"></a>
147
171
148
-
## Service-based built-in connectors
172
+
## Built-in connectors for specific services and systems
149
173
150
-
Connectors for some services provide both built-in connectors and managed connectors, which might differ across these versions.
174
+
You can use the following built-in connectors to access specific services and systems. In Standard logic app workflows, some of these built-in connectors are also informally known as *service providers*, which can differ from their managed connector counterparts in some ways.
151
175
152
176
:::row:::
153
177
:::column:::
@@ -172,75 +196,75 @@ Connectors for some services provide both built-in connectors and managed connec
172
196
When Swagger is included, the triggers and actions defined by these apps appear like any other first-class triggers and actions in Azure Logic Apps.
Call [Azure-hosted functions](../azure-functions/functions-overview.md) to run your own *code snippets* (C# or Node.js) within your workflow.
223
+
Consume and publish events through an event hub. For example, get output from your logic app with Event Hubs, and then send that output to a real-time analytics provider.
Consume and publish events through an event hub. For example, get output from your logic app with Event Hubs, and then send that output to a real-time analytics provider.
261
+
Connect to your Azure Storage account so that you can create, update, query, and manage tables.
# As a developer, I want learn about the capability to create custom connectors with operations that I can use in my Azure Logic Apps workflows.
10
10
---
11
11
@@ -47,23 +47,15 @@ In [multi-tenant Azure Logic Apps](logic-apps-overview.md), you can create [cust
47
47
48
48
In [single-tenant Azure Logic Apps](logic-apps-overview.md), the redesigned Azure Logic Apps runtime powers Standard logic app workflows. This runtime differs from the multi-tenant Azure Logic Apps runtime that powers Consumption logic app workflows. The single-tenant runtime uses the [Azure Functions extensibility model](../azure-functions/functions-bindings-register.md), which provides a key capability for you to create your own [built-in connectors](../connectors/built-in.md) for anyone to use in Standard workflows. In most cases, the built-in version provides better performance, capabilities, pricing, and so on.
49
49
50
-
When single-tenant Azure Logic Apps officially released, new built-in connectors included Azure Blob Storage, Azure Event Hubs, Azure Service Bus, and SQL Server. Over time, this list of built-in connectors continues to grow. However, if you need connectors that aren't available in Standard logic app workflows, you can [create your own built-in connectors](create-custom-built-in-connector-standard.md) using the same extensibility model that's used by built-in connectors in Standard workflows.
50
+
When single-tenant Azure Logic Apps officially released, new built-in connectors included Azure Blob Storage, Azure Event Hubs, Azure Service Bus, and SQL Server. Over time, this list of built-in connectors continues to grow. However, if you need connectors that aren't available in Standard logic app workflows, you can [create your own built-in connectors](create-custom-built-in-connector-standard.md) using the same extensibility model that's used by *service provider-based*built-in connectors in Standard workflows.
In single-tenant Azure Logic Apps, a built-in connector that has the following attributes is called a *service provider*:
56
+
In single-tenant Azure Logic Apps, a [built-in connector with specific attributes is informally known as a *service provider*](../connectors/built-in.md#service-provider-interface-implementation). For example, these connectors are based on the [Azure Functions extensibility model](../azure-functions/functions-bindings-register.md), which provide the capability for you to create your own custom built-in connectors to use in Standard logic app workflows.
57
57
58
-
* Is based on the [Azure Functions extensibility model](../azure-functions/functions-bindings-register.md).
59
-
60
-
* Provides access from a Standard logic app workflow to a service, such as Azure Blob Storage, Azure Service Bus, Azure Event Hubs, SFTP, and SQL Server.
61
-
62
-
Some built-in connectors support only a single way to authenticate a connection to the underlying service. Other built-in connectors can offer a choice, such as using a connection string, Azure Active Directory (Azure AD), or a managed identity.
63
-
64
-
* Runs in the same process as the redesigned Azure Logic Apps runtime.
65
-
66
-
A built-in connector that's *not a service provider* has the following attributes:
58
+
In contrast, non-service provider built-in connectors have the following attributes:
67
59
68
60
* Isn't based on the Azure Functions extensibility model.
69
61
@@ -206,4 +198,4 @@ This method has a default implementation, so you don't need to explicitly implem
206
198
207
199
When you're ready to start the implementation steps, continue to the following article:
208
200
209
-
*[Create custom built-in connectors for Standard logic apps in single-tenant Azure Logic Apps](create-custom-built-in-connector-standard.md)
201
+
*[Create custom built-in connectors for Standard logic apps in single-tenant Azure Logic Apps](create-custom-built-in-connector-standard.md)
Copy file name to clipboardExpand all lines: articles/logic-apps/single-tenant-overview-compare.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -193,7 +193,7 @@ The single-tenant model and **Logic App (Standard)** resource type include many
193
193
194
194
* Create logic apps and their workflows from [hundreds of managed connectors](/connectors/connector-reference/connector-reference-logicapps-connectors) for Software-as-a-Service (SaaS) and Platform-as-a-Service (PaaS) apps and services plus connectors for on-premises systems.
195
195
196
-
* More managed connectors are now available as built-in connectors in Standard logic app workflows. The built-in versions run natively on the single-tenant Azure Logic Apps runtime. Some built-in connectors are also [*service provider-based* connectors](custom-connector-overview.md#service-provider-interface-implementation). For a list, review the [Built-in connectors for Standard logic apps](#built-connectors-standard) section later in this article.
196
+
* More managed connectors are now available as built-in connectors in Standard logic app workflows. The built-in versions run natively on the single-tenant Azure Logic Apps runtime. Some built-in connectors are also informally known as [*service provider* connectors](../connectors/built-in.md#service-provider-interface-implementation). For a list, review [Built-in connectors in Consumption and Standard](../connectors/built-in.md#built-in-connectors).
197
197
198
198
* You can create your own custom built-in connectors for any service that you need by using the single-tenant Azure Logic Apps extensibility framework. Similar to built-in connectors such as Azure Service Bus and SQL Server, custom built-in connectors provide higher throughput, low latency, and local connectivity because they run in the same process as the single-tenant runtime. However, custom built-in connectors aren't similar to [custom managed connectors](../connectors/apis-list.md#custom-connectors-and-apis), which aren't currently supported. For more information, review [Custom connector overview](custom-connector-overview.md#custom-connector-standard) and [Create custom built-in connectors for Standard logic apps in single-tenant Azure Logic Apps](create-custom-built-in-connector-standard.md).
199
199
@@ -244,7 +244,7 @@ A Standard logic app workflow has many of the same built-in connectors as a Cons
244
244
245
245
For example, a Standard logic app workflow has both managed connectors and built-in connectors for Azure Blob, Azure Cosmos DB, Azure Event Hubs, Azure Service Bus, DB2, FTP, MQ, SFTP, SQL Server, and others. Although a Consumption logic app workflow doesn't have these same built-in connector versions, other built-in connectors such as Azure API Management, Azure App Services, and Batch, are available.
246
246
247
-
In single-tenant Azure Logic Apps, [built-in connectors with specific attributes are informally known as *service providers*](custom-connector-overview.md#service-provider-interface-implementation). Some built-in connectors support only a single way to authenticate a connection to the underlying service. Other built-in connectors can offer a choice, such as using a connection string, Azure Active Directory (Azure AD), or a managed identity. All built-in connectors run in the same process as the redesigned Azure Logic Apps runtime. For more information, review the [built-in connector list for Standard logic app workflows](../connectors/built-in.md).
247
+
In single-tenant Azure Logic Apps, [built-in connectors with specific attributes are informally known as *service providers*](../connectors/built-in.md#service-provider-interface-implementation). Some built-in connectors support only a single way to authenticate a connection to the underlying service. Other built-in connectors can offer a choice, such as using a connection string, Azure Active Directory (Azure AD), or a managed identity. All built-in connectors run in the same process as the redesigned Azure Logic Apps runtime. For more information, review the [built-in connector list for Standard logic app workflows](../connectors/built-in.md#built-in-connectors).
0 commit comments