Currently, Activator rules only sends email notifications to individual internal email addresses. It would be very beneficial to allow Activator rules to send emails directly to Microsoft Exchange Distribution List as well.   This will make notification management easy for developers. Instead of updating recipients individually within each Activator rule whenever team members join or leave, administrators could manage membership directly through the Exchange Distribution List.   This will reduce effort require for maintenace and help ensure notifications always reach the correct audience.   This enhancement will be useful for teams, support groups, and large organizations where notification recipients change frequently.  ... View more

Today, when creating an Activator rule from a Power BI visual, we can set the evaluation frequency (for example, 1 evaluation per hour), but we cannot control when those evaluations happen during the day or week. Two related gaps:   No time window control. Alerts run 24/7 at the chosen frequency. There is no way to scope evaluations to specific days or hours of the day. No start time control. The evaluation cycle appears to anchor to the Activator creation time, so the rhythm of the schedule depends on when the rule was saved rather than a business-meaningful anchor the user picks.   Proposal Extend the frequency configuration to also support: Time windows: pick the days of the week and the hour range during which the alert should evaluate (for example, Mon to Fri, 09:00 to 18:00). Custom start time: let users set an explicit start time for the evaluation cycle instead of defaulting to the creation timestamp.   Example scenarios A retail operations team only needs inventory alerts during store hours. A support team wants SLA breach alerts only during staffed shifts, not overnight. A finance team wants market-hours-only evaluations for trading dashboards.   Why it matters Cuts noise from off-hours alerts that no one is around to act on. Reduces unnecessary evaluation volume and the capacity it consumes. Aligns Activator's behavior with how teams actually operate. ... View more

As explained here, currently, if we want to allow PowerBI users to create alerts, we must authorise them to create items in Fabric (without being able to restrict other items such as Data Pipeline, Copy Job, etc.). This is a real governance issue in the Fabric platform, because for a PowerBI user, it is legitimate to create an alert on a PowerBI report without enabling the creation of Data Pipeline, Notebook, and others that require other skills (and governance). https://community.fabric.microsoft.com/t5/Fabric-platform/Allow-PowerBI-users-to-create-alerts-without-being-able-to/m-p/4868832#M22557 Beyond the functionality of Data Alerts, I believe that access to the various Fabric features should be made modular. ... View more

According to the official documentation: "If a problem occurs with any of your Fabric Activator events, objects, or rules after you create them, then Fabric Activator sends you an email containing an error code." However: The recipient is not configurable (hardcoded to item creator only) This limitation is not documented No alternative notification channels are available This creates a critical blind spot for production monitoring when: Activators are deployed via service principal (cannot receive emails) The original creator leaves the team or changes roles Multiple team members need visibility into system errors Requested Feature: Enable configuration of error notification recipients through: Workspace-level notification settings Distribution list/group email support Integration with workspace contacts/admins Use Case: Our production Activators are deployed via CI/CD pipelines using service principals. Without configurable notifications, we have no way to receive critical error alerts, making Activator unsuitable for production use ... View more

Hi there,   as a developer I would like to be able to select conditions, so that if the condition is met, actions are only triggered for a certain amount of time even if the condition is still met.   Example: Monitoring of capacity interactive delay threshold percentage. I want to create a condition to get notified if the CU usage is about 80% on my capacity. Then a trigger shall create a MS Teams message ONCE. And if the condition is meet after e.g. 15min another message.    Right now the behaviour is event based. Meaning everytime a new datapoint is created from Fabric (automatic behaviour, not changeable) the condition is evaluated and triggers an alert. This leads to messages every 30 seconds.    Would be great to see this function in the near future.   Best regards! ... View more

When a new alert is created and its frequency is set (for example, to daily) the alert currently follows the exact time at which it was created. For instance, if the alert is created at 3:04 PM with a one‑day frequency, it will run the KQL query every day at 3:04 PM. At this time, there is no way to view or modify the scheduled run time. We would like to request a feature that allows users to adjust the alert execution time based on a user‑selected schedule, rather than being restricted to the original creation time.     ... View more

Currently Activator will auto ingest all dimension columns and one measure column, however as end user we cannot choose which column will be treated as dimension from pbi side.   Thus I would suggest to add feature to ingest selected columns into activator so that we can choose more columns in the context and user can tell and have a full picture on what's triggering the alert, simply according to the context information included in the notification ... View more

Hi Team, As organizations begin adopting Microsoft Fabric's Data Activator, we need centralized administrative visibility and control over reflexes (alerts) created across the tenant. Currently, there is Mechanisam to: Retrieve a list of all reflexes (Data Activator rules) Identify owners, workspace locations, trigger conditions Audit or manage usage at scale We request the introduction of Admin REST API endpoints or any other possible method that allow administrators to: List all reflexes across all workspaces Filter by workspace, owner, status (enabled/disabled) Export configuration details Detect inactive or duplicate alerts Monitor real-time activation logs (optional) This functionality is critical for enterprise adoption, governance, and automation in regulated or large-scale environments. Thank you ... View more

Add the ability to set 'alerts' in reports. ... View more

Hi,   Currently, the Power BI REST API allows us to extract only the workspace name and report name, but it does not provide the ability to retrieve a list of Data Activator Reflex items across different workspaces. We request that this feature be added to help track Reflex items more effectively. Thanks, Mahammad Jafar ... View more

All Fabric items don't necessarily align with organizational security and governance policies. It is frustrating that we cannot decide what specific Fabric items get to be enabled and it has to be all or nothing. In particular, my organization relies heavily on Power BI for business intelligence, and stakeholders are upset that they can't use Report data alerts because it's powered by Fabric Activator which can only be enabled if we switch everything else on. It is also concerning that without being able to control the capabilities enabled, our Fabric capacities usage would be impacted if we don't have the "pay as you go" pricing model. Having someone start using 'copy job' could jeopardize our Power BI reports and create throttling unitentionally. Please give back the governance decision to the tenant admins. ... View more

Currently, the Power BI alert operates on a checkpoint system, running every 60 minutes from the trigger creation timestamp. However, in practice, we would prefer a more frequent monitoring schedule or a real-time check that fires the trigger as soon as the threshold is met. This would be especially useful for incidents where immediate notification is crucial, rather than having to wait for the next checkpoint. ... View more

Right now, when using Activator for KPI alerting in Microsoft Fabric, the messages that get sent to Microsoft Teams only support plain text. This means that if you try to add a link to the source report, it just shows up as text and can’t be clicked. As a result, users have to manually copy and paste the link or go find the report themselves, which interrupts the workflow.   If Activator messages supported clickable hyperlinks, users could jump straight from the Teams alert into the relevant Power BI or Fabric report. This would make the alerts far more actionable, saving time and reducing friction for business users. It would also add important context by tying the KPI breach or anomaly directly to the detailed report, similar to how alerts from other Microsoft services, like Power Automate, already provide interactive links. ... View more

Dear community, Do you also face the challenge that you upload csv-files and need to monitor manually if the file was modified? Then you manually start the process to have the current data available in your tables/data models/reports?   In the documentation it is explained that a action can be triggered by "if the the file is created or replaced"; this only happens when the file is really uploaded manually (or by a notebook) in the browser in onelake in fabric. If it is only changed in the onelake file explorer for windows preview feature plus saved there, ONLY the activation details arrive but NO action is triggered.   It would be nice to have a possibility to trigger an action when the data within the file is modified. ... View more

The app space and workspace Set Alerts (menu bar) and Add Alerts (ellipses on object) both automatically create the "My Power BI Activator Alerts" in another workspace than the one currently under. Suggest the creation of the Alert only be made on a Save like the Subscriptions. Fix the default selected Workspace saved location to the current workspace and possibly naming the Activator Alert from the default during the initial creation; like Subscriptions. Service Request #: 2502120040007360 ... View more

Currently there is no way to fully pause an Activator rule that uses a KQL query as a source. Even when the rule is paused, the activator continues to run the KQL query against the Eventhouse.   The current workaround is to set the query frequency to the longest available option, which is once per day. However, this daily execution prevents the Eventhouse from becoming idle, which results in ongoing Eventhouse uptime charges.   Would it be possible to add a feature that allows an Activator to be completely paused, similar to how rules can be paused?   Thank you in advance. ... View more

Alert is not triggering when the current value is same as prior value. We need an option under notification frequency settings like “Every Dataset refresh”. This option will trigger Alert when the current numeric value meets the condition on every data refresh irrespective of data changes or not. ... View more

Hi Team,  for a faster creation of alerts it will be beneficial to duplicate an existing alert and change just minor details.  Thank you.   ... View more