<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Trigger Alerts Notification for successful/failed Pipelines in Pipelines</title>
    <link>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4619150#M7322</link>
    <description>&lt;P&gt;Also, we are only looking to integrate this as a complete Fabric solution (we don't want to use Azure).&lt;/P&gt;</description>
    <pubDate>Fri, 21 Mar 2025 05:08:37 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2025-03-21T05:08:37Z</dc:date>
    <item>
      <title>Trigger Alerts Notification for successful/failed Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4615783#M7309</link>
      <description>&lt;P&gt;Hi Community!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a scenario where I have a master pipeline which has multiple child pipelines within it.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For Example:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Pipeline A&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Child pipeline(Pipeline A) - Pipeline B&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Child pipeline(Pipeline B) - Pipeline C&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pipeline A has some activities and is then connected to a child pipeline &lt;STRONG&gt;Pipeline B&lt;/STRONG&gt;, Pipeline B has few activities with another child pipeline &lt;STRONG&gt;Pipeline C. &lt;/STRONG&gt;Now these pipelines are interconnected and have dependencies. I want to ensure that I get an email notifications triggered upon successful/ failed runs. I did find some solutions in the community but none of them suits my scenario. Also I have complicated pipelines, therefore I cannot work on below scenarios as well(includes too many activities/ doesn't suit my scenario):&lt;BR /&gt;&lt;A href="https://www.c-sharpcorner.com/article/error-logging-and-the-art-of-avoiding-redundant-activities-in-msft-fabric-data-p/" target="_self"&gt;https://www.c-sharpcorner.com/article/error-logging-and-the-art-of-avoiding-redundant-activities-in-msft-fabric-data-p/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.fabric.microsoft.com/t5/Data-Pipeline/Monitor-pipeline-runs-with-alerts/m-p/4141013" target="_self"&gt;https://community.fabric.microsoft.com/t5/Data-Pipeline/Monitor-pipeline-runs-with-alerts/m-p/4141013&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was thinking of using a single notebook activity and using Fabric API's to parameterize my pipelines and capture logs and use email notifications. However, I thought there might be better solutions.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Please let me know if there are any other ways.&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance!&lt;BR /&gt;Hrishi&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 07:15:05 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4615783#M7309</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-03-19T07:15:05Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger Alerts Notification for successful/failed Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4617389#M7312</link>
      <description>&lt;P&gt;Hi&amp;nbsp;Anonymous&lt;/LI-USER&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To address your scenario in Microsoft Fabric, where you have a master pipeline with multiple interconnected child pipelines and want to trigger email notifications upon success or failure, here are some potential solutions:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Using Fabric API with a Notebook Activity&lt;BR /&gt;Your idea of using a single notebook activity to parameterize pipelines and capture logs is a good approach. Here's how you can implement it:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Use the Fabric API to monitor pipeline runs programmatically.&lt;BR /&gt;Create a notebook activity in your pipeline that:&lt;BR /&gt;Fetches the pipeline run status using the Fabric API.&lt;BR /&gt;Logs the status (success/failure) for each pipeline and its child pipelines.&lt;BR /&gt;Sends an email notification using an SMTP library (e.g., Python's smtplib) or a third-party email service like SendGrid.&lt;BR /&gt;Parameterize the notebook to handle different pipelines dynamically.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Using Webhooks for Notifications&lt;BR /&gt;You can use webhooks to trigger notifications based on pipeline events.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Configure a webhook in Microsoft Fabric to listen for pipeline run events (success/failure).&lt;BR /&gt;Use a service like Azure Logic Apps, Power Automate, or a custom webhook handler to process the event and send email notifications.&lt;BR /&gt;Ensure the webhook is triggered for both the master and child pipelines.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Custom Logging and Notification Pipeline&lt;BR /&gt;Create a separate pipeline dedicated to logging and notifications.&lt;/P&gt;
&lt;P&gt;At the end of each pipeline (master and child), add an activity to log the run status to a centralized location (e.g., Azure Blob Storage, SQL Database).&lt;BR /&gt;Trigger the logging and notification pipeline after the master pipeline completes.&lt;BR /&gt;The logging pipeline reads the run statuses and sends email notifications.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Using Azure Monitor Alerts&lt;BR /&gt;Leverage Azure Monitor to track pipeline runs and send alerts.&lt;/P&gt;
&lt;P&gt;Enable diagnostic settings for your pipelines to send logs to Azure Monitor.&lt;BR /&gt;Create an alert rule in Azure Monitor to trigger on specific conditions (e.g., pipeline failure).&lt;BR /&gt;Configure the alert to send email notifications.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Combining Fabric API and Logic Apps&lt;BR /&gt;If you want a more robust solution, combine the Fabric API with Azure Logic Apps.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Use the Fabric API to fetch pipeline run statuses.&lt;BR /&gt;Trigger a Logic App workflow to process the statuses and send email notifications.&lt;BR /&gt;Schedule the Logic App to run periodically or trigger it from the pipeline.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Nono Chen&lt;/P&gt;
&lt;P&gt;If this &lt;STRONG&gt;&lt;EM&gt;post&lt;/EM&gt;&lt;/STRONG&gt;&amp;nbsp;helps, then please consider&amp;nbsp;&lt;STRONG&gt;&lt;EM&gt;Accept it as the solution&lt;/EM&gt;&lt;/STRONG&gt;&amp;nbsp;to help the other members find it more quickly.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Mar 2025 01:34:53 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4617389#M7312</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-03-20T01:34:53Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger Alerts Notification for successful/failed Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4619135#M7321</link>
      <description>&lt;P&gt;Hi&amp;nbsp;Anonymous&lt;/LI-USER&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the logic, I happen to use notebook at pipeline run time by using a wait activity(as the status might take some time to reflect since we are using API). I happen to use the notebook during pipeline run where I fetch my latest run. I am able to extract this. However, I am trying to use Outlook activity to push the notification. The issue is I am not sure how to convert my string output to Table.&lt;BR /&gt;&lt;BR /&gt;This is the structure of my notebook df output:&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Main Pipeline Name&lt;/TD&gt;&lt;TD&gt;Master Pipeline Name&lt;/TD&gt;&lt;TD&gt;Pipeline Name&lt;/TD&gt;&lt;TD&gt;Invoke Pipeline Name&lt;/TD&gt;&lt;TD&gt;Pipeline ID&lt;/TD&gt;&lt;TD&gt;Status&lt;/TD&gt;&lt;TD&gt;Error Message&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;PL_Parameter_&lt;/TD&gt;&lt;TD&gt;Main Pipeline&lt;/TD&gt;&lt;TD&gt;Invoke pipeline1&lt;/TD&gt;&lt;TD&gt;PL_Parameter_&lt;/TD&gt;&lt;TD&gt;xyz-abc&lt;/TD&gt;&lt;TD&gt;Failed&lt;/TD&gt;&lt;TD&gt;{Error_Message_will_be_displayed}&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;PL_Parameter_&lt;/TD&gt;&lt;TD&gt;PL_Parameter_&lt;/TD&gt;&lt;TD&gt;Invoke pipeline1&lt;/TD&gt;&lt;TD&gt;PL_Test_1&lt;/TD&gt;&lt;TD&gt;efg-fhi&lt;/TD&gt;&lt;TD&gt;Failed&lt;/TD&gt;&lt;TD&gt;{Error_Message_will_be_displayed}&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;BR /&gt;I am using mssparkutils to capture this notebook output(exitValue) as a string and pass it to set variable(optional) then to Outlook activity. But since it is string, I am not sure how I can convert this string to table.&lt;BR /&gt;&lt;BR /&gt;Also, if we want to use SMTP, can I use FabricRestClient instead of passing username and password.&lt;BR /&gt;Can you please share a sample structure for SMTP code as I don't want to pass username and password.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance!&lt;BR /&gt;Hrishi&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2025 05:02:16 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4619135#M7321</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-03-21T05:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger Alerts Notification for successful/failed Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4619150#M7322</link>
      <description>&lt;P&gt;Also, we are only looking to integrate this as a complete Fabric solution (we don't want to use Azure).&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2025 05:08:37 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4619150#M7322</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-03-21T05:08:37Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger Alerts Notification for successful/failed Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4634977#M7391</link>
      <description>&lt;P&gt;cant we use power automate for this ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 11:46:44 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4634977#M7391</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-04-02T11:46:44Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger Alerts Notification for successful/failed Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4684647#M7749</link>
      <description>&lt;P&gt;Hi&amp;nbsp;Anonymous&lt;/LI-USER&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;Thanks &lt;SPAN class=""&gt;for &lt;SPAN class=""&gt;the &lt;SPAN class=""&gt;detailed &lt;SPAN class=""&gt;context&amp;nbsp;&lt;SPAN class=""&gt;you're &lt;SPAN class=""&gt;on &lt;SPAN class=""&gt;the &lt;SPAN class=""&gt;right &lt;SPAN class=""&gt;track &lt;SPAN class=""&gt;with &lt;SPAN class=""&gt;using &lt;SPAN class=""&gt;a &lt;SPAN class=""&gt;notebook &lt;SPAN class=""&gt;and &lt;SPAN class=""&gt;Fabric &lt;SPAN class=""&gt;APIs. &lt;SPAN class=""&gt;To &lt;SPAN class=""&gt;convert &lt;SPAN class=""&gt;your &lt;SPAN class=""&gt;DataFrame &lt;SPAN class=""&gt;output &lt;SPAN class=""&gt;into &lt;SPAN class=""&gt;a &lt;SPAN class=""&gt;format &lt;SPAN class=""&gt;suitable &lt;SPAN class=""&gt;for &lt;SPAN class=""&gt;the &lt;SPAN class=""&gt;Outlook &lt;SPAN class=""&gt;activity, &lt;SPAN class=""&gt;I &lt;SPAN class=""&gt;recommend &lt;SPAN class=""&gt;using &lt;SPAN class=""&gt;df.&lt;SPAN class=""&gt;to_html(&lt;SPAN class=""&gt;index=&lt;SPAN class=""&gt;False) &lt;SPAN class=""&gt;within &lt;SPAN class=""&gt;your &lt;SPAN class=""&gt;notebook &lt;SPAN class=""&gt;to &lt;SPAN class=""&gt;transform &lt;SPAN class=""&gt;the &lt;SPAN class=""&gt;DataFrame &lt;SPAN class=""&gt;into &lt;SPAN class=""&gt;an &lt;SPAN class=""&gt;HTML &lt;SPAN class=""&gt;table &lt;SPAN class=""&gt;string. &lt;SPAN class=""&gt;You &lt;SPAN class=""&gt;can &lt;SPAN class=""&gt;then &lt;SPAN class=""&gt;pass &lt;SPAN class=""&gt;this &lt;SPAN class=""&gt;HTML &lt;SPAN class=""&gt;string &lt;SPAN class=""&gt;using &lt;SPAN class=""&gt;mssparkutils.&lt;SPAN class=""&gt;notebook.&lt;SPAN class=""&gt;exit(), &lt;SPAN class=""&gt;capture &lt;SPAN class=""&gt;it &lt;SPAN class=""&gt;in &lt;SPAN class=""&gt;a &lt;SPAN class=""&gt;Set &lt;SPAN class=""&gt;Variable &lt;SPAN class=""&gt;activity, &lt;SPAN class=""&gt;and &lt;SPAN class=""&gt;use &lt;SPAN class=""&gt;it &lt;SPAN class=""&gt;as &lt;SPAN class=""&gt;the &lt;SPAN class=""&gt;email &lt;SPAN class=""&gt;body &lt;SPAN class=""&gt;in &lt;SPAN class=""&gt;your &lt;SPAN class=""&gt;Outlook &lt;SPAN class=""&gt;activity (&lt;SPAN class=""&gt;assuming &lt;SPAN class=""&gt;it &lt;SPAN class=""&gt;supports &lt;SPAN class=""&gt;HTML &lt;SPAN class=""&gt;content). &lt;SPAN class=""&gt;This &lt;SPAN class=""&gt;approach &lt;SPAN class=""&gt;maintains &lt;SPAN class=""&gt;formatting &lt;SPAN class=""&gt;and &lt;SPAN class=""&gt;ensures &lt;SPAN class=""&gt;readability &lt;SPAN class=""&gt;in &lt;SPAN class=""&gt;email &lt;SPAN class=""&gt;notifications. &lt;SPAN class=""&gt;Regarding &lt;SPAN class=""&gt;SMTP, &lt;SPAN class=""&gt;FabricRestClient &lt;SPAN class=""&gt;currently &lt;SPAN class=""&gt;doesn’t &lt;SPAN class=""&gt;support &lt;SPAN class=""&gt;credential-&lt;SPAN class=""&gt;free &lt;SPAN class=""&gt;SMTP &lt;SPAN class=""&gt;directly. &lt;SPAN class=""&gt;If &lt;SPAN class=""&gt;avoiding &lt;SPAN class=""&gt;username/&lt;SPAN class=""&gt;password &lt;SPAN class=""&gt;is &lt;SPAN class=""&gt;critical, &lt;SPAN class=""&gt;consider &lt;SPAN class=""&gt;using &lt;SPAN class=""&gt;the &lt;SPAN class=""&gt;Outlook &lt;SPAN class=""&gt;activity (&lt;SPAN class=""&gt;if &lt;SPAN class=""&gt;supported &lt;SPAN class=""&gt;in &lt;SPAN class=""&gt;your &lt;SPAN class=""&gt;tenant) &lt;SPAN class=""&gt;or &lt;SPAN class=""&gt;triggering &lt;SPAN class=""&gt;a &lt;SPAN class=""&gt;webhook &lt;SPAN class=""&gt;to &lt;SPAN class=""&gt;Power &lt;SPAN class=""&gt;Automate &lt;SPAN class=""&gt;for &lt;SPAN class=""&gt;notifications, &lt;SPAN class=""&gt;which &lt;SPAN class=""&gt;provides &lt;SPAN class=""&gt;secure &lt;SPAN class=""&gt;and &lt;SPAN class=""&gt;flexible &lt;SPAN class=""&gt;email &lt;SPAN class=""&gt;delivery &lt;SPAN class=""&gt;without &lt;SPAN class=""&gt;handling &lt;SPAN class=""&gt;credentials &lt;SPAN class=""&gt;directly.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If this post&amp;nbsp;helps, then please give us ‘Kudos’ and consider&amp;nbsp;Accept it as a solution&amp;nbsp;to help the other members find it more quickly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 08 May 2025 11:36:15 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4684647#M7749</guid>
      <dc:creator>v-saisrao-msft</dc:creator>
      <dc:date>2025-05-08T11:36:15Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger Alerts Notification for successful/failed Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4690030#M7782</link>
      <description>&lt;P&gt;&lt;SPAN data-teams="true"&gt;Hi Anonymous&lt;/LI-USER&gt;&amp;nbsp;,&lt;BR /&gt;I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.&lt;BR /&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 04:58:10 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4690030#M7782</guid>
      <dc:creator>v-saisrao-msft</dc:creator>
      <dc:date>2025-05-13T04:58:10Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger Alerts Notification for successful/failed Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4695285#M7823</link>
      <description>&lt;P&gt;Hi&amp;nbsp;Anonymous&lt;/LI-USER&gt;,&lt;/P&gt;
&lt;P&gt;May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 May 2025 06:02:38 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4695285#M7823</guid>
      <dc:creator>v-saisrao-msft</dc:creator>
      <dc:date>2025-05-16T06:02:38Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger Alerts Notification for successful/failed Pipelines</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4698163#M7843</link>
      <description>&lt;P&gt;Hi Anonymous&lt;/LI-USER&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We haven’t heard back from you regarding your issue. If it has been resolved, please mark the helpful response as the solution and give a ‘Kudos’ to assist others. If you still need support, let us know.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 May 2025 09:50:21 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Trigger-Alerts-Notification-for-successful-failed-Pipelines/m-p/4698163#M7843</guid>
      <dc:creator>v-saisrao-msft</dc:creator>
      <dc:date>2025-05-19T09:50:21Z</dc:date>
    </item>
  </channel>
</rss>

