Monitor all the pipeline failures and send a Teams alert

[JoanAmal]

We run multiple scheduled pipelines, each with chained Invoke pipelines. How can we monitor all of the multiple pipeline failures and send a Teams alert when any pipeline fails? Please give step-by-step instructions.

[V-yubandi-msft]

Hi @JoanAmal ,
Could you please let us know if your issue has been resolved, or if you need any additional information.

Thank you.

[V-yubandi-msft]

Hi @JoanAmal ,

May I know if your issue is resolved. If you need any additional help or further details, please let us know.

Thank you.

[V-yubandi-msft]

Hi @JoanAmal ,

Thank you for reaching out to the Microsoft Fabric Community. In Fabric, it's most effective to manage notifications within the pipeline graph rather than relying solely on Activator.
Set up a reusable Send Teams Alert pipeline and call it from the On Failure branch of each Invoke Pipeline activity. Pass parameters like the pipeline name, activity name, and error message. This approach ensures that whenever any child pipeline encounters a failure, the orchestrator will promptly send a Teams notification, no matter where the issue occurs in the process.

Helpful Reference:

Solved: Re: Data Pipeline failure alert - Microsoft Fabric Community

Create alerts for pipeline runs - Microsoft Fabric | Microsoft Learn

Teams activity - Microsoft Fabric | Microsoft Learn

Regards,
Yugandhar.

[JoanAmal]

I am having trouble configuring a reliable failure alert for my orchestration pipelines.

Current Setup:

I have a main orchestration pipeline that sequentially calls three child pipelines using Invoke Pipeline activities.

• Invoke A -> Invoke B -> Invoke C

1. Single Pipeline Test (Works): When I test a pipeline containing just one activity, the Teams Alert fires correctly on failure.

2. Chained Pipelines (Fails): When I run the chained orchestration, the Teams Alert does not fire if the first or second invoked pipeline fails.

I tried using the Activator/Alerts feature for pipeline monitoring, but it does not appear to monitor or catch the failure state of the chained Invoke Pipelines effectively.

What is the recommended best practice in Fabric to reliably send a Teams notification when ANY activity (or invoked child pipeline) fails within a sequential orchestration flow? Please give step-by-step instructions.