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

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

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

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

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

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

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

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

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

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

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

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

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

Please allow to derive a value out of a complex JSON which is stored in a single field in your stream ... View more

It would be great if you can define Create/Update/Delete actions from Event Processing. So depending of a field you can say i.e. "if this is field contains "delete" it's a delete operation, use the ID stored in field ID to identify the record to be deleted in your lakehouse". Same with Updates and Inserts. That would be super helpful to have a table which always contains the latest version of a record. This would be i.e. a great help when you receive events from D365 which can be new records, updates or deletes. ... View more

Hi, I think that it could be very useful to see the component columns when a KQL materialized view is created, in the KQL databases explorer. I can see the columns of a table and not of a materialized view. Also it could be very useful seeing the related data types. Thanks ... View more

Provide continuous ingestion from OneLake. ... View more

[This is a personal wish for a project I am working on; trying to see whether there's similar community interest in this] I'm looking for four distinct improvements in the "Map" visual for KQL: Have the map emit its lat/lon corners (upper left, lower right) into parameter values so that I can restrict a query with them. I have a LOT of data in some dashboards and restricting by region would be very useful, so that the results in an adjacent visual track my restriction in the map, i.e. I zoom into an area and the list next to the map is constrained to what's in that area. Have a setting that will keep the map at whatever position and zoom level the user did set it to, rather than the map resetting on refresh to include all items in the refreshed result set. Have a tiny little tooltip on each bubble that is permanently visible so that I can, for instance, label a bus. Have repeatability on which bubble for which item gets which color (and shape?) ... View more