Difference between revisions of "Outlook Addin"
Line 10: | Line 10: | ||
** No API to create a new message in inbox folder with custom content. | ** No API to create a new message in inbox folder with custom content. | ||
** Only an API to open the compose form, but this does not allow us to save to the correct location except of drafts folder. It would become sent or a draft. Both we don't want. | ** Only an API to open the compose form, but this does not allow us to save to the correct location except of drafts folder. It would become sent or a draft. Both we don't want. | ||
+ | ** Display only in a small side pane. If we want to open a bigger window for displaying the message, the user is forced to always allow this window every time. | ||
In addition, the API version provided by the users environment must support the needed API functionality. For on-prem installations of Exchange 2016 and 2019, the maximum API requirement set available is 1.5. But for the most functions required, an API requirement set of 1.11 or even higher is needed. Such API requirement set levels are only available if your Outlook is connected to Exchange Online from Office 365 (hosted by Microsoft) ([https://learn.microsoft.com/en-us/javascript/api/requirement-sets/outlook/outlook-api-requirement-sets?view=common-js-preview&tabs=jsonmanifest#requirement-sets-supported-by-exchange-servers-and-outlook-clients source]). Microsoft also did not yet announce, what API requirements set it will support for upcomming Exchange 2025. | In addition, the API version provided by the users environment must support the needed API functionality. For on-prem installations of Exchange 2016 and 2019, the maximum API requirement set available is 1.5. But for the most functions required, an API requirement set of 1.11 or even higher is needed. Such API requirement set levels are only available if your Outlook is connected to Exchange Online from Office 365 (hosted by Microsoft) ([https://learn.microsoft.com/en-us/javascript/api/requirement-sets/outlook/outlook-api-requirement-sets?view=common-js-preview&tabs=jsonmanifest#requirement-sets-supported-by-exchange-servers-and-outlook-clients source]). Microsoft also did not yet announce, what API requirements set it will support for upcomming Exchange 2025. | ||
Line 17: | Line 18: | ||
=== What comes next? === | === What comes next? === | ||
− | Until now, we focused on the official | + | Until now, we focused on the official ''office-js'' API provided by Microsoft. But there is the option to communicate with the connected Exchange server directly, offering some more functionality than the ''office-js'' API. We are investigating the possibility to gain what we want from this path. |
+ | |||
+ | Our focus is now to provide you with an add-in that offers at least some basic functionality soon. But it needs time, so please be patient. | ||
We will keep you updated on this page. | We will keep you updated on this page. |
Revision as of 10:38, 20 December 2024
Contents
Outlook for Web (OWA) and Outlook new
We really tried to develop an add-in for Outlook new and OWA. Unfortunately, the official office-js API from Microsoft does not allow us to create a working regimail add-in. The main reason is the lack of API functionality provided. This is what we are missing (12/2024):
- Composing regimails
- Reading regimails
- No API to set/replace body or delete/replace attachments (source). The alternative would be to create a new message with decrypted content in parallel. But see next point.
- No API to create a new message in inbox folder with custom content.
- Only an API to open the compose form, but this does not allow us to save to the correct location except of drafts folder. It would become sent or a draft. Both we don't want.
- Display only in a small side pane. If we want to open a bigger window for displaying the message, the user is forced to always allow this window every time.
In addition, the API version provided by the users environment must support the needed API functionality. For on-prem installations of Exchange 2016 and 2019, the maximum API requirement set available is 1.5. But for the most functions required, an API requirement set of 1.11 or even higher is needed. Such API requirement set levels are only available if your Outlook is connected to Exchange Online from Office 365 (hosted by Microsoft) (source). Microsoft also did not yet announce, what API requirements set it will support for upcomming Exchange 2025.
Therefore, we recommend you to not update to Outlook new if you want to keep your current regimail add-in working!
Here is how you can stop Outlook from automatic update to Outlook new.
What comes next?
Until now, we focused on the official office-js API provided by Microsoft. But there is the option to communicate with the connected Exchange server directly, offering some more functionality than the office-js API. We are investigating the possibility to gain what we want from this path.
Our focus is now to provide you with an add-in that offers at least some basic functionality soon. But it needs time, so please be patient.
We will keep you updated on this page.
Outlook Legacy
Supported versions
The current AddIn for Microsoft Outlook is available for the following versions:
- Outlook 2019 (32 Bit & 64 Bit)
- Outlook 2021 / Office 365 (32 Bit & 64 Bit)
- Outlook 2024 / Office 365 (32 Bit & 64 Bit)
Please respect that we're no longer supporting Outlook before 2019. Running this e-mail client is also no longer secure. Please consider upgrading to a newer version or how about trying Mozilla Thunderbird?
Functions
The AddIn for Microsoft Outlook offers the following functions:
- create new regify e-mails
- forward, reply and reply all using regify
- reconvert regify mails to ordinary e-mails
- automatically reconvert while receiving
- configure regify settings (account settings)
- invite new users to regify
Setup
The Outlook AddIn is installed automatically (in the correct version) during setup of the regify client. If you do not like to install the Outlook AddIn during setup, please refer the "regify client software deployment documentation" for possible options. It is provided to you by your regify provider.