Dear @opk.giandomenico
Thanks for the feedback.
We understand that frequent releases combined with strict version parity can create additional overhead for MSP environments with many tenants.
Unfortunately, there’s currently no workaround for the matching-version requirement.
We take feedback like this into consideration when evaluating future improvements to release management and update workflows for MSP environments.
Considering i've updated Director and all customer one week ago and considering 11.2.2 has been released something like some days ago now i need to update all again. It need alot of time..
Microsoft has confirmed the retirement timeline for Exchange Web Services (EWS) in Exchange Online.
The retirement happens in phases:
August 31, 2026: Recommended deadline to complete configuration for zero disruption.
October 1, 2026: EWS disabled by default for tenants without an allow list configured (Backups will start failing).
April 1, 2027: Microsoft will permanently shut down EWS with no exceptions.
What NAKIVO users need to do
NAKIVO Backup for Microsoft 365 uses EWS for Exchange Online and group mailbox backups. Affected users need to add the Azure Client ID for their NAKIVO Backup & Replication instance to the AppID allow list for their tenant before August 31, 2026.
How to Configure the EWS Allow List:
We have published a full, step-by-step walkthrough in our Help Center and it takes only a few minutes to complete:
View the EWS allow‑list instructions.
Note: Complete the configuration by the end of August to ensure that user, group and shared mailbox backups continue to run in NAKIVO Backup & Replication before Microsoft begins disabling EWS.
Is version parity required between the MSP Director and the remote tenant's NAKIVO deployment, or is there a workaround to connect them despite a version mismatch? Updating the MSP Director and every customer's instance every time is too time-consuming.
MSP Director version: 11.2.1.104556
Remote Tenants: 11.2.2.108504