activator-authoring-cli

Automate Microsoft Fabric Activator alert rules and action workflows via REST API and az CLI.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/weiflycc-cmd/skills-for-fabric --skill activator-authoring-cli-weiflycc-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: activator-authoring-cli
Source: https://github.com/weiflycc-cmd/skills-for-fabric/tree/main/plugins/fabric-authoring/skills/activator-authoring-cli
Command: npx skills add https://github.com/weiflycc-cmd/skills-for-fabric --skill activator-authoring-cli-weiflycc-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about activator-authoring-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Microsoft Fabric Activator alert rules creation via REST API?

You can automate Fabric Activator alert creation by using the Fabric control-plane REST API and az CLI to programmatically author, update, and delete Reflex definitions, bypassing manual UI configuration for complex multi-source scenarios.

Can I bind Microsoft Fabric alerts to trigger Pipelines and Teams messages?

Yes, Fabric Activator alerts can be bound to trigger actions such as Teams messages, emails, and the execution of Fabric items including Pipelines, Notebooks, Spark job definitions, Dataflows, and User Data Functions.

What data sources support Fabric Activator alert authoring through az CLI?

Fabric Activator alerts authored via az CLI support connections to KQL databases, Eventstreams, Digital Twin Builder/Ontology instances, and Real-time Hub workspace event subscriptions.

How do I configure threshold and heartbeat detection conditions for Fabric alerts?

You configure detection conditions by defining thresholds, ranges, state changes, transitions, and heartbeats within the Activator definition payload, using transition-based detectors to avoid alert spam.

How do I handle long-running operations when updating Fabric Reflex definitions?

When updating Fabric Reflex definitions, you must handle long-running operations correctly by managing GUIDs throughout the read, modify, and update process to avoid common authoring pitfalls.

Why use az CLI instead of the Fabric UI for Activator configuration?

Using az CLI and REST APIs for Activator configuration eliminates the friction and errors of manual UI setup, enabling repeatable, programmatic management of complex alert rules and automated action workflows.