Merge pull request #2764 from MicrosoftDocs/main639082874215667724sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/data-factory/media/pipeline-runs/schedule-failure-notifications.png

@@ -83,6 +83,16 @@ To delete a schedule, select the **Edit** icon (pencil) next to the schedule you
 
 :::image type="content" source="media/pipeline-runs/delete-schedule.png" alt-text="Screenshot showing the delete button can be found in the edit window.":::
 
+### Configure failure notifications
+
+You can configure email notifications to be sent when a scheduled pipeline run fails. Notifications aren’t sent for on‑demand runs.
+
+To configure failure notifications, open the pipeline, select **Schedule** in the top banner of the **Home** tab, and add users or groups under **Failure notifications**.
+
+To configure failure notifications, open the pipeline, go to the **Home** tab, select **Schedule**, and then add users or groups under **Failure notifications**.
+
+:::image type="content" source="media/pipeline-runs/schedule-failure-notifications.png" alt-text="Screenshot that shows failure notification settings for scheduled pipeline runs." lightbox="media/pipeline-runs/schedule-failure-notifications.png":::
+
 ## Event-based pipeline runs
 
 Event triggers let you start pipelines when specific events happen, like when files arrive or get deleted in storage. You can trigger pipelines from file events, job events, and workspace events. If you're moving from Azure Data Factory, you'll find storage events familiar.

docs/data-factory/pipeline-runs.md

@@ -65,6 +65,28 @@ To ensure your schedule is valid:
 > [!IMPORTANT]
 > Schedules become expired if a user doesn't log in to Fabric for 90 consecutive days. For more information, see [Refresh tokens in the Microsoft identity platform](/entra/identity-platform/refresh-tokens).
 
+## Receive notifications for failed scheduled jobs
+
+You can receive email notifications when a job triggered by a **schedule** fails to complete.
+
+### Configure failure notifications
+While configuring a schedule, add users or groups under **Failure notifications** to receive emails when a scheduled run fails.
+
+### Important considerations
+- **Applies to all schedules**: Notification settings apply across all schedules for the item.
+- **Scheduled runs only**: Notifications are sent only for failures from scheduled runs. Notifications aren't sent for manually triggered runs.
+- **Recipients**: Notifications can be sent to users or groups in your Microsoft Entra tenant, including internal users and B2B guest users. Direct external email addresses aren’t supported.
+- **Language**: Notifications are sent in the display language of the recipient’s Fabric account. English is used as a fallback. 
+
+### Notification content
+When a scheduled run fails, the email includes:
+- Item name and type
+- Submitter
+- Error details  
+- Run time (UTC)  
+- Link to view details in the Monitoring Hub  
+- Technical details for troubleshooting, including Activity ID, Request ID, and timestamps
+
 ## Manage multiple schedules
 
 Create and manage multiple schedules for a single item. Use different schedules to run jobs at different times or with different settings.