Fix The HTTP request was forbidden with client authentication scheme ‘Anonymous’ issues
EWS must now be specifically enabled at the organization and mailbox levels in order for backups to be successful after Microsoft fixed this behaviour.
EWS must now be specifically enabled at the organization and mailbox levels in order for backups to be successful after Microsoft fixed this behaviour.
This is intended for Veeam Backup for Microsoft 365 customers who upgraded from a previous version or for Microsoft 365 tenants that were already protected before this default was implemented and may wish to adjust their current setup.
Veeam released Veeam Backup for Microsoft 365 v8.6 on September 14, 2026, which included new features and Enhancements. It also fixed some bugs.
Microsoft begins disabling EWS tenant by tenant on October 1, 2026. Tenants that have not explicitly enabled EWS will be blocked automatically as the rollout proceeds.
You can configure Microsoft 365 with an MFA-enabled account for notification settings. This can be used to send email notifications about backup job results.
Veeam Backup for Microsoft 365 uses the Veeam Azure archiver appliance, a small virtual machine deployed in Azure, to efficiently move backed-up M365 data (Exchange, SharePoint, Teams, OneDrive) into Azure Archive Storage (cold tier) for long-term, low-cost retention, minimizing data egress and speeding up copy jobs by processing data locally within Azure.
The upgrade failed because the SSH public key fingerprint of the Linux proxy does not match Veeam’s expectations. This typically happens when the proxy’s SSH keys are changed, the server is rebuilt, or the fingerprint stored in Veeam is outdated.
Veeam released Veeam Backup for Microsoft 365 v8.3.0.2201 on December 18, 2025, which included new features and Enhancements. It also fixed some bugs.
In Veeam Backup for Microsoft 365 version 8.2, adding a Microsoft Azure Archive Storage repository involves a multi-step wizard within the Backup Infrastructure view. This repository type is specifically designed for long-term retention and supports Backup Copy jobs.
After upgrading Veeam Backup for Microsoft 365 to 8.2.0.2202 (P20251031), a SharePoint site backup error message appeared.
We will add Azure Blob Storage, which lacks immutability, to our Veeam Backup for Microsoft 365 Infrastructure in the following steps.
Network Attached Storage can also be used with Veeam Backup for Microsoft 365 as a backup repository. These Network Attached Storage devices can be accessed and configured via a shared folder on your computer or any other physical device accessed using theΒ SMB protocol.
To add a local directory or Direct Attached Storage (DAS) as a backup repository in Veeam Backup for Microsoft 365, you need to use the Veeam Backup for Microsoft 365 console and select the server hosting the storage as a backup proxy.
Linux Backup proxy servers are auxiliary servers that you can configure to improve performance, scalability, and flexibility.
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.
When you add an organization using the modern app-only authentication method, Veeam Backup for Microsoft 365 automatically grants permissions for Microsoft Entra applications.
Anyway, if you prefer to use a custom application of your own, grant all the permissions as below.
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.
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.