Memory leak caused by establishing connections to Exchange Online

Question

This issue affects only Adaxes 2023.2 Update 1 - version 3.16.21515. It has been fixed in Adaxes 2023.2 Update 2 - version 3.16.21627

 

Description

If a Microsoft 365 tenant and a corresponding Azure AD domain are registered in Adaxes using different application accounts or the same application account but different client secrets, a memory leak will occur on the computer where Adaxes service is installed.

 

Cause

The Connect-ExchangeOnline cmdlet from the EXOv3 PowerShell module used by Adaxes has a known issue that causes a memory leak when establishing a connection.

If different client secrets are used, Adaxes will re-establish a new connection every minute instead of holding a single connection.

 

Solution

1. Update the credentials of each registered Azure AD domain and the corresponding Microsoft 365 tenant so that the same Azure app with the same client secret is used.
2. On the computer where Adaxes service is installed, navigate to the \AppData\Local\Temp folder that belongs to the Adaxes service account and delete all folders whose name starts with tmpEXO. This must be done while the Softerra Adaxes Service Windows service is stopped.