If you haven’t already, check out Arun Ulag’s hero blog “FabCon and SQLCon 2026: Unifying databases and Fabric on a single, complete platform” for a complete look at all of our FabCon and SQLCon announcements across both Fabric and our database offerings.
When you set up a scheduled job, the goal is usually to set it and forget it. But when something goes wrong, finding out late can mean stale data, broken downstream processes, or surprised stakeholders.
Microsoft Fabric now supports email notifications for failed scheduled jobs, so you’re notified as soon as a run fails and can take action.
Why this matters
Scheduled jobs often run quietly in the background. Without proactive notifications, failures can go unnoticed until someone spots an issue downstream.Failure notifications help you:
- Spot failed runs sooner without manually checking run history.
- Reduce downtime when a job fails.
- Keep the right people informed when attention is needed.
Set up failure notifications
Failure notifications are configured alongside an item’s schedules.- Open your item in Microsoft Fabric.
- Select Schedule to open the schedule configuration.
- Under Failure notifications, add the users or groups who should be notified when a scheduled run fails.
Figure: Failure notifications for Pipeline schedule.
How failure notifications work
- Failure notifications work for all Fabric items that support scheduling, including Pipelines, Notebooks, Dataflows Gen2, and more.
- Schedules created both in the Fabric portal or via the Job Scheduler API send a notification when a scheduled run fails.
- Notifications are sent for scheduled runs only. Runs triggered manually don’t send failure notifications.