What problem does it solve?
Manually configuring Microsoft Fabric Activator (Reflex) alert rules, notifications, and automated action workflows through the Fabric UI is time-consuming and error-prone, especially for complex scenarios involving multiple data sources and custom action bindings. This Skill eliminates that friction by providing step-by-step guidance for programmatically authoring and managing Activator definitions via the Fabric REST API and az CLI.
Core Features & Use Cases
- Multi-Source Alert Authoring: Create alerts connected to KQL databases, Eventstreams, Digital Twin Builder/Ontology instances, and Real-time Hub workspace event subscriptions.
- Flexible Detection Logic: Configure threshold, range, state change, transition, and heartbeat detection conditions for alerts, with guidance on avoiding alert spam via transition-based detectors.
- Action Binding: Wire alerts to actions including Teams messages, emails, and execution of Fabric items such as Pipelines, Notebooks, Spark job definitions, Dataflows, and User Data Functions.
- Definition Management: Safely read, modify, and update existing Activator/Reflex definitions with guidance on GUID management, LRO handling, and common authoring pitfalls.
- Use Case: A data engineer can use this Skill to set up an alert that sends a Teams notification and triggers a data remediation pipeline when KQL query results show more than 10 error records in a 5-minute window.
Quick Start
Use the activator-authoring-cli skill to create an alert that sends a Teams message and runs a data quality pipeline when KQL query results show more than 10 error records in a 5-minute window.