Revision: Be able to enable OneLake Availability on the follower so the business users can enable it as well as inherit the permissions from the follower rather than the primary.     Problem: Currently, downstream consumers who need to query Eventhouse data via Lakehouse shortcuts must have read access to the primary Eventhouse tables. This creates two main challenges: Security / Governance: Users can access the primary Eventhouse, which may not be desirable. Operational Overhead: Teams must schedule incremental .export commands for each table to provide Lakehouse access, which is cumbersome and difficult to manage at scale.   Proposed Solution: Introduce a feature that allows Eventhouse to automatically export data to Lakehouse shortcuts without requiring users to have read access to the primary tables. Benefits: Downstream consumers can query Lakehouse shortcuts without impacting Eventhouse compute or hitting query limits. Eliminates the need to schedule per-table exports manually. Maintains strict security and governance by preventing direct access to the primary Eventhouse tables. Supports both full and incremental exports, keeping Lakehouse data fresh and up-to-date. ... View more

Eventhouses now support Git Integration, which is a great step forward. But when you look at what actually gets pushed to Git, there is an immediate version control concern: the entire Eventhouse definition is stored as one large .kql file. From a DataOps perspective, this is not ideal. Large monolithic files are difficult to review, hard to merge across teams, and almost always produce noisy diffs. When you look at more mature version controlled artifacts in Fabric, such as Power BI’s move to TMDL or the PBIR format, the direction is clear: break complex assets into smaller, structured, independent files. TMDL separates tables, measures, relationships, expressions, and roles into their own files. PBIR moved away from the single report.json and now stores each page and visual independently. This level of granularity makes teamwork easier, improves change tracking, and strengthens DevOps workflows. Eventhouse should follow the same pattern. Instead of one large script, the service could output a clean directory structure that separates tables, policies, ingestion settings, functions, and materialized views. This would: Make merges safer and easier Let team members work on different components without conflicts Improve the clarity of version history Support more consistent automation and testing patterns If Fabric adopted a multi file structure for Eventhouse artifacts, it would enable stronger collaboration across Power BI and data engineering teams and make Eventhouse a first class citizen in real DataOps workflows. ... View more

As individual teams coming up with AI agents/ Agentic workflows. It would be great to have a shared Kusto MCP server that is maintained/deployed by Kusto team, so that individual teams at microsoft doesnt have to take the code and deploy individual instances. It just adds overhead when it comes to maintenance to get any fixes/upgrades.  @Anshul ... View more

When defining a follower database (or shortcut) in Fabric RTI (Eventhouse), the follower database in Fabric folllows the entire ADX source Database But in ADX when create a data share, which is the similar concept, it's possible to share only certain tables as explained here  https://learn.microsoft.com/en-us/azure/data-explorer/data-share#sharing-tables It will be good to have the same kind of sharing logic for Fabric RTI as we have for ADX : to be aligned in terms of capabilities and have a more granular control of what is to be shared.   ... View more

I'd like the ability to run all queries in a fabric realtime dashboard on a schedule unattended in order to pre-populate the query-results-cache in Kusto so that when i open the dashboard after the scheduled time, queries run much faster ... View more

Eventhouses have a query URI which doesn't contain the name of the eventhouse (e.g. https://trd-k54tu9rfpz168xehtx.z6.kusto.fabric.microsoft.com/). This query URI is used to communicate with the Eventhouse with the SDK or connectors (e.g. Open Telemetry connector).   It is therefore quite possible to have such a URI inside a config file without knowing where (i.e. which workspace / folder) the actual Eventhouse sits (e.g. somebody configured it and left the company since).   The global search currently doesn't work with a query URI, but that would be useful. ... View more

We autoprovision sites around the world that have an eventhub to send us data but we have to have a person use the UI to connect their eventhub to their eventhouse to be used by powerbi for real time intelligence. Please add this functionality to the REST api as we were able to do this function before with ADX admin sdk. copilot suggested dataStreams methods.. POST https://fabric.microsoft.com/v1/workspaces/<workspaceId>/eventhouses/<eventhouseId>/datastreams Content-Type: application/json Authorization: Bearer <your_token> { "name": "MyDataStream", "source": { "type": "EventHub", "namespace": "<your_eventhub_namespace>", "eventHubName": "<your_eventhub_name>", "authentication": { "type": "ConnectionString", "value": "<your_eventhub_connection_string>" } }, "destination": { "type": "Eventhouse", "database": "<your_database_name>", "table": "<your_table_name>" } } we would want to add the format and ingestion mapping to use. ... View more

We have a dataset which for which I am working on a visualization. With incremental refresh, each time I publish a change I have lost historical data. From what I can see there is no way to run refreshes as if I was starting from a past date. If the data I am looking at is all timestamped, I think it would be a great feature to be able to run the queries on different timeframes in order to populate this historical data ... View more

We are concerned that the use of Real-Time Hub data sources results in high CU consumption and that end users may be using them without permission. We would like a feature to restrict access to Real-Time Hub so that end users cannot independently use these data sources to retrieve data from Power BI. We kindly ask for your consideration. ... View more

Azure AI Agent service (preview) allows you to create agents to perform different tasks. These agents can have “knowledge tools” for grounding. At the moment the only knowledge tools available are: Bing search Azure AI search File Search   I don’t know what are your plans, but adding Eventhouse to the knowledge tools may be a good idea As you know almost all DB have vector DB capabilities. I will expect Cosmos and MSSQL to be next to integrate. So Fabric Eventhouse must be integrated as well.  IMHO ... View more

I have several use cases where I want to embed a Real-Time Dashboard with Power BI Embedded which isn't currently supported. ... View more

User creates a Materialized view in EH. Have the ability to make that MV available in OneLake. The workaround is for the the application to copy over the MV on a periodic basis to Onelake. I would like this capability in the platform.  ... View more

At the moment it is possible to assign AllDatabasesAdmin and AllDatabasesViewer to Eventhouse inheriting the Admin or Viewer permission of the workspace, implying that Admin or Viewer role is assigned to all Eventhouse artifacts in the workspace. It would be great if AllDatabasesAdmin and AllDatabasesViewer can be assigned to individual Eventhouse artifacts in the workspace. ... View more

A new technology called query acceleration policies allows for better integration between Delta Lake and KQL, but there are limitations. Currently, real-time processing cannot be done on Delta Lake tables.   In detail, Materialized Views cannot be created on external tables in Delta Lake format, nor can update policies be applied to them.   We suggest enabling Materialized Views and update policies on external Delta Lake tables.   This would help us build Gold Zone tables/views from raw Delta Lake data. ... View more

Currently RTI dashboard supports conditional formatting only in three visual types: table, stat and multi-stat.   We’d like to request a feature enhancement in Real-Time Dashboards that allows us to manually select and define colors for specific graph elements—such as bars, lines, or segments, without relying on conditional rules.   For example, when visualizing the number of devices per type or per category, we’d like to assign specific colors to each group (e.g., green for Type A, blue for Type B) to ensure consistent and meaningful visual representation across all dashboards.   This level of customization would significantly improve clarity and alignment with our internal standards and stakeholder expectations. ... View more

One of the use case of Kusto functions is to abtract underlying table schema/data changes etc. But with the permissions at database level, there is no way to hide/restrict direct usage of tables. Users are able to view all entities (tables, functions etc) within database and able to explore and access. When we change table schema, it may break if they are directly accessing table. It would be good to have security role which restricts at entity level (e.g provide access to function but not tables).    Also in the ADX ideas  ... View more

Parameters are immensely useful. It is OK to refresh them when I open the dashboard. But my preference is that their values would be cached from the preview session and available immediately, so I can choose them quickly, instead of waiting for the full page to render while the cluster is busy answering many other queries.   First show me the previous values, and when you manage to refresh the query that powers the drop down refresh the cache and the drop down values. Just don't make me wait until all the page renders, especially when I am likely to change the parameters and relaunch the page queries.  ... View more

As a Fabric real time dashboard owner, I would like to track usage of my dashboard. Which users loading it, what pages/tiles are they looking at, frequently used parameters, etc. (Copied from Azure Data Explorer dashboard usage telemetry · Community) ... View more

Azure TimeSeries Insights offers a unique UI experience for self-service no-code 'slicing-and-dicing' time series data via sliders and swimming lanes. It even offers advanced options like time-traveling through old and recent data to compare it via the swimming lanes. Unfortunately, TSI will be deprecated very soon. A migration path towards Azure Data Explorer is offered for the data and common UI tools. for the special UI experience, a Kusto Trender UI library is offered but this means a special development team must be assembled to bring back that TSI experience on top of ADX data. So, there is a unique opportunity for Microsoft Fabric to take away this complexity by offering a TSI-like historian experience on top of KQL databases. If you want to have a no-code experience regarding digging into time-series data with an attractive UI so it acts like a historian, upvote this idea! ... View more