1. Introduction

Purpose of the connector, supported environments and what changes in versions 24.08 and 26.04.

What the Connector Is For

Exchange Connector keeps selected vtenext data synchronized with Microsoft 365 or Microsoft Exchange.

It can synchronize:

Synchronization can work in both directions: changes made in vtenext can be sent to Exchange and changes made in Exchange can be brought back into vtenext, depending on the enabled features.

Two connection methods

For end users, the main difference is how the account is connected: Microsoft 365 uses Microsoft sign-in and authorization, while Exchange Server uses Exchange credentials and selected folders.

Who configures what

The vtenext administrator configures the connector, selects what must be synchronized and defines field mappings. Each user then completes their own account connection and selects the folders to use when required.

Once configuration is complete, the connector works automatically in the background.

What Changes from 20.04.xx to Versions 24.08 and 26.04

The most important difference from version 20.04 is not only Microsoft Graph: the way the connector is integrated into vtenext also changes.

From 20.04 to the new structure

In version 20.04, Exchange Connector was installed using the legacy dedicated procedure and was not registered as a standard vtenext vtlib module.

In versions 24.08 and 26.04, the connector is managed as a real vtenext module/extension. After the first migration, future upgrades can therefore be handled through the normal module update procedure.

For this reason, moving from 20.04.xx to 24.08 or 26.04 requires a specific migration and a one-time module registration script.

If Microsoft 365 is used

The new connector generation uses Microsoft Graph for Microsoft 365 / Exchange Online. After migration, the Office365 configuration and user connections must be checked.

The connector can use either vtenext Proxy or a Custom Microsoft App.

If Exchange Server is used

Exchange Server installed on the customer infrastructure continues to use EWS. Supported configurations include Exchange 2016, Exchange 2019 and Exchange Server Subscription Edition.

Future upgrades

Once Exchange Connector is already using the new structure, for example version 24.08, moving to 26.04 no longer requires the registration script.