Eventstream MQTT broker source: V3.1.1 support
The Eventstream MQTT broker source supports connections with public MQTT brokers that offer MQTT V5 support. Please offer support for V3.1.1 too, because this is still a valid and widely used version (perhaps still even more than V5). Regarding version V3.1 (which is different from V3.1.1), this one seems to be deprecated by now.
Get data from Apache Kafka topics via private networking
Current prerequisites limit to public Kafka instances which is not feasible for most enterprise customers. When will this limitation be lifted so that it can be used in private network setups, for example via gateway? https://learn.microsoft.com/en-gb/fabric/real-time-intelligence/event-streams/add-source-apache-kafka#prerequisitesImprove CI/CD consistency for Microsoft Fabric Real-Time Intelligence Eventstreams
Microsoft Fabric Real-Time Intelligence has made strong progress with Git integration and deployment pipelines, but lifecycle management can still be inconsistent across Eventstream sources, destinations, connections, and deployment scenarios. I would like to see more consistent CI/CD support across Real-Time Intelligence artifacts, including automated environment-specific connection rebinding, easier promotion from development to test and production, deployment validation before activation, and clearer diagnostics when an RTI artifact cannot be promoted successfully. For enterprise implementations, it would also be valuable to reduce the amount of manual reconfiguration required after deployment. Improving these capabilities would make Real-Time Intelligence solutions easier to operationalize, govern, automate, and teach as production-ready architectures rather than solutions that require manual configuration between environments.
RLS mismatch when assigning multiple regions in semantic model live connection.
Hello Community, I am facing an issue with Row-Level Security (RLS) in a Power BI report connected to a semantic model (live connection). I created RLS roles based on region-wise access. When I assign a user access to a single region (e.g., Brazil), the data displays correctly. However, when I assign the same user access to an additional region, the data for the first region starts showing mismatches. The formulas are correct, and the user has all required data permissions. Interestingly, if I give the user Contributor or Admin access at the workspace level, they can see all regions correctly. But the requirement is that the user should only have Viewer access, not workspace-level permissions. Has anyone faced this issue before? Is there a way to fix this so that users with Viewer access can see multiple regions correctly without needing workspace-level roles? Thanks in advance for your guidance!
Native OTLP/Protobuf Support in Fabric Event Streams
As a data engineer, I need Fabric Event Streams to accept OTLP/Protobuf payloads natively so that I can stream high-frequency observability and sensor data without format conversion overhead. Given an OpenTelemetry collector or agent emitting OTLP/Protobuf (the industry standard OTel wire format) When that collector sends data directly to a Fabric Event Streams endpoint Then Event Streams should decode and ingest the OTLP/Protobuf payload directly into the stream, without requiring intermediate transformation or format conversion Use Cases 1. Industrial IoT & Energy Monitoring Sensors/devices emit OTLP/Protobuf via sparkplug to minimize bandwidth Today: Must convert OTLP/Protobuf → JSON before Event Streams, adding 30-40% overhead and latency Benefit: Native ingestion eliminates transformation; real-time stream processing at lower cost 2. Microservices Observability Pipeline OTel collectors emit OTLP/Protobuf natively; teams want to stream traces/metrics to Fabric for correlation and ML Today: Custom decoders or third-party tools required to bridge OTel → Event Streams Benefit: Native support enables seamless OTel → Event Streams → Lakehouse pipelines 3. Edge-to-Cloud Event Streaming Edge gateways and devices emit OTLP/Protobuf to conserve bandwidth; need to stream to cloud for aggregation Today: Protobuf efficiency is lost in format conversion to Event Streams Benefit: Preserves bandwidth savings across the full pipeline; validates Fabric for edge architectures Business & Priority Justification OTel is Industry Standard: CNCF project, adopted by AWS, Google, Azure—Event Streams should be a native destination Competitive Gap: Rivals already support OTel streaming; Fabric risks being seen as outdated Performance: Native protobuf saves 40-60% bandwidth vs. JSON; direct ROI for high-volume users Ecosystem Lock-in: Early support captures OTel-first teams before they choose alternatives Sources: Fabric Eventstream: Supported Data Formats Parse Protobuf - Azure Stream AnalyticsAdd HTTP REST / Webhook source and destination to Eventstream
At this moment, Eventstream has no support for ingesting messages via HTTP REST / Webhook (like an Azure Function HTTP trigger). The same goes for egress to an HTTP REST / Webhook endpoint. Supporting these endpoints opens many possibilities to integrate directly with external platforms, in real-time.
Add/Enhance CustomCode Transformation Node (JavaScript / .NET) in Fabric Eventstream
Add a new Transform CustomCode node in Eventstreams that lets users author and run sandboxed JavaScript or .NET code as a streaming transformation step—similar in UX placement to existing transformations and the SQL operator, but designed for arbitrary code logic.
