Basic Requirements
If you'd like to install the Virtru for Outlook 365 Add-In (Web, Desktop, Mobile) you will need to check a few things to ensure that your platform is supported in order to install and use the plugin successfully.
First, ensure Virtru's endpoints are allowed in your network: What are the required endpoints for Virtru?
Next, you need to ensure that the browser/platform on your device is supported and that the minimum API requirements are met.
Browsers We Support
Virtru for Outlook 365 is compatible with the following modern browsers:
- Edge (with WebView2 - Chromium-based)
- Chrome
- Safari
- Firefox
For full compatibility, be sure to configure the following: Cookies and Pop-Up Requirements for the Outlook 365 Add-in
We are not compatible with Internet Explorer or Edge (Legacy). Compatibility with other browsers may vary.
Outlook Desktop Versions We Support
To display add-ins in Outlook Desktop, an embedded browser is used. Depending on your configuration, your version of Outlook may not be using a compatible embedded browser. Our add-in is compatible on:
- Windows machines with Office versions using Edge (with WebView2 - Chromium-based)
- Non-subscription Office 2021 or later on Windows 10 or 11
- Microsoft 365 ver. >= 16.0.13530.20424 on Windows 10 or 11
- Outlook for Mac
To confirm which browser your version of Outlook uses, please reference the following: Browsers used by Office Add-ins
API Requirement Sets for Outlook Add-ins
In order to Compose secure messages on Web and Outlook Desktop, our add-in requires a configuration that supports API set 1.8. For reading messages, you need a configuration that supports API set 1.5. Since our mobile compatibility is read-only, iOS and Android apps are supported.
Please note: Due to these API requirements, we only support organizations using Exchange Online. We do not support organizations using Exchange on-premises.
For details on support of API sets by product and platform, refer to the following: Outlook JavaScript API requirement sets
Additionally, our API requirements only support organizations hosted on "Global Azure" which include:
Since our current implementation only supports “Global Azure” this limits us from using the following plans.