{"active":true,"blog_title":"What\u2019s new in Fabric Eventstream: July\u2013December 2025 updates","blog_url":"https://community.fabric.microsoft.com/blog/fbc_fabricupdatesblogs/what%E2%80%99s-new-in-fabric-eventstream-july%E2%80%93december-2025-updates/5172334","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.","feature_description_html":"<h3>Large Message Support in Fabric Eventstreams</h3>\n<h4>Overview</h4>\n<p>Large Message Support enables Fabric Eventstreams to ingest, process, and deliver event payloads up to <strong>20 MB</strong> per message. This removes the need for customers to split, chunk, or pre-process large events before streaming them through Eventstreams.</p>\n<h4>Problem</h4>\n<p>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.</p>\n<h4>What's changing</h4>\n<p>With this feature, customers can opt in to a configurable message size ceiling (up to 20 MB) on their Eventstreams. Key aspects:</p>\n<ul>\n<li><strong>Opt-in by design</strong> -- existing Eventstreams are unaffected unless the customer explicitly enables a higher limit.</li>\n<li><strong>Configurable ceiling</strong> -- customers choose the maximum message size aligned to their workload, rather than a one-size-fits-all default.</li>\n<li><strong>No pipeline redesign required</strong> -- sources, transformations, and destinations continue to work as expected. Larger messages flow through the same Eventstream canvas.</li>\n</ul>","feature_name":"Large message support ( 20 MB) for Fabric Event streams","last_modified":"2026-10-05","product_id":"58cb90aa-4203-ef11-a1fd-000d3a36eea4","product_name":"Real-Time Intelligence","release_date":"Q3 2026","release_item_id":"4dc5810b-2040-f111-88b5-6045bd0066ad","release_status":"Shipped","release_type":"Public preview"}