---
id: post/demiliani-com/12002
type: post
title: "Azure Logic Apps: are you handling large blobs? Keep memory usage under control."
summary: Handling large blob files in Azure Logic Apps for Dynamics 365 Business Central integration can cause excessive memory usage because built-in connectors load all data into memory. To prevent out-of-memory exceptions, monitor workflow concurrency, ensure 64-bit platform settings, and delegate large file processing to Azure Functions or inline code.
tier: community
language: en
tags:
  - azure logic apps
  - blob storage
  - memory optimization
  - large files
  - serverless
  - connectors
  - performance
  - integration
system: integration
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:01:32.331Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: 37770fe1baf760f38da1a0732cacc1ac4d1b37c051f6fed66551d17c4ecf5f56
evidence:
  - kind: blog
    url: https://demiliani.com/2025/06/25/azure-logic-apps-are-you-handling-large-blobs-keep-memory-usage-under-control/
    title: "Azure Logic Apps: are you handling large blobs? Keep memory usage under control."
    date: "2025-06-25"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://demiliani.com/2025/06/25/azure-logic-apps-are-you-handling-large-blobs-keep-memory-usage-under-control/
    title: "Azure Logic Apps: are you handling large blobs? Keep memory usage under control."
    date: "2025-06-25"
    commit: null
    t: null
    quote: The built-in connectors load all the informations into memory by design.
  - kind: blog
    url: https://demiliani.com/2025/06/25/azure-logic-apps-are-you-handling-large-blobs-keep-memory-usage-under-control/
    title: "Azure Logic Apps: are you handling large blobs? Keep memory usage under control."
    date: "2025-06-25"
    commit: null
    t: null
    quote: Usually the built-in version of a connector provides better performance than the managed counterpart, so it's why they are proposed as default.
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "12002"
source_id: demiliani-com
source_name: Stefano Demiliani
url: https://demiliani.com/2025/06/25/azure-logic-apps-are-you-handling-large-blobs-keep-memory-usage-under-control/
published_at: "2025-06-25T14:19:13.000Z"
author: Stefano Demiliani
full_text: false
words: 779
quotes:
  - text: The built-in connectors load all the informations into memory by design.
    why_it_matters: Explains the root cause of memory issues when processing large blobs in Logic Apps workflows
  - text: Usually the built-in version of a connector provides better performance than the managed counterpart, so it's why they are proposed as default.
    why_it_matters: Shows the trade-off between performance and memory usage when choosing connector types
code_objects_mentioned: []
systems:
  - integration
versions_mentioned: []
preview:
  embeddable: true
  frame_url: https://demiliani.com/2025/06/25/azure-logic-apps-are-you-handling-large-blobs-keep-memory-usage-under-control/embed/
  image: https://demiliani.com/wp-content/uploads/2025/06/logicappshighmemoryusage_01a.png
  image_alt: null
  image_w: 649
  image_h: 317
  site_name: Stefano Demiliani
  favicon: https://demiliani.com/wp-content/uploads/2022/09/sd_wordpress_logo.png?w=32
  probed_at: "2026-10-07T11:52:01.055Z"
---

# Azure Logic Apps: are you handling large blobs? Keep memory usage under control.

[Read the post](https://demiliani.com/2025/06/25/azure-logic-apps-are-you-handling-large-blobs-keep-memory-usage-under-control/) · Stefano Demiliani (Stefano Demiliani, MVP) · 2025-06-25 · 779 words · tier community · reviewed (checked by Opus)

> Handling large blob files in Azure Logic Apps for Dynamics 365 Business Central integration can cause excessive memory usage because built-in connectors load all data into memory. To prevent out-of-memory exceptions, monitor workflow concurrency, ensure 64-bit platform settings, and delegate large file processing to Azure Functions or inline code.

## Key points

- Built-in Azure Logic Apps connectors load entire files into memory, causing high memory consumption with large blobs
- Logic Apps Standard in WS1 plan (3.5 GB total) can run out of memory when processing multiple large files or concurrent executions
- Solutions include monitoring workflow concurrency, verifying 64-bit platform configuration, and delegating file processing to Azure Functions
- Using Azure Functions or inline code functions significantly improves performance and memory efficiency for large file handling

## Quotes

- "The built-in connectors load all the informations into memory by design." (Explains the root cause of memory issues when processing large blobs in Logic Apps workflows)
- "Usually the built-in version of a connector provides better performance than the managed counterpart, so it's why they are proposed as default." (Shows the trade-off between performance and memory usage when choosing connector types)

## Context

- Features: Blob Storage connector, built-in connectors, managed connectors, Azure Functions integration, workflow concurrency monitoring, inline code functions

Source: Stefano Demiliani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.