Overview

In late 2023, Microsoft has launched a new Outlook client, separate from the classic one, and you may have noticed the new Outlook client in your Windows machine and you're wondering if you can move your Kerio account/s to it. 

Solution

Currently, the Outlook (new) client has limited support with 3rd party providers. While it does boast native oAuth login with Gmail and Yahoo, Exchange ActiveSync and COM add-ins is missing.

The only current way of syncing your Kerio Connect account with the Outlook (new) client is to use IMAP, however, this only provides a limited experience, as IMAP protocol will not allow you to sync your calendars and contacts.

As for the KOFF plugin, that is also not compatible, mainly because it is a COM Add-in, and the new Outlook only supports web add-ins. More information can be found in the below Microsoft resources:

• Feature comparison between new Outlook and classic Outlook - Microsoft Support
• Add-ins in the new Outlook for Windows | Microsoft Community Hub

Please note that a feature request has been raised with our product management team to address this compatibility matter. However, there is no guarantee that this feature will be implemented. 

Summary

While the new Microsoft Outlook client does not currently support the Kerio Outlook Connector (KOFF), users can still sync their Kerio Connect account using IMAP. However, this provides a limited usage scope. A feature request has been raised to address this compatibility issue.

FAQ

1. Can I use the Kerio Outlook Connector (KOFF) with the new Microsoft Outlook client?
   No, the new Microsoft Outlook client only supports web-addins, and the KOFF is a COM add-in.
2. What can I do to sync my Kerio Connect account with the new Microsoft Outlook client?
   You can set up your Kerio Connect account in the new Microsoft Outlook client using IMAP. However, this provides a limited usage scope.
3. Will there be a solution to this compatibility gap?
   A feature request has been raised to address this compatibility gap, but there is no guarantee that this feature will be implemented.