Fabric Ideas

rabindori · ‎05-05-2025

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.

Anonymous · ‎05-26-2023

Provide continuous ingestion from OneLake.

fbcideas_migusr · ‎09-18-2024

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

Samanoha · ‎09-15-2025

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

thomas_pagel · ‎10-07-2023

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.

thomas_pagel · ‎10-07-2023

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

nicola_greco · ‎10-10-2024

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.

VChimbili

Currently, EventStream supports adding Event Hub as an input source using the SAS Key authentication method. Please add support for Managed Identity–based authentication so that EventStream can align with Microsoft’s Safe Secrets and keyless authentication best practices. This would improve security posture, eliminate secret rotation overhead, and enable seamless integration with Azure resources using RBAC.

bbates22 · ‎04-23-2025

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.

JonStewart · ‎03-20-2025

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

sourabhguha · ‎03-12-2025

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.

Natalie_iTalent · ‎05-26-2023

Provide connectivity to Kakfa and IoT Hub in Ingestion wizard.

fbcideas_migusr · ‎06-10-2024

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!

fbcideas_migusr · ‎03-30-2024

The following are examples of scenarios that benefit from clustering: Tables often filtered by high cardinality columns. Tables with significant skew in data distribution. Tables that grow quickly and require maintenance and tuning effort. Tables with access patterns that change over time. Tables where a typical partition column could leave the table with too many or too few partitions.

werner_zirkel · ‎12-11-2024

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.

dschlesinger · ‎03-30-2025

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

SandeepPawar1 · ‎06-30-2023

It's not very widely known or shared that Kql queries can be run in Fabric notebooks. Could you please install the Kqlmagic extension in the default Fabric environment so it can be used without installation. Thanks. Tutorial- Use a notebook with Kqlmagic to query a KQL database - Microsoft Fabric | Microsoft Learn

fbcideas_migusr · ‎04-19-2024

Currently, materialised views cannot reference external tables. For data curation, it is important to combine Lakehouse table dimensions (cold data) with KQL tables (hot data). Support for this feature improves data manageability.

Anonymous · ‎05-26-2023

Provide table, materialized view, cache, user monitoring insights similar to Azure Data Explorer Insights

matthewlopesdev · ‎12-10-2025

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.

Share your ideas and vote for future features

Fabric RTI - follower database with Table level sharing

Provide continuous ingestion from OneLake

Support Real-Time Dashboard in Power BI Embedded

Shared Kusto MCP server needed

Event Processing: Allow CUD actions

Event Processing: Derive value from complex JSON

Assign AllDatabasesViewer role at Eventhouse level.

Enable Managed Identity Authentication for Event Hubs in Event Stream Inputs

Add Create data stream to Fabric REST Api for Eventhouse

Kusto Backfill for Incremental Refresh

Onelake availability of Materialized views in EH

Provide connectivity to Kakfa and IoT Hub in Ingestion wizard

Integrate Kusto Trender as TSI UI equivalent in Real-Time Hub

Support Liquid Clustering on Delta Tables

Materialized Views on Delta Lake tables

Integrate Fabric Eventhouse with Azure AI Agent service as knowledge tool

Install Kqlmaginc extension by default in Fabric

Support KQL materialized view reference OneLake shortcut

Provide table, materialized view, cache, user monitoring insights similar to Azure Data Explorer Insights

Automated export for Eventhouse data to Lakehouse without primary table access

Helpful resources

How to connect to Fabric database from fabric note...

Warehouse: Show execution plans

Query plan or explain plan in Warehouse

Cross Workspace Row Level Security in MS Fabric

folder-based write access

FabCon is coming to Atlanta

Share your ideas and vote for future features

Helpful resources