Could you expose the Kusto database which holds monitor data (Activity Name, Status, Item type, Start time etc.)? I understand we can subscribe to Fabric Events and Job Events, but this can't be configured at the Workspace level and so it needs to be maintained for every item. ... View more

I have been working on a customer solution to enable the automatic detection and processing of SFTP files landing in ADLS storage. I can get Event Stream to work with the BlobCreated event type. However, with SFTP there are two files created one with a .csv.filepart extension and the final .csv. As I was working through the filtering process to find a filter to prevent the trigger from firing on .filepart, I could not edit the filters after the event stream was created. This required that I delete the event stream/reflex/etc. to make any adjustments. Add the ability to tweak the filters in edit mode (not just the event type). ... 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

When the parameters/tiles on a real-time dashboard are updating, a moving icon shows up indicating the update is in progress. When a refresh rate is configured, this happens for all tiles/parameters at the same time. When the refresh rate is set to "continuous" it is even more annoying as you will see "updating", followed by "updated as of less than a minute a go", and straight after that it switches back to "updating".   This results in a lot of movement on the dashboard distracting customers without adding any value. Customer should be triggered when the value of a tile changes (conditional formatting can be used for this), not when the update status of the tile/parameter itself changes.   The text indicating when the tile was updated is useful (especially in case of failures), but the "updating" spinners should be removed to make the dashboard calmer for the eye.   If an indicator is required for whatever reason, leave out the spinner icons and simply show "updating" without a spinner next to it. ... View more

Love Activator! Would love to see the "View details" link to the Power BI report, not the design tab of the reflex (using Teams action). This design view of the reflex is irrelevant to most of my end users. If not the Power BI report, changing the link to land on the data tab in the reflex would be better than the design view because there is already a link to the report on that tab. Thanks for the consideration! Kim Blackburn ... 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

Improve the discoverability to migrate dashboards in Azure Data Explorer to Fabric Real-Time Dashboards. I know this can be done by downloading the file and importing, but it was not clean that I could do this when migrating my dashboards. ... View more

This suggestion is intended for the Data Activator team: Whenever my trigger is activated, I would like an option to only send alerts for a fixed number of times. This to avoid my end user to get the same alert over and over. Can this functionality be added to the "Detect" section under setting up the Reflex? Best, Christian ... View more

We have UPNs (User Principal Name/ Email) in our organization that have different domains while they are all hosted on the same Fabric Tenancy. They need to be able receiving Trigger emails across domains within the organizations, but unfortunately, they can't according to the current settings with Activator (recipients' domain must match with trigger creator's). We also have a customer service ticket open for this issue (TrackingID#2402290040012315). ... View more

there is already an option to trigger based on value 'change' but this trigger wil activate if the value goes up and down. I would like the trigger to only active in the value goes up (and not down). And another trigger option that only triggers when the value goes down (and not up). Thanks ... View more

Provide connectivity to Kakfa and IoT Hub in Ingestion wizard. ... View more

When sharing a dashboard, the link that is being shared must include the current page and current parameters values for it to be effective. ... View more

No error code. ... View more

I would like to access sickness absence records for the team please. ... View more

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 ... View more

In current state, when a Fabric capacity goes over its CU limit and generates an overage. Reflexes turn off automatically and do not reenable when the overage is burned off. This makes the bursting capabilities of Fabric beyond the CU limits very risky and almost unusable for organizations using the monitoring and real-time architectures. Aside from being able to limit the ability to generate an overage, it would be helpful to have options to deal with Reflexes when an overage occurs. Initial options include: Add a setting that when the CU limits lower to a certain percentage, Reflex jobs resume. Having a setting that allows Reflex jobs to continue beyond 100% CU Utilization to a certain point. When the Reflex job pauses, an admin is notified. ... View more

We need control over who can see the Real-Time Hub in the Microsoft Fabric Portal for better governance. ... View more

Hello, Currently, the EventStream UI for defining EventStream flows is working perfectly. While most of us enjoy the no-code experience, it would be greatly appreciated if we can be allowed to edit or entirely define the query (similar to ASA Job queries). ... View more