activator-authoring-cli

To create Microsoft Fabric Activator alerts, you need to wire entities from KQL, Eventstream, or Real-time Hub sources and define trigger logic. The process generates a JSON-stringified rule template and Base64-encoded definition parts deployed via Fabric REST calls.

Yes, you can automate Teams notifications and Fabric item invocations using Activator. The system supports automated actions for Teams messages, email alerts, and triggering pipelines, notebooks, dataflows, and functions based on your defined event-driven rules.

The best way to troubleshoot existing Microsoft Fabric Activator definitions is to validate the entity wiring and ensure the JSON-stringified rule templates are correctly formatted. You can then use update workflows to fix and redeploy the Activator items.

Yes, the Fabric Activator supports Digital Twin Builder and Real-time Hub as source graphs. It also accommodates KQL and Eventstream sources to build alerts, notifications, and automated actions within your Microsoft Fabric environment.

Fabric REST calls fail when updating Activator definitions if the api.fabric.microsoft.com audience is incorrect or the az rest command lacks properly Base64-encoded definition parts. Ensure your JSON-stringified rule templates and entity wiring are valid before deployment.

Yes, you need az rest to deploy Microsoft Fabric Activator rules because the deployment requires making Fabric REST calls to the proper api.fabric.microsoft.com audience. This ensures the Base64-encoded definition parts and rule templates are correctly authored and applied.