<?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 managing incident from dynamic emails using MSGRAPH integration in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/managing-incident-from-dynamic-emails-using-msgraph-integration/m-p/599166#M7262</link>
    <description>&lt;P&gt;Hello everyone,&lt;/P&gt;
&lt;P&gt;I am looking for a solution to handle a specific situation related to incident activation from an email, using the MSGRAPH integration.&lt;/P&gt;
&lt;P&gt;Typically, to activate an incident, I classify it based on a static email subject. Then, I configure the "type" to trigger the corresponding playbook. However, this approach seems limited by the fact that the email subject must always be static.&lt;/P&gt;
&lt;P&gt;I am now dealing with a scenario where the email subject cannot always be static but contains only some dynamic parts of text. I would like to understand if there is a way to correctly trigger the playbook in these cases, using only parts of the subject for classification.&lt;/P&gt;
&lt;P&gt;Is it possible to implement this kind of management in email classification? If anyone has faced a similar situation or has ideas on how to proceed, I would appreciate any suggestions.&lt;/P&gt;
&lt;P&gt;Thanks in advance for your help!&lt;/P&gt;</description>
    <pubDate>Tue, 01 Oct 2024 10:22:16 GMT</pubDate>
    <dc:creator>MF762</dc:creator>
    <dc:date>2024-10-01T10:22:16Z</dc:date>
    <item>
      <title>managing incident from dynamic emails using MSGRAPH integration</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/managing-incident-from-dynamic-emails-using-msgraph-integration/m-p/599166#M7262</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;
&lt;P&gt;I am looking for a solution to handle a specific situation related to incident activation from an email, using the MSGRAPH integration.&lt;/P&gt;
&lt;P&gt;Typically, to activate an incident, I classify it based on a static email subject. Then, I configure the "type" to trigger the corresponding playbook. However, this approach seems limited by the fact that the email subject must always be static.&lt;/P&gt;
&lt;P&gt;I am now dealing with a scenario where the email subject cannot always be static but contains only some dynamic parts of text. I would like to understand if there is a way to correctly trigger the playbook in these cases, using only parts of the subject for classification.&lt;/P&gt;
&lt;P&gt;Is it possible to implement this kind of management in email classification? If anyone has faced a similar situation or has ideas on how to proceed, I would appreciate any suggestions.&lt;/P&gt;
&lt;P&gt;Thanks in advance for your help!&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2024 10:22:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/managing-incident-from-dynamic-emails-using-msgraph-integration/m-p/599166#M7262</guid>
      <dc:creator>MF762</dc:creator>
      <dc:date>2024-10-01T10:22:16Z</dc:date>
    </item>
    <item>
      <title>Re: managing incident from dynamic emails using MSGRAPH integration</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/managing-incident-from-dynamic-emails-using-msgraph-integration/m-p/599442#M7268</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/292722"&gt;@MF762&lt;/a&gt;, I think this a XSOAR question, is that right?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Oct 2024 15:51:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/managing-incident-from-dynamic-emails-using-msgraph-integration/m-p/599442#M7268</guid>
      <dc:creator>jmazzeo</dc:creator>
      <dc:date>2024-10-03T15:51:33Z</dc:date>
    </item>
  </channel>
</rss>

