|
Integrated apps rejects the add-in because it's already deployed |
2 |
The add-in, possibly under a previous name, is already deployed in your tenant. |
Open the deployed add-in in Integrated apps and update it. Contact support if the update is also rejected. |
| The Report phishing to LibraCyber button isn't in Outlook |
2 |
The add-in hasn't reached this user yet, the user isn't included in the deployment, or no received email is open. |
Forward the email to report@app.mantra.ms, then check the deployment: wait up to 72 hours and restart Outlook, and make sure the user is assigned the add-in in Integrated apps. Contact support if it's still missing after three days. |
| Users still see an old name or icon on the report button |
2 |
The add-in was deployed before May 2026 and has never been updated. |
Update the add-in in Integrated apps using the current link. |
| Users see two report buttons in Outlook |
2, 3 |
Both the add-in and Microsoft's Report button are showing. |
Select Use a non-Microsoft add-in button in User reported settings. Or, connect the Microsoft button as well (Step 3: Microsoft Report button). |
| Microsoft rejects the report mailbox |
3 |
It's a distribution list, which Microsoft no longer accepts. |
Use a shared mailbox as the report mailbox. |
| Reports sent with Microsoft's Report button reach the report mailbox but not Threats
|
3 |
The mailbox isn't forwarding to report-hook@app.mantra.ms: wrong address, automatic forwarding blocked by outbound anti-spam policy, or a data loss prevention rule. |
Check that the forwarding address is report-hook@app.mantra.ms. Then review the outbound policy and DLP exceptions. Contact support if a forwarded copy still doesn't show up in Threats. |
| A user reported with Microsoft's Report junk and nothing reached the security team |
3 |
Junk reports aren't sent to LibraCyber: only Report phishing is. |
Forward it from the Junk Email folder to report@app.mantra.ms. |