Large message support ( 20 MB) for Fabric Event streams — Microsoft Fabric Roadmap

Description

### Large Message Support in Fabric Eventstreams #### Overview Large Message Support enables Fabric Eventstreams to ingest, process, and deliver event payloads up to **20 MB** per message. This removes the need for customers to split, chunk, or pre-process large events before streaming them through Eventstreams. #### Problem Today, Eventstreams enforces a default message size limit of 1 MB. Customers with larger payloads -- such as batched IoT telemetry, enriched event schemas, media metadata, or complex domain events -- must implement workarounds to stay within this constraint. These workarounds add pipeline complexity, increase failure surface, and break downstream schema consistency. #### What's changing With this feature, customers can opt in to a configurable message size ceiling (up to 20 MB) on their Eventstreams. Key aspects: - **Opt-in by design** -- existing Eventstreams are unaffected unless the customer explicitly enables a higher limit. - **Configurable ceiling** -- customers choose the maximum message size aligned to their workload, rather than a one-size-fits-all default. - **No pipeline redesign required** -- sources, transformations, and destinations continue to work as expected. Larger messages flow through the same Eventstream canvas.

📰 Related Blog Article

What’s new in Fabric Eventstream: July–December 2025 updates

🔗 community.fabric.microsoft.com

Change History

2026-09-04

Release Date 2027-03-31 -> 2026-09-30
2026-07-16

Release Date 2026-09-30 -> 2027-03-31
2026-06-22

Feature Description -> ### Large Message Support in Fabric Eventstreams #### Overview Large Message Support enables Fabric Eventstreams to ingest process and deliver event payloads up to **20 MB** per message. This removes the need for customers to split chunk or pre-process large events before streaming them through Eventstreams. #### Problem Today Eventstreams enforces a default message size limit of 1 MB. Customers with larger payloads -- such as batched IoT telemetry enriched event schemas media metadata or complex domain events -- must implement workarounds to stay within this constraint. These workarounds add pipeline complexity increase failure surface and break downstream schema consistency. #### What's changing With this feature customers can opt in to a configurable message size ceiling (up to 20 MB) on their Eventstreams. Key aspects: - **Opt-in by design** -- existing Eventstreams are unaffected unless the customer explicitly enables a higher limit. - **Configurable ceiling** -- customers choose the maximum message size aligned to their workload rather than a one-size-fits-all default. - **No pipeline redesign required** -- sources transformations and destinations continue to work as expected. Larger messages flow through the same Eventstream canvas.
2026-06-19

Roadmap Item Added