Technical Tip: Recent Chromium-based browsers require additional configuration for use with the FortiDLP Email add-in with Outlook 365
Description | Â This article describes how to enable the FortiDLP Email add-in for use with Chromium-based browsers. |
Scope | Any FortiDLP administrators with users of Chromium-based browsers. |
Solution | Symptom: Starting with Chrome 147, Edge 147, and potentially other Chromium-based browsers soon to be released, any users of Outlook or Exchange Online with the FortiDLP Email add-in may see repeated pop-ups saying 'The FortiDLP Email add-in is taking longer than expected.', before timing out at 30 seconds with the email not being sent. Root Cause: Recent Chromium builds have disabled the ability for websites to communicate over localhost connections by default, meaning that the FortiDLP email add-in can no longer communicate with the local FortiDLP Agent. Workaround: Users can select the small icon to the left of the address bar and enable 'Apps on device' manually for any Outlook web URLs they use. ![]() Solution: All Chromium-based browsers provide administrators with the ability to enable this functionality remotely for specific URLs via registry keys on Windows, or MDM profiles on macOS. For Google Chrome, this can also be done via Google Workspace administration for any managed Chrome Browser, and with Microsoft Edge using Microsoft A365 Admin Center. The relevant registry key is LocalNetworkAccessAllowedForUrls. Administrators are recommended to add this key for any users of the FortiDLP Email add-in. Some examples of how to do this for different platforms are provided below for Chrome specifically. Customers are recommended to consult their specific browser documentation for further details on how to configure the LocalNetworkAccessAllowedForUrls setting. Windows: Via Group Policy Objects (GPO), using: Keys should use REG_SZ, with a Name of an increasing integer list. For example:
![]() macOS: On macOS, an MDM profile can be used with the following key settings in the com.google.chrome payload: Linux: Can be configured via Google Workspace Admin via: Devices -> Chrome -> Settings -> Users and browsers -> Local network URLs. ![]() |



