Managed connectors in Azure Logic Apps

Artikkel
05/31/2022
6 minutter å lese

Managed connectors provide ways for you to access other services and systems where built-in connectors aren't available. You can use these triggers and actions to create workflows that integrate data, apps, cloud-based services, and on-premises systems. Different from built-in connectors, managed connectors are usually tied to a specific service or system such as Office 365, SharePoint, Azure Key Vault, Salesforce, Azure Automation, and so on. Managed by Microsoft and hosted in Azure, managed connectors usually require that you first create a connection from your workflow and authenticate your identity.

For a smaller number of services, systems and protocols, Azure Logic Apps provides a built-in version alongside the managed version. The number and range of built-in connectors vary based on whether you create a Consumption logic app that runs in multi-tenant Azure Logic Apps, or a Standard logic app that runs in single-tenant Azure Logic Apps. In most cases, the built-in version provides better performance, capabilities, pricing, and so on. In a few cases, some built-in connectors are available only in one logic app type, and not the other.

For example, a Standard logic app provides both managed connectors and built-in connectors for Azure Blob, Azure Cosmos DB, Azure Event Hubs, Azure Service Bus, DB2, FTP, MQ, SFTP, and SQL Server, while a Consumption logic app doesn't have the built-in versions. A Consumption logic app provides built-in connectors for Azure API Management, Azure App Services, and Batch, while a Standard logic app doesn't have these built-in connectors. For more information, review the following documentation: Built-in connectors in Azure Logic Apps and Single-tenant versus multi-tenant and integration service environment (ISE).

This article provides a general overview about managed connectors and how they're organized in Consumption logic apps versus Standard logic apps with examples. For technical reference information about each managed connector in Azure Logic Apps, review Connectors reference for Azure Logic Apps.

Managed connector categories

In a Standard logic app, all managed connectors are organized into the Azure group. In a Consumption logic app, managed connectors are organized into the Standard group or Enterprise group. However, pricing for managed connectors works the same in both Standard and Consumption logic apps. For more information, review Trigger and action operations in the Consumption model and Trigger and action operations in the Standard model.

Standard connectors provide access to services such as Azure Blob Storage, Office 365, SharePoint, Salesforce, Power BI, OneDrive, and many more.
Enterprise connectors provide access to enterprise systems, such as SAP, IBM MQ, and IBM 3270 for an additional cost.

Some managed connectors also belong to the following informal groups:

On-premises connectors provide access to on-premises systems such as SQL Server, SharePoint Server, SAP, Oracle DB, file shares, and others.
Integration account connectors help you transform and validate XML, encode and decode flat files, and process business-to-business (B2B) messages using AS2, EDIFACT, and X12 protocols.
Integration service environment connectors and are designed to run specifically in an ISE and provide benefits over their non-ISE versions.

Standard connectors

For a Consumption logic app, this section lists some of the popular connectors in the Standard group. In a Standard logic app, all managed connectors are in the Azure group, but pricing works the same as Consumption logic apps. For more information, review Trigger and action operations in the Standard model.

Azure Blob Storage

Connect to your Azure Storage account so that you can create and manage blob content.

Azure Event Hubs

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.

Azure Queues

Connect to your Azure Storage account so that you can create and manage queues and messages.

Azure Service Bus

Manage asynchronous messages, sessions, and topic subscriptions with the most commonly used connector in Logic Apps.

Azure Table Storage

Connect to your Azure Storage account so that you can create, update, query, and manage tables.

File System

Connect to your on-premises file share so that you can create and manage files.

FTP

Connect to FTP servers you can access from the internet so that you can work with your files and folders.

Office 365 Outlook

Connect to your work or school email account so that you can create and manage emails, tasks, calendar events and meetings, contacts, requests, and more.

Salesforce

Connect to your Salesforce account so that you can create and manage items such as records, jobs, objects, and more.

SharePoint Online

Connect to SharePoint Online so that you can manage files, attachments, folders, and more.

SFTP-SSH

Connect to SFTP servers that you can access from the internet by using SSH so that you can work with your files and folders.

SQL Server

Connect to your SQL Server on premises or an Azure SQL Database in the cloud so that you can manage records, run stored procedures, or perform queries.

Enterprise connectors

For a Consumption logic app, this section lists connectors in the Enterprise group, which can access enterprise systems for an additional cost. In a Standard logic app, all managed connectors are in the Azure group, but pricing is the same as for Consumption logic apps. For more information, review Trigger and action operations in the Standard model.

IBM 3270

SAP

On-premises connectors

Before you can create a connection to an on-premises system, you must first download, install, and set up an on-premises data gateway. This gateway provides a secure communication channel without having to set up the necessary network infrastructure.

For a Consumption logic app, this section lists example Standard connectors that can access on-premises systems. For the expanded on-premises connectors list, review Supported data sources.

SharePoint Server

SQL Server

Teradata

Integration account connectors

Integration account operations specifically support business-to-business (B2B) communication scenarios in Azure Logic Apps. After you create an integration account and define your B2B artifacts, such as trading partners, agreements, maps, and schemas, you can use integration account connectors to encode and decode messages, transform content, and more.

For example, if you use Microsoft BizTalk Server, you can create a connection from your workflow using the on-premises BizTalk Server connector. You can then extend or perform BizTalk-like operations in your workflow by using these integration account connectors.

Consumption logic apps

Before you use any integration account operations in a Consumption logic app, you have to link your logic app to your integration account.
Standard logic apps

Integration account operations don't require that you link your logic app to your integration account. Instead, you create a connection to your integration account when you add the operation to your Standard logic app workflow.

For more information, review the following documentation:

ISE connectors

In an integration service environment (ISE), these managed connectors also have ISE versions, which have different capabilities than their multi-tenant versions:

Note

Logic apps that run in an ISE and their connectors, regardless where those connectors run, follow a fixed pricing plan versus the consumption-based pricing plan. For more information, see Logic Apps pricing model and Logic Apps pricing details.

AS2 ISE

Azure Automation ISE