Get instant support with our search!
MetaCompliance Report Phish Button Options
We have a few options available for our MetaCompliance 'Report button' depending on which works best with your environment.
- Microsoft Report Button Integrated with MetaCompliance - Outlook
- MetaCompliance Phish Mail Report Button - Outlook
- MetaCompliance Gmail Phish Report Button - Gmail
We have summarised the pre-requisites, benefits, and drawbacks/limitations of each button below.
| # | Report Button Options: | Requirements: | Can I customise the text on the button? | Supports more than 1 language? | Can integrate with MS Defender |
| 1. | Microsoft Integrated MetaCompliance Report Phish Button (Outlook) | Microsoft O365 License/ Environment + SSO | ❌ | ✔️ | ✔️ |
| 2. | MetaCompliance Phish Mail Report Button (Outlook) | Microsoft O365 License/ Environment + SSO | ✔️ | ❌ | ✔️ |
| 3. | MetaCompliance Gmail Report Button (Google Workspace) | Google Workspace Gmail License/ Environment + SSO | ✔️ | ❌ | ❌ |
1. Microsoft Report button Integrated with MetaCompliance
If you want your users to use the 'default' Microsoft button it will look like the following:
Requirements for the Microsoft Report button Integrated with MetaCompliance
- Microsoft Exchange Online is required for the Microsoft Integrated Report Button.
- A mail flow rule in Exchange would be required to redirect Phish simulation emails from the shared mailbox to your MetaCompliance mailbox. This ensures only simulation emails are forwarded to MetaCompliance, while real phish stay in Defender.
- We will not be handling any other emails that are reported as phishing emails. ONLY MetaCompliance Phish simulation emails.
High level overview: - Set up guide:
Pros - Microsoft Report button Integrated with MetaCompliance
✅ Supports full multi-language out of the box, as it uses Microsoft's native button
✅ Microsoft look and feel, which your end users would be familiar with, reducing user confusion.
✅ Can be integrated with MS Defender for your team to analyse further.
✅ No plugins or user training required - uses Microsoft's native button.
✅ More accurate reporting data, as all 'MetaCompliance simulated emails' are reported and captured
✅ Quick, low-risk setup with no special licensing required when using the mail flow method.
Cons - Microsoft Report button Integrated with MetaCompliance
❌ The text is not customisable - (Contains default Microsoft text) - will not inform the user that it 'was' a simulated phish or not.
❌ The 'Report Junk' option does not to do anything at present.
❌ This button does not notify the end user that it was a simulated phishing email or an actual phishing email.
2. MetaCompliance Phish Mail Report Button
If you would like your end user to use the existing MetaCompliance Phish Mail Report Button it will look like the following:
Requirements - MetaCompliance Phish Mail Report Button
- Microsoft Exchange Online is required for this report button.
- You must have SSO configured on Microsoft IDP (Identity Provider)
- You will also be required to complete and return the Outlook_Web_Plugin-Customer Template for the configuration of this report button.
- We will not be handling any other emails that are reported as phishing emails. ONLY MetaCompliance Phish simulation emails.
- High level overview / workflow:
-
Please note we have to configure settings on our side BEFORE you deploy this button.
Pros - MetaCompliance Phish Mail Report Button
✅ The text is customisable.
✅ Notifies your end users if it was a 'MetaCompliance simulated phishing email' and if it was not a Metacompliance simulated Phish it would state that it has been forward to your security team for future analysation.
✅ Can be integrated with MS Defender for your team to analyse further.
✅ Reported MetaCompliance simulated emails will be available in the MetaCompliance reports.
Cons - MetaCompliance Phish Mail Report Button
❌ You can only choose 1 language. You can provide the template values in your preferred language but it will only display 1 x language example: German / Portuguese / Spanish / English etc
❌ You cannot customise the icon/logo as it is hard-coded.
3. - MetaCompliance Phish Mail Report Button
Requirements - MetaCompliance Phish Mail Report Button
- You must have SSO configured on Google IDP (Identity Provider).
- You will also be required to complete and return the 'Gmail-PhishReportButton' template for the configuration of this report button.
- We will not be handling any other emails that are reported as phishing emails. ONLY MetaCompliance Phish simulation emails.
- Guide: https://support.metacompliance.com/hc/en-gb/articles/4405180995601-How-to-install-the-Gmail-Phish-Reporter-Report-Button
- Please note we have to configure settings on our side BEFORE you deploy this button.
Pros - MetaCompliance Phish Mail Report Button
✅ The text is customisable.
✅ Notifies your end users if it was a 'MetaCompliance simulated phishing email' and if it was not a Metacompliance simulated Phish it would state that it has been forward to your security team for future analysation.
✅ Reported MetaCompliance simulated emails will be available in the MetaCompliance reports.
Cons - MetaCompliance Phish Mail Report Button
❌ Limited functionality due to Google workspace platform.
❌ You cannot customise the icon/logo as it is hard-coded.