Microsoft Defender ATP Logic App Trigger on New Remediation Not Triggering

%3CLINGO-SUB%20id%3D%22lingo-sub-3058005%22%20slang%3D%22en-US%22%3EMicrosoft%20Defender%20ATP%20Logic%20App%20Trigger%20on%20New%20Remediation%20Not%20Triggering%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3058005%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBeen%20working%20on%20trying%20to%20get%20the%20MDATP%20Connector%20in%20Logic%20Apps%20to%20trigger%20on%20when%20a%20new%20remediation%20is%20triggered.%26nbsp%3B%20The%20logic%20app%20saves%20and%20runs%20without%20error%2C%20but%20the%20history%20shows%20skipped.%26nbsp%3B%20The%20response%20in%20the%20history%20is%20status%20code%20202%2C%20however%20I've%20created%20(and%20closed%2C%20and%20created%20again)%20remediations%20in%20365%20Security%20and%20the%20actions%20never%20seem%20to%20get%20triggered.%3CBR%20%2F%3E%3CBR%20%2F%3EDoes%20anyone%20have%20any%20insights%20on%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3058005%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAutomation%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hello,

 

Been working on trying to get the MDATP Connector in Logic Apps to trigger on when a new remediation is triggered.  The logic app saves and runs without error, but the history shows skipped.  The response in the history is status code 202, however I've created (and closed, and created again) remediations in 365 Security and the actions never seem to get triggered.

Does anyone have any insights on this?

0 Replies