Version 8 of Veeam Backup for Microsoft 365 introduced proxy pools to improve performance and scalability in large installations. By logically combining several backup proxies, a proxy pool enables dynamic load distribution of backup and restore traffic, removing bottlenecks and accelerating processes.
Make sure you are running Veeam Backup & Replication version 12.3.1 or later to perform an in-place upgrade to Windows Server 2025, since version 13.0.1 enables in-place upgrades from this version. First, create a full backup of your existing Veeam configuration database and install the updated Veeam Backup & Replication 13.0.1.180 ISO, which is now available for Windows Server 2025.
Veeam Backup for Microsoft 365 consists of Backup proxy servers, Backup Proxy Pools, Backup Local repositories, and Object storage repositories. These are configured as locations for Microsoft 365 backup data. These can be configured on-premises, in the cloud, or in a hybrid configuration.
Windows Backup proxy servers are auxiliary servers that you can configure to improve performance, scalability, and flexibility.
Veeam Backup Enterprise Manager v13 is a centralized management and reporting tool designed by Veeam Software for overseeing Veeam Backup & Replication deployments. It allows administrators to control and monitor their backup infrastructure through a web-based interface, making it easier to manage large-scale environments.
Veeam Backup & Replication v13 is available for Microsoft Windows as self-managed installable software and as a fully managed software appliance.
The Veeam Backup & Replication console is installed on the backup server automatically when you install Veeam Backup & Replication v13. You can utilize the web user interface (UI) or install the Veeam Backup & Replication console on a dedicated computer to access Veeam Backup & Replication remotely.
Veeam released a version of Veeam Backup for Microsoft 365 v8.2.0.2202 (P20251031) on November 06, 2025, and it resolved the issue – A backup job may fail when processing Archive Mailbox objects with the following error:
Processing archive mailbox: username@organization.com failed with error: Mailbox is not fully configured.
These can only be installed on Veeam Backup & Replication Management Servers.
There are benefits such as enhanced scalability, flexibility, and security when a restore portal and a REST API are installed on a separate computer. This architecture increases the total performance and dependability of the system by enabling autonomous development, scaling, and maintenance of each component.
When you install Veeam Backup for Microsoft 365, the PowerShell Toolkit is automatically installed on the backup server. If you want to run Veeam Backup for Microsoft 365 PowerShell sessions on remotely, you can install the PowerShell Toolkit on a dedicated machine.
When you install Veeam Backup for Microsoft 365, its console is automatically installed on the backup server. If you want to access Veeam Backup for Microsoft 365 remotely, you can install the Veeam Backup for Microsoft 365 console on a dedicated machine. You can install as many remote consoles as you need.
Veeam Backup & Replication should be upgraded after Veeam Backup Enterprise Manager is upgraded.
Veeam released the Backup & Replication v12.3.2.4165 on October 14, 2025.
One backup job can protect the data of only one tenant.
After you’ve added a Microsoft Entra ID tenant to the backup infrastructure, you can backup and restore Entra ID resources managed by the tenant.
A log backup repository is a storage area where Veeam Backup for Microsoft Entra ID keeps backups of audit and sign-in logs from protected Microsoft Entra ID tenants.
Beginning with version 12.3, the Veeam Backup & Replication solution allows you to add Microsoft Entra ID tenants to the backup infrastructure and manage data protection and recovery operations for these tenants from a single console.
This section describes how to recover (or move) a backup VM to Microsoft Azure.
This section describes creating a backup copy job that off-loads to the Azure blob after performing a full backup. It will not use the Azure Blob archive tier.
This section describes creating a backup job that backs up at local repositories to sync backup files with Azure cloud and off-loads Azure blob after performing a full backup. It would be best to have a scale-out repository ready before beginning this backup job.
This procedure immediately creates a backup job to backup to Azure Blob Repository without local repositories.