Kicking off a job on a schedule or in response to an event

Microsoft Fabric lets you automate pipeline (and other item) execution using time-based schedules or event-based triggers so that data movement and transformation run without manual intervention. Schedules are configured per item (pipeline, notebook, dataflow) with recurrence and time-zone settings, while event triggers fire pipelines in response to Fabric or storage events surfaced through the Real-Time hub/Reflex (Data Activator).

1 · Learn the must-know

• 1Each Fabric item (Data pipeline, notebook, dataflow, semantic model refresh) has its own Schedule settings pane where you set a start date/time, time zone, and recurrence (once, by minutes, hourly, daily, or weekly on specific days).
• 2The minimum supported schedule interval is a few minutes (commonly quoted as no more frequent than every 1-5 minutes depending on item type), so near-real-time needs should use event-based triggers instead.
• 3Event-based automation in Fabric is delivered through the Real-Time hub/Data Activator (Reflex), which can subscribe to Fabric workspace events (e.g., item refresh completed) or external events like Azure Blob/ADLS storage 'blob created/deleted' to start a pipeline or send an alert.
• 4Storage event triggers require the underlying storage account to have Event Grid enabled and the Fabric workspace/service principal to have the necessary permissions on that storage account.
• 5A single pipeline can have multiple triggers attached (e.g., one schedule plus one or more event triggers), and each trigger can be independently enabled or disabled without republishing the whole pipeline.
• 6Monitoring of both scheduled and event-triggered runs is done through the pipeline's Run history/Monitor hub, which shows trigger type, trigger time, and status, aiding troubleshooting of missed or duplicate runs.

2 · Check your understanding