Skip to main content
Skip table of contents

Phishing Report Button missing in Outlook v.1.2023.411.200 and OWA

Read this article in: English, Deutsch, Dutch, French

With the recent update to Outlook version 1.2023.411.200 and Outlook Web Access (OWA), it’s been observed that the SoSafe Phishing Report Button Add-in is sometimes not displayed on the ribbon bar as it was previously.
 

Currently, the recommended solution is manual addition of the SoSafe Phishing-Reporting Add-in to the ‘Message surface’. To make it visible, users must pin the SoSafe Phishing Report Button Add-in to the Message surface.

Here’s a step-by-step guide on how to do this. The steps are the same for both the Outlook desktop client as well as OWA.

New Outlook v.1.2023.411.200 (and higher) and OWA

In the new Outlook version and even the new OWA version you will find the Phishing Report Button behind the Apps Icon in the mail preview.

Apps Icon in the mail:

image-20240410-144824.png

Phishing Report Button:

image-20240410-144837.png

OWA (none standard version)

1. Access Settings: 

Click on the settings icon, usually located in the top right corner of the Outlook interface.

rtaImage.jpeg

2. Navigate to Mail settings:

Within the settings menu, go to ‘Mail’. From there, select ‘Customize actions’.

rtaImage (1).jpeg

3. Proceed to Message surface:

In ‘Customized actions’, you’ll find a section labeled ‘Message surface’.

rtaImage (2).jpeg

 4. Enable the SoSafe Phishing-Reporting Add-on:

Locate the ‘SoSafe Phishing-Reporting’ option in the list. Check the box beside it to enable the Add-in on the message surface.

rtaImage (3).jpeg

5. Save changes.

After completing these steps, the SoSafe Phishing Report Button should be visible on the ‘Message surface’ in Outlook. If it’s still missing, consider restarting Outlook or investigate if there’s other configurations that might be preventing the Add-in from displaying.

rtaImage (4).jpeg

If issues persist, or if you need further assistance, please contact Microsoft directly.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.