PAB Enhancement: Outlook Report Message add-in

Answered

Comments

4 comments

  • Official comment
    Avatar
    Maddy Townsend

    Hi Jacob,

    Thanks for the great suggestion and for including links to a previous community board post as well as that Microsoft article. I've submitted a feature request on your behalf which is sent to our development team for their review. 

    Maddy
    KnowBe4

    Comment actions Permalink
  • Avatar
    Laura Puzo

    Maddy,

    Can you tell us if this is being considered and if yes, a rough timeline when we might see it?

    0
    Comment actions Permalink
  • Avatar
    Kaiser

    Laura,

    Thanks for reaching out! At this time the feedback provided by our community is still being reviewed and considered by our development teams. As such, there isn't an available timeline or estimate on if this will be developed. However, it would make a great feature! 

    Please let us know if you have more feedback or suggestions for our team. The more feedback we get, the more our development team sees an interest in certain products and content!

    Kaiser

    KnowBe4

    0
    Comment actions Permalink
  • Avatar
    Alex Rourke (Edited )

    We would love this feature as well, though I think there might be a novel workaround here. All Microsoft's Report Message Add-In does when an email is reported is forward an attachment of the email in question to either junk@office365.microsoft.com or phish@office365.microsoft.com. Per this setup article for Microsoft's add-in, it may be possible to intercept these messages when reporting and do something with them. On the KnowBe4 side, it doesn't look like emails are reported this way.

    You choose which email addresses the emails get reported to in the PAB configuration. It may be possible to add phish@office365.microsoft.com to that list so that these get reported, assuming the email is formatted properly to enable this. On the flip side, if the PAB functionality could be replicated using an inbound email address (like Office 365 does), you could use Microsoft's add-in and set up transport rules to also forward messages to KnowBe4 when reporting, excluding messages which have the Phish testing email header. This could be problematic because the phish test header is in the attached email header, not the header of the email itself. Another transport rule could intercept phish test emails (based on header) and not allow them to be reported to Microsoft. You could also make this rule send the user an email saying they successfully identified a phish testing email.

    I think adding Microsoft's phish reporting address to the "also send to" in the PAB setup might work. Setting things up the other way around probably won't (at least for now), though it is feasible. Just some food for thought. 

    1
    Comment actions Permalink

Please sign in to leave a comment.