One more thing worth planning for is restore testing. A backup policy is only useful if you know how long it takes to recover a mailbox, file, or other data when needed. For a university account, documenting who owns the backup process and who is responsible for recovery also helps.

That is disappointing. After all the discussion about an upcoming release, the answer is still "no ETA" more than eight months later. Even basic VLAN ID support during restore would solve a major part of the problem while full SDN support is being worked on.

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..

Hello @opk.giandomenico, MSP Director and remote tenant deployment need to be on the exact same version and build. There is no workaround for this.

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.