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
+31-17Lines changed: 31 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.suite: integration
6
6
ms.reviewer: estfan, azla
7
7
ms.topic: conceptual
8
8
ms.custom: engagement-fy23
9
-
ms.date: 04/15/2024
9
+
ms.date: 12/18/2024
10
10
---
11
11
12
12
# Built-in connectors in Azure Logic Apps
@@ -25,11 +25,11 @@ This article provides a general overview about built-in connectors in Consumptio
25
25
26
26
## Built-in connectors in Consumption versus Standard
27
27
28
-
The following table lists the current and expanding galleries of built-in connectors available for Consumption versus Standard 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.
28
+
The following table lists the current and expanding galleries of built-in operations collections available for Consumption versus Standard 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.
@@ -153,7 +153,7 @@ You can use the following built-in connectors to access specific services and sy
153
153
:::column-end:::
154
154
:::column:::
155
155
[![Azure API Management icon][azure-api-management-icon]][azure-api-management-doc]
156
-
<br><br>[**Azure API Management**][azure-api-management-doc]<br>(*Consumption workflow only*)
156
+
<br><br>[**Azure API Management**][azure-api-management-doc]
157
157
<br><br>Call your own triggers and actions in APIs that you define, manage, and publish using [Azure API Management](../api-management/api-management-key-concepts.md). <br><br>**Note**: Not supported when using [Consumption tier for API Management](../api-management/api-management-features.md).
158
158
:::column-end:::
159
159
:::column:::
@@ -197,7 +197,7 @@ You can use the following built-in connectors to access specific services and sy
<br><br>**Chunk text**: Split up content into pieces to use in AI solutions or with AI service operations such as [Azure OpenAI and Azure AI Search operations](../logic-apps/connectors/azure-ai.md). For more information, see [Parse or chunk content](../logic-apps/parse-document-chunk-text.md).
361
364
<br><br>**Compose**: Create a single output from multiple inputs with various types.
362
365
<br><br>**Create CSV table**: Create a comma-separated-value (CSV) table from an array with JSON objects.
363
366
<br><br>**Create HTML table**: Create an HTML table from an array with JSON objects.
364
367
<br><br>**Filter array**: Create an array from items in another array that meet your criteria.
365
368
<br><br>**Join**: Create a string from all items in an array and separate those items with the specified delimiter.
369
+
<br><br>**Parse a document**: Create a tokenized string to use in AI solutions or with AI service operations such as [Azure OpenAI and Azure AI Search operations](../logic-apps/connectors/azure-ai.md). For more information, see [Parse or chunk content](../logic-apps/parse-document-chunk-text.md).
366
370
<br><br>**Parse JSON**: Create user-friendly tokens from properties and their values in JSON content so that you can use those properties in your workflow.
367
371
<br><br>**Select**: Create an array with JSON objects by transforming items or values in another array and mapping those items to specified properties.
368
372
:::column-end:::
369
373
:::column:::
370
-
![Date Time action icon][date-time-icon]
374
+
![Date Time icon][date-time-icon]
371
375
<br><br>**Date Time**
372
376
<br><br>Perform operations with timestamps.
373
377
<br><br>**Add to time**: Add the specified number of units to a timestamp.
@@ -378,7 +382,7 @@ Azure Logic Apps provides the following built-in actions for working with data o
378
382
<br><br>**Subtract from time**: Subtract a number of time units from a timestamp.
Copy file name to clipboardExpand all lines: articles/logic-apps/custom-connector-overview.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
@@ -15,7 +15,7 @@ ms.date: 01/04/2024
15
15
16
16
Without writing any code, you can quickly create automated integration workflows when you use the prebuilt connector operations in Azure Logic Apps. A connector helps your workflows connect and access data, events, and actions across other apps, services, systems, protocols, and platforms. Each connector offers operations as triggers, actions, or both that you can add to your workflows. By using these operations, you expand the capabilities for your cloud apps and on-premises apps to work with new and existing data.
17
17
18
-
Connectors in Azure Logic Apps are either *built in* or *managed*. A *built-in* connector runs natively on the Azure Logic Apps runtime, which means they're hosted in the same process as the runtime and provide higher throughput, low latency, and local connectivity. A *managed connector* is a proxy or a wrapper around an API, such as Office 365 or Salesforce, that helps the underlying service talk to Azure Logic Apps. Managed connectors are powered by the connector infrastructure in Azure and are deployed, hosted, run, and managed by Microsoft. You can choose from [hundreds of managed connectors](/connectors/connector-reference/connector-reference-logicapps-connectors) to use with your workflows in Azure Logic Apps.
18
+
Connectors in Azure Logic Apps are either *built in* or *managed*. A *built-in* connector runs natively on the Azure Logic Apps runtime, which means they're hosted in the same process as the runtime and provide higher throughput, low latency, and local connectivity. A *managed connector* is a proxy or a wrapper around an API, such as Office 365 or Salesforce, that helps the underlying service talk to Azure Logic Apps. Managed connectors are powered by the connector infrastructure in Azure and are deployed, hosted, run, and managed by Microsoft. You can choose from [1,400+ managed connectors](/connectors/connector-reference/connector-reference-logicapps-connectors) to use with your workflows in Azure Logic Apps.
19
19
20
20
When you use a connector operation for the first time in a workflow, some connectors don't require that you create a connection first, but many other connectors require this step. Each connection that you create is actually a separate Azure resource that provides access to the target app, service, system, protocol, or platform.
0 commit comments