3.2 — Configure Alerts
DP-700 Domain 3 · Skill 3.2
What You Need to Know
Monitoring tells you what happened when you look. Alerts tell you without being asked. Fabric has several ways to alert, from a free failure email to rules that act on live data.
Alert options
| Option | What it watches | What it does | Cost |
|---|---|---|---|
| Schedule failure emails (job scheduler, or Monitor hub → Alerts) | Scheduled runs of an item that fail | Emails users or groups in the tenant | Free |
| Activator-based job alerts (Monitor hub → Alerts) | Job events such as Started, Succeeded and Failed, for many item types | Rich notifications and automated actions. Needs workspace monitoring | Activator uses capacity |
| Pipeline activities (Office 365 Outlook, Teams) | Whatever path you connect them to, such as On fail | Sends an email or Teams message with dynamic content (error message, run ID) | Part of the pipeline run |
| Activator rules on data | Values in an eventstream, eventhouse query, Real-Time Dashboard or Power BI visual | Email, Teams, run a pipeline or notebook, Power Automate | Activator uses capacity |
| Alerts from workspace monitoring queries | A KQL query over the monitoring logs | Activator notification when the query returns rows | Activator uses capacity |
Activator in brief
- Activator is Fabric's no-code detection engine. It watches events or data, evaluates rules per object (for example per device, per pipeline or per store) and runs actions.
- Rules can trigger on a condition (temperature > 90), a change (status changes to Failed), no events for a period (a feed has stopped), or a value staying above a threshold for a duration.
- Sources include eventstreams, Fabric events (job events, OneLake events, workspace item events), Azure events (Blob Storage), KQL querysets, Real-Time Dashboards and Power BI reports.
- Actions include email, Teams messages, running Fabric items (pipelines, notebooks, Spark job definitions) and Power Automate flows.
Picking the right alert
| Requirement | Choose |
|---|---|
| "Email the data engineers when any step of the load pipeline fails" | An Outlook activity on the failure paths in the pipeline (or a pipeline-level failure branch) |
| "Tell the owner when a scheduled notebook fails, at no extra cost" | Schedule failure emails |
| "Alert when the nightly job hasn't succeeded by 6:00" or "on every Succeeded event" | Activator job alerts |
| "Notify operations when a sensor's reading goes over its limit" | An Activator rule on the eventstream |
| "Run a cleanup pipeline when a file lands in a OneLake folder" | Activator on OneLake events, with the action Run pipeline |
Key Concept: To alert on a job's outcome, use schedule failure emails, pipeline activities or Activator job alerts. To alert on data values or events, use an Activator rule on that data.
Exam Traps
- Expecting schedule failure emails to fire for manual runs (they cover scheduled runs only)
- Polling a table with a scheduled notebook to detect a condition that Activator can watch on the stream
- Putting the alert activity on On completion, so it sends a message after every run
- Forgetting that Activator-based job alerts need workspace monitoring turned on
Check your understanding
Practice Scenario
🔒 This practice scenario is part of Skillmarked Pro
The lessons stay free. Pro unlocks the other 16 DP-700 practice scenarios and the 50-question timed mock exam, plus everything for every other exam.
Launch Deal: first month €9.95, then €19.90/month. Enter code LAUNCH50 at checkout. Ends 1 December.
Cancel anytime. Or €199 a year, which saves 17%.
Not sure yet? Try 10 free mock exam questions.
Already Pro? Log in.
Sources
- Set up job alerts in the Monitor hub, Microsoft Learn
- What is Fabric Activator?, Microsoft Learn
- Office 365 Outlook activity, Microsoft Learn
- Job Scheduler in Microsoft Fabric, Microsoft Learn