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.
Registering a new Microsoft Entra ID application automatically is unavailable if you want to back up team chats and have selected Team chats at the Organization Deployment Type step.
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.
These can only be installed on Veeam Backup & Replication Management Servers.
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.
Veeam Backup for Microsoft Entra ID Logs to protect tenant audit and sign-in logs.
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.
This section describes how to add Azure Blob Object Storage Repositories as the performance tier (hot tier), a capacity tier (cool tier) and an archive (cold tier) tier of the scale-out repository.
A scale-out backup repository allows for horizontal scaling for multi-tier data storage.
These steps show how to add Microsoft Azure Archive Storage to the backup infrastructure as a backup repository. This repository can only be used as an archive extension of the scaled-out backup repository.
Veeam Backup & Replication allows you to prevent data deletion from the object storage repository by making it momentarily immutable and protecting data from malware activity by keeping several versions of a single backup.
To add Microsoft Azure Blob Storage as an object repository without immutability, you normally integrate the Azure Blob Storage service to store and manage objects without enforcing retention or immutability requirements.