Azure Logic Apps: Built-in vs Managed Azure Blob Storage Connector.

When creating workflows with Azure Logic Apps that uses the Azure Blob Storage Connector, you have the possibility to select the built-in or the managed version of such connector.

A connector provides one or more prebuilt operations, which you use as steps in your workflow. Each operation is either a trigger condition that starts a workflow or a subsequent action that performs a specific task, along with properties that you can configure.

Built-in connectors are designed to run directly and natively inside Azure Logic Apps runtime, while Managed connectors are deployed, hosted, and managed in Azure.

In my past sessions about Azure Logic Apps and high-performance workflows I’ve talked a lot about the differences between these two types of connectors and their implications on perfortmance of your solution. But sometimes, there are also functional differences that you need to know between a built-in and a managed connector, and the Azure Blob Storage Connector is exactly one of those.

Last week I talked with a partner that moved a workflow from a Consumption to a Standard Azure Logic App. This workflow had the Azure Blob Storage Connector When a blob is added or modified as trigger and they have some unexpected problems when running the workflow due to the wrong selection of the connector type.

When creating such workflow with the Azure Blob Storage Connector as trigger, you can choose between the built-in and the managed connector versions:

But what happens if you are not careful on selecting the righ connector type in this case?

Azure Blob Storage connector has a different behavior (not well documented) between the built-in and the managed version. Here are the differences that you need to know:

Azure Blob Storage built-in connector:

• When triggered, it processes all the existing blobs the first time it’s executed. Then for all subsequent runs, it processes any blobs that are added or updated, including in existing subfolders. 

Azure Blob Storage managed connector:

• When triggered, it processes all the files that are added or modified in a given container. It ignores all the existing files and also it ignores existing subfolders (works only in the root folder).

From a security perspective, there’s also another difference that impacts built-in vs managed connectors. If your Azure Logic App workflow runs from within a virtual network (VNet), remember that managed connectors run on shared clusters , so the workflow execution will be outside of the VNet.

Instead, built-in connectors run on the same cluster as the Azure Logic App, so their execution will be in the same VNET as the Logic App.

Be careful on these differences, because sometimes they can have an impact in your final workflow.

After sharing this with you, I wish everyone a wonderful August 15th. Enjoy the barbecue

Original Post https://demiliani.com/2025/08/15/azure-logic-apps-built-in-vs-managed-azure-blob-storage-connector/