Eventstream connection with Event Hub
Hello, I have an existing event hub which I'm planning to use with an eventstream in Fabric. I see two connection options: 1. SAS keys 2. Organisational account I'm in a microsoft internal team and we're not allowed to use SAS keys. When I try to use my own account via organisational account option I'm getting following error Sign in failed with the following error code: "invalid_request". Error description given: "AADSTS65002: Consent between first party application 'b52893c8-bc2e-47fc-918b-77022b299bbc' and first party resource '80369ed6-5f11-4dd9-bef3-692475845e77' must be configured via preauthorization - applications owned and operated by Microsoft must get approval from the API owner before requesting tokens for that API. Trace ID: 3e344c2e-4ab0-442d-af25-23f3e1c15500 Correlation ID: 18583d2a-007b-4b7a-a7d0-5485087e55c7 Timestamp: 2025-07-29 16:05:32Z" (Session ID: f67ac96c-b700-4aed-8514-2b9acd5b00c8, Region: usfr) I'm wondering how to solve this and also is there any support to use Managed Identities for auth? This is normally possible but I don't see how via Microsoft Fabric.
Options for High‑Frequency, Low‑Latency API Ingestion
I’m looking for guidance on options for invoking external APIs(with dynamic date parameters in specific format like '202602152359') at very high frequency (every 2 minutes or less) and making the data available with minimal end‑to‑end latency. Requirements: Invoke external APIs at 2‑minute intervals (or less). Parse incoming XML/JSON data into structured tables. Refresh user reports/streamlit dashboards quickly, alongside other enterprise data, to support near‑real‑time decision‑making wihtout the delay of sql endpoint refresh. We currently use a Fabric medallion architecture with payload based ingestions. However, this approach is not well‑suited for this use case, as running pipelines/notebooks on 2–5 minute schedules is triggering 70% Fabric capacity alerts.
Deserialization error when publishing events to Eventstream via Event Grid after initial success
Hi, I’m trying to ingest events into Microsoft Fabric Eventstream using Azure Event Grid and ran into an issue that I’m unable to understand. Here’s what I did step by step: I created an Event Grid Namespace, followed by a custom Topic. In Fabric Eventstream, I configured a Custom Source by selecting the Event Grid namespace and topic. From the Azure portal, I noted down the topic endpoint and access key. Using Azure Cloud Shell, I started publishing events to the Event Grid topic. Initially, my plan was to ingest 10 events at once, but that didn’t work. So I changed the approach and started publishing the events one by one. This is where the issue started, the first two events were published and consumed by Eventstream successfully.When I tried to publish the third event, Eventstream threw a deserialization error.Despite that, only the third event (and subsequent ones) fail with a deserialization issue. What’s confusing is that the schema is exactly the same for all events and I followed the same steps, used the same format, and didn’t change anything between events. Has anyone faced a similar issue when publishing events from Event Grid to Fabric Eventstream? What could cause deserialization? Any known limitations or best practices for publishing events via Event Grid to Eventstream? Thank YouDeleted workspace still showing CU usage in Capacity Metrics (Eventstream)
Hi all, We deleted a workspace, but the Fabric Capacity Metrics app still shows CU usage for that workspace, and the top consumer listed is an Eventstream. What’s confusing is that Eventstream doesn’t appear in the supported item types for Item Recovery, so it seems like a non‑recoverable item. https://learn.microsoft.com/en-us/fabric/admin/retention-recovery#supported-item-types So why would it still show up as consuming CUs after the workspace was deleted? Is this expected because a deleted workspace stays in workspace retention for a period before it’s permanently removed? If yes, what’s the correct way to stop the CU usage, do we need to permanently delete the workspace from the admin portal during the retention window? Thanks, Shreya
