Built-In vs. Managed Connectors in Azure Logic Apps: Step-by-Step Guide

Azure Logic Apps provides an incredible way to seamlessly integrate workflows with various apps, services, and platforms. One of its most powerful features is connectors, which allow you to interact with data and resources without writing code. However, there are two types of connectors: built-in and managed. Let’s talk about the differences in when to use each, and some popular examples to help you get started.

1. What are Connectors in Azure Logic Apps?

Connectors are like the "bridges" that link Azure Logic Apps to other applications, services, or platforms. They allow workflows to interact with external systems using prebuilt operations (that is, triggers or actions).

• Trigger: Starts the workflow.

• Action: Performs tasks after the trigger fires.

For example, a connector can start your workflow when a new email arrives (trigger) and then save the attachment to OneDrive (action).

Many connectors include both triggers and actions, but some provide only triggers, while others are limited to actions.

2. The Two Types of Connectors

Azure Logic Apps offers two types of connectors:

Built-In Connectors

• Run directly and natively inside Azure Logic Apps.

• Do not require additional Azure-hosted services.

• Often provide better performance because they operate within the Azure Logic Apps runtime.

• Examples: Recurrence trigger, HTTP action, and Azure Blob Storage operations.

Managed Connectors

• Hosted, deployed, and managed by Microsoft in Azure.

• Act as proxies or wrappers for APIs of underlying services.

• Require authentication to connect with third-party platforms.

• Examples: Office 365, Salesforce, and Twitter.

3. Key Differences Between Built-In and Managed Connectors

4. When to Use Each Connector Type

Use Built-In Connectors When:

• Your workflow interacts with Azure services, such as Blob Storage or Functions.

• You need operations to run faster and directly within Azure Logic Apps.

• You’re working on simple workflows that don’t rely on external platforms.

Use Managed Connectors When:

• Your workflow integrates with third-party apps like Outlook, Salesforce, or Twitter.

• You need prebuilt connectors for external services.

• You’re okay with slightly higher latency due to external service calls.

5. Popular Examples of Connectors

Built-In Connectors

• Recurrence Trigger: Start workflows on a schedule.

• HTTP Action: Send HTTP requests to external APIs.

• Azure Blob Storage: Upload, retrieve, or delete files from Azure storage.

Managed Connectors

• Outlook: Send or receive emails as part of a workflow.

• Salesforce: Retrieve or update CRM data.

• Twitter: Post tweets or monitor hashtags for specific actions.

6. Choosing the Right Connector for Your Workflow

1. What platform are you connecting to?

2. How complex is the workflow?

3. What’s your budget?

7. Step-by-Step Example: Using Connectors in a Workflow

Scenario: Automate File Storage and Notifications

Objective: Move email attachments to Azure Blob Storage and notify your team in Microsoft Teams.

1. Choose a trigger Connector): Use the Outlook connector to start the workflow when a new email arrives.

2. Add an action(Built-In Connector): Add an action to save the email attachment to Azure Blob Storage.

3. Add a Notification (Managed Connector): Use the Team's connector to send a message notifying your team about the uploaded file.

Summary

Connectors are the foundation of Azure Logic Apps workflows. Whether built-in or managed, they enable seamless integration across platforms and services.

• Built-In Connectors: Best for Azure services and performance-driven tasks.

• Managed Connectors: Perfect for third-party service integration.

By understanding these options, you can design workflows that are efficient, cost-effective, and tailored to your specific needs. Which connector do you use the most in your workflows? Share your thoughts below! 🌟