Veeam Backup for Microsoft 365 8
Release Notes
User Guide

Veeam Backup for Microsoft 365 8 Release Notes

This document provides last-minute information about Veeam Backup for Microsoft 365 v8, including system requirements, installation, and upgrade procedure, as well as relevant information on technical support, documentation, online resources, and more.

The release version of Veeam Backup for Microsoft 365 v8 is available for download at: https://www.veeam.com/products/saas/backup-microsoft-office-365-download.html starting from September 3, 2024.

See next:

System Requirements

Unless otherwise stated, all 3rd party software must be at the latest update and/or patch level.

Supported Organizations

Veeam Backup for Microsoft 365 supports the following Microsoft organizations:

  • Microsoft 365, including Exchange Online and SharePoint Online
  • Microsoft Exchange Server 2019 or 2016
  • Microsoft SharePoint 2019, 2016 or Subscription Edition

Veeam Backup for Microsoft 365 Server

Hardware

  • CPU: any modern multi-core x64 processor, 8 cores minimum.
  • Memory: 16 GB RAM minimum. Additional RAM and CPU resources improve backup, restore, and search performance.

    If you plan to deploy Veeam Backup for Microsoft 365 on a VM with dynamic memory allocation, such VM must have 32 GB RAM minimum.

  • Disk Space: 3 GB for product installation and additional free space required for product logs and for the PostgreSQL instance and the NATS server deployment (if using the default installation).

    For optimal performance, we recommend to use SSD drive.

OS

64-bit version of the following Microsoft Windows operating systems are supported:

  • Microsoft Windows Server 2016, 2019, 2022
  • Microsoft Windows 10 (versions 21H2, 22H2)
  • Microsoft Windows 11 (versions 22H2, 23H2)
  • Microsoft Windows Server Core editions 2016 (LTSC 1607), 2019 (LTSC 1809), 2022

Software

  • Microsoft ASP.NET Core Runtime 8.0.7 or later.
  • Microsoft .NET Desktop Runtime 8.0.7 or later.
  • Microsoft .NET Runtime 8.0.7 or later.
  • Local or remote installation of PostgreSQL 15.8 or later.

    For optimal performance, we recommend to use SSD drive.

  • Local or remote installation of the NATS server 2.10.18 or later.
  • To use PowerShell, Windows PowerShell 7.4.2 or later is required.
  • (optional) To export Exchange folders and items as Personal Folder Files (.PST), it a 64-bit version of Microsoft Outlook for Microsoft 365, Microsoft Outlook 2010, or later must be installed on the machine with Veeam Explorer for Microsoft Exchange.
  • (optional) Veeam Backup & Replication or Veeam Agent for Microsoft Windows for the Veeam Backup for Microsoft 365 server backup. Application-aware processing of the Veeam Backup for Microsoft 365 server is supported by Veeam Backup & Replication v12 or later, and Veeam Agent for Microsoft Windows 6.0 or later.

Backup Proxy

Hardware

  • CPU: any modern multi-core x64 processor, 4 cores minimum.
  • Memory: 16 GB RAM minimum. Additional RAM and CPU resources improve backup, restore, and search performance.

    If you plan to deploy Veeam Backup for Microsoft 365 on a VM with dynamic memory allocation, such VM must have 32 GB RAM minimum.

  • Disk space: 3 GB for backup proxy installation and additional free space for product logs.

OS

64-bit version of the following Microsoft Windows operating systems are supported:

  • Microsoft Windows Server 2016, 2019, 2022
  • Microsoft Windows 10 (versions 21H2, 22H2)
  • Microsoft Windows 11 (versions 22H2, 23H2)
  • Microsoft Windows Server Core editions 2016 (LTSC 1607), 2019 (LTSC 1809), 2022

64-bit versions of the following Linux distributions are supported:

  • RHEL 8.8 LTS, 8.10 LTS, 9.0 LTS, 9.2 LTS, and 9.4 LTS
  • Ubuntu: 20.04 LTS, and 22.04 LTS

Software

  • Microsoft .NET Runtime 8.0.7 or later.

    Note that if you want to manually install Microsoft .NET Runtime on Linux backup proxy servers, you should install .NET packages from the Microsoft package feed.

  • To use PowerShell, Windows PowerShell 7.4.2 or later is required.

REST API Host

Hardware

  • CPU: any modern multi-core x64 processor, 8 cores minimum.
  • Memory: 16 GB RAM minimum. Additional RAM and CPU resources improve backup, restore, and search performance.

    If you plan to deploy Veeam Backup for Microsoft 365 on a VM with dynamic memory allocation, such VM must have 32 GB RAM minimum.

  • Disk Space: 1 GB for Veeam Backup for Microsoft 365 REST API server installation and additional free space for product logs.

OS

64-bit version of the following Microsoft Windows operating systems are supported:

  • Microsoft Windows Server 2016, 2019, 2022
  • Microsoft Windows 10 (versions 21H2, 22H2)
  • Microsoft Windows 11 (versions 22H2, 23H2)
  • Microsoft Windows Server Core editions 2016 (LTSC 1607), 2019 (LTSC 1809), 2022

Software

  • Microsoft ASP.NET Core Runtime 8.0.7 or later.
  • Microsoft .NET Desktop Runtime 8.0.7 or later.
  • Microsoft .NET Runtime 8.0.7 or later.

Backup Target

Backup can be performed to the following storage systems accessible from a Veeam Backup for Microsoft 365 server or a backup proxy:

  • Local folder on a backup proxy.
  • Direct Attached Storage (DAS) connected to the backup proxy, including external USB/eSATA drives and raw device mapping (RDM) volumes.
  • Storage Area Network (SAN). Veeam Backup for Microsoft 365 server or backup proxy must be connected to the SAN fabric via hardware or virtual HBA, or software iSCSI initiator.
  • Network Attached Storage (SMB shares version 3.0 or later).

    Note that this support is experimental and will be dropped in future versions of Veeam Backup for Microsoft 365.

  • Amazon S3 object storage.
  • Microsoft Azure Blob Storage.
  • IBM Cloud Object Storage.
  • Wasabi Cloud storage;
  • Any S3 Compatible object storage device fully compatible with the AWS S3 operations and AWS S3 Signature Version 4 standard.

Storage volumes hosting a backup repository must be formatted with NTFS or ReFS.

Backup Copy Target

Backup copy can be performed to the following storage systems accessible from a Veeam Backup for Microsoft 365 server or a backup proxy:

  • Amazon S3 object storage.
  • Amazon S3 Glacier.
  • Microsoft Azure Blob Storage.
  • Microsoft Azure Archive Storage.
  • IBM Cloud Object Storage.
  • Wasabi Cloud storage.
  • Any S3 Compatible object storage device fully compatible with the AWS S3 operations and AWS S3 Signature Version 4 standard.

Veeam Explorer for Microsoft Exchange

Veeam Explorer for Microsoft Exchange requires Veeam Backup for Microsoft 365 v8 or Veeam Backup & Replication version 12 or later or Veeam Backup & Replication Console version 12 or later.

To learn more about system requirements for Veeam Explorer for Microsoft Exchange, see the user guide.

Veeam Explorer for Microsoft SharePoint

Veeam Explorer for Microsoft SharePoint requires Veeam Backup for Microsoft 365 v8 or Veeam Backup & Replication version 12 or later or Veeam Backup & Replication Console version 12 or later.

To learn more about system requirements for Veeam Explorer for Microsoft SharePoint, see the user guide.

Veeam Explorer for Microsoft OneDrive for Business

Veeam Explorer for Microsoft OneDrive for Business is distributed in one package with Veeam Explorer for Microsoft SharePoint. For system requirements, see the user guide.

Veeam Explorer for Microsoft Teams

Veeam Explorer for Microsoft Teams requires Veeam Backup for Microsoft 365 v8 or Veeam Backup & Replication version 12 or later or Veeam Backup & Replication Console version 12 or later.

To learn more about system requirements for Veeam Explorer for Microsoft Teams, see the user guide.

Permissions Changelog

Microsoft Entra Application Permissions

The following permission changes apply to a Microsoft Entra application that you use to connect to your Microsoft 365 organization.

The following Microsoft Graph API permissions and roles become mandatory in Veeam Backup for Microsoft 365 v8 compared to previous versions:

  • Exchange.ManageAsApp
  • Global Reader role

In Veeam Backup for Microsoft 365 v8, the following new Microsoft Graph API permissions must be assigned to the application:

  • For backup purposes:

    • ChannelMember.Read.All (Application type)
  • For restore purposes:

    • ChannelMember.ReadWrite.All (for restore via a device code: Delegated type)
    • ChannelMember.ReadWrite.All (for restore via a certificate: Application type)
    • Files.ReadWrite.All (Application type)

For the full list of permissions that must be assigned to a Microsoft Entra application, see Microsoft Entra Application Permissions.

Service Account on Windows

You can use a custom service account for running a backup proxy service on Windows hosts. For the list of permissions required for such an account, see Permissions for Service Account on Windows.

Service Account on Linux

You can use a custom service account for running a backup proxy service on Linux hosts. For the list of permissions required for such an account, see Permissions for Service Account on Linux.

Amazon S3 Storage Permissions

For the updated list of permissions that must be granted to access Amazon S3 buckets and folders and create backup repositories, see Amazon S3 Storage Permissions.

Azure Blob Storage Permissions

For the updated list of permissions that must be granted to a user account that you use to access Azure Blob Storage and Azure Blob Storage Archive, see Azure Blob Storage Permissions.

For the updated list of permissions that must be granted to a user account that you use to create a Microsoft Entra application for the Microsoft Azure service account if you want to use the Azure Archiver appliance, see Permissions for Azure Archiver Appliance.

Deprecations

The following support is deprecated in Veeam Backup for Microsoft 365 v8:

  • Modern authentication that allows for using legacy auth protocols.
  • Azure Blob Storage Germany region.

The following support is planned for deprecation in future Veeam Backup for Microsoft 365 releases:

  • Basic authentication for Microsoft 365 tenants. In Veeam Backup for Microsoft 365 v8, adding Microsoft 365 organizations using the basic authentication method is only available in the Microsoft Entra China region through REST API and PowerShell.

    • Auxiliary backup accounts for SharePoint processing.
  • Microsoft 365 Germany region. In Veeam Backup for Microsoft 365 v8, you can add organizations located in the Microsoft Entra Germany region only through REST API and PowerShell.
  • NAS SMB shares as backup targets.
  • Using multiple auxiliary backup applications for SharePoint processing.
  • On-premises Microsoft Exchange and Microsoft SharePoint organizations.

Known Issues, Considerations, and Limitations

The following is a list of considerations, limitations, and issues known to exist at the time of the Veeam Backup for Microsoft 365 v8.

Infrastructure and Configuration

Platforms and Applications

  • You can find system requirements and limitations for Microsoft 365 in the System requirements for Microsoft 365 and Office article.
  • Exchange Online throttling policies are set to hard limits and cannot be changed by a tenant Microsoft 365 organization. If you need to modify these settings, please contact Microsoft technical support.
  • Microsoft Outlook update channels such as Beta Channel, Current Channel, or Monthly Enterprise Channel are not supported. Veeam supports only RTM/GA versions of Microsoft Outlook. For more information, see this Microsoft article.
  • Automatic firewall rules creation and port opening is not supported. If any of the required ports are closed, you should open them manually.
  • IPv6 connections to Microsoft 365 endpoints are not supported. For more information, see this Microsoft article.

Microsoft 365 Organizations

  • Support for the Modern authentication that allows for using legacy auth protocols is deprecated.
  • Basic authentication method is only available for Microsoft 365 organizations in the Microsoft Entra China region. To add such organizations, use REST API and PowerShell.
  • Adding a Microsoft 365 organization in the China region may fail with one of the following errors:

    • “Connect to SharePoint: Unable to locate SharePoint Online. Identify Client Runtime Library (IDCRL) could not look up the realm information for a federated sign-in”.
    • “Check LegacyAuthProtocolsEnabled: Client Runtime Library (IDCRL) could not look up the realm information for a federated sign-in”.
  • Connection to a Microsoft 365 SharePoint Online organization in the China region may fail with the error: “Unable to locate SharePoint Online. Identity Client Runtime Library (IDCRL) could not look up the realm information for a federated sign-in. To resolve this error, try to re-connect in 30 minutes”.
  • Email notifications using OAuth 2.0 Authorization Framework are not supported for organizations in the Microsoft 365 China region.
  • Microsoft 365 organizations located in the Germany region can be added only through REST API and PowerShell.
  • Modern app-only authentication is not supported for the Microsoft 365 Germany region.
  • Microsoft Teams service is not supported for organizations in the Microsoft 365 China and Germany regions.
  • Email notifications on job results may not work properly for Microsoft 365 China and Germany regions. For more information, see KB2692.
  • Some of the Microsoft 365 SharePoint service plans assigned to the Microsoft 365 organization cannot be automatically identified as valid by Veeam Backup for Microsoft 365. For such organizations, OneDrive accounts cannot be backed up. Please contact Veeam Support to resolve this issue.
  • Connections using TLS 1.3 are not supported.

Veeam Backup for Microsoft 365 Components

  • If any of the machines hosting any of Veeam Backup for Microsoft 365 components were renamed or its FQDN was changed or it was joined to a different domain, the components would become unable to access each other. If these changes occur on a machine hosting a backup proxy, such proxy will have the Offline status displayed in the Veeam Backup for Microsoft 365 Console. To workaround, in the Console, remove this proxy from the infrastructure configuration, then configure this proxy anew, targeting the machine with its new name. Associated repositories will be preserved.
  • Installing Veeam Backup for Microsoft 365 and its components on a machine hosting a remote Veeam Backup for Microsoft 365 backup proxy is not supported.
  • Installing the Veeam Backup for Microsoft 365 REST API Service on a host machine running the Veeam Backup for Microsoft 365 Service is not supported.
  • On the host where Veeam Backup for Microsoft 365 is installed, internet proxy settings configured in Veeam Backup for Microsoft 365 are not reverted back after selecting the “Do not use internet proxy” setting.
  • Logs export using the Support Information wizard is not supported for REST services installed remotely. To collect logs manually, navigate to the %ProgramData%\Veeam\Backup365\Logs directory on the host running the REST service.
  • Logs exported using the Support Information wizard cannot be opened using File Explorer for Microsoft Windows if they include a backup job with a name of more than 260 characters. To view such logs, use other 3rd party tools, such as 7zip or WinRAR.
  • Installing Veeam Backup for Microsoft 365 and Veeam Explorers on Windows 11 22H2 with the enabled Smart App Control feature is not supported.
  • Certificates from the Trusted Root Certification Authorities store are not displayed and cannot be used for configuring tenant authentication and restore operator authentication.
  • The organization cache in PostgreSQL is updated once every 24 hours. Consider the following:

    • New objects created in Microsoft 365 organizations may not be yet present in the cache until the next synchronization is performed. To manually initiate organization cache synchronization, you can use either PowerShell or REST APIs.
    • Newly created SharePoint sites may not be synchronized to the cache for up to 20 minutes after their creation, because of the time required to synchronize changes across Microsoft 365.
  • On Linux backup proxies, unattended upgrades of .NET can impact proxy availability. To prevent unattended upgrades:

    • On Ubuntu hosts, .NET (dotnet-) must be added to the blacklist.
    • On Red Hat hosts, .NET (dotnet-*) must be added to the excludepkgs list.
  • Installing a PostgreSQL instance using the default Domain Administrator account is not supported.
  • Connection to a Veeam Backup for Microsoft 365 configuration database using local authentication credentials from a Veeam Backup for Microsoft 365 server running on another host fails with the warning: “Failed to decrypt data”.
  • System date and time in the UTC format must be the same on all machines with the Veeam Backup for Microsoft 365 components installed, including the PostgreSQL instance and the NATS server.

Backup Repositories

  • A symbolic link set as a mapped drive is not supported as a repository target.
  • A JET-based repository initially associated with a certain backup proxy can only be used by a proxy running the same Windows OS version or later. If you try to associate such a repository with a backup proxy running an earlier Windows version (for example, after downgrading the proxy server OS due to maintenance reasons), Veeam Backup for Microsoft 365 will not be able to access the repository data. The following error message will be issued: “JetError -514, JET_errBadLogVersion, Version of log file is not compatible with Jet version”. The reason is that the JET engine (ESE) differs for different versions of Windows OS. To be able to work with the data backed up by a proxy before such maintenance, make sure that the proxy has the same OS version before and after maintenance.
  • SMB shares on workgroup backup proxies are not supported as target repositories.
  • The $root and $log containers in Azure Blob Storage are not supported.
  • For Azure Blob Storage, only Azure Block Blob storage accounts are supported. For more information about the types of storage accounts in Azure, see this Microsoft article.
  • Microsoft Azure Blob Storage with a hierarchical namespace is not supported.
  • Governance mode is not supported for immutable IBM Cloud Object Storage and Object First repositories.
  • The immutability period on objects is automatically set up longer than the configured by the user. For backups, objects are locked for 10 days longer, and for backup copies, objects are locked for 30 days longer than the specified immutability period.
  • Azure Blob Storage Archive accounts configured for Read-access geo-zone-redundant storage (RA-GZRS) replication are not supported. For more information, see this Microsoft article.
  • The default 443 port is not supported for creating an archiver appliance in the AWS China region.
  • Amazon buckets with a period (‘.’) character in their names are not supported. For more information, see KB3095.
  • IPv6 connections to object storage are not supported.
  • The Versioning feature is only supported for Amazon S3 buckets, S3 Compatible buckets, and Microsoft Azure storage accounts that are used for immutable backup repositories.
  • Azure Archive Storage located in China East, China North, and China North 3 regions is not supported for creating backup repositories. For more information, see this Microsoft article.
  • Azure Blob Storage Germany region support is deprecated.
  • The Object Storage node is removed from the Backup Infrastructure view. After the upgrade to v8, existing backup repositories extended with object storage are displayed under the Backup Repositories node. If any object storage was configured but not added as an extension to a backup repository, you can finalize its configuration as a ready-to-use object storage repository using REST APIs or PowerShell after the upgrade to v8.
  • If you delete a remote backup proxy, backup repositories working with this proxy are removed from the Veeam Backup for Microsoft 365 scope. If you want to add such backup repositories back, you need to do it manually.
  • Connection to Azure Blob Storage, Amazon S3, and IBM Cloud Storage using TLS 1.3 is not supported.
  • Empty restore points created in Veeam Backup for Microsoft 365 v5 and earlier remain in a repository after all objects from such restore point have been deleted or moved to another location.

Upgrade

  • Upgrade from beta and technical preview versions of Veeam Backup for Microsoft 365 v8 is not supported.
  • Product updates cannot be installed automatically on the following components:

    • Remote REST services
    • Remote Veeam Explorers
  • After installing updates automatically and restarting a backup server, a new access token for REST clients cannot be received using a refresh token, and all REST clients need to re-authenticate with user credentials.
  • If a successfully installed automatic update has been rolled back by a user, automatic updates for remote Veeam Backup for Microsoft 365 Console and PowerShell components are not initiated.
  • Remote workgroup backup proxy upgrade fails if the upgrade installation is performed under a non-domain user account. To upgrade such a proxy, provide a remote proxy host administrator account credentials.
  • An automatic upgrade to v8 using the Upgrade wizard is not available. The ‘Your system is up to date’ status is displayed for installations running version 7a with the latest patch (P20240418).
  • Automatic silent updates are not supported for Linux backup proxy servers. After a silent update is installed such proxies are displayed with the Out-of-date status. You need to update them manually.
  • Upgrade of an immutable repository to v8 may fail with an error if such a repository contains backup data that has been mistakenly transferred using the Move-VBOEntityData PowerShell cmdlet and is incompatible with the immutability settings. For more details, see KB4644.
  • A previously installed Veeam license file is not automatically detected and installed during the upgrade. You need to manually install the license after you upgrade Veeam Backup for Microsoft 365 to version 8.
  • To ensure backup consistency, a full backup of messages from private and shared Teams channels will be performed after you upgrade to Veeam Backup for Microsoft 365 v8. This may result in a one-time increase in costs for using the Teams Exports APIs. The full backup is necessary because your backup repositories may already contain some of the messages, but the date when Microsoft APIs began returning messages from private and shared channels is unknown and may vary across different channels, teams, and organizations.

Backup

General

  • The following limitations apply to the backup of Microsoft 365 tenants using modern app-only authentication:

    • Dynamic distribution groups cannot be protected and cannot be used as a selection mechanism.
    • Resource/equipment mailboxes are presented and available for backup with the general User type.
    • SharePoint web parts can only be backed up if their ‘exportmode’ property is enabled. Non-exportable web parts are not supported.

    For more information, see KB3146.

  • Backup operations using an internet proxy with SSL filtering may fail with the error: “Exception of type ‘System.OutOfMemoryException’”.
  • Microsoft 365 group owner data backup is not supported if the group owner is not a member of the Group.
  • Backup jobs using auxiliary backup accounts newly created in Microsoft 365 and added to a security group may fail with the “Unauthorized (401)” error because of the time required to synchronize changes across Microsoft Entra and Microsoft 365.
  • In organizations with modern app-only authentication, the Type property for discovery search, resource, and equipment mailboxes is not resolved. Such mailboxes are available for backup with the general User type.
  • In hybrid organizations using modern app-only authentication, shared and public folder mailboxes are available for backup with the general User type if this user type is set for such users in the on-premises Microsoft Exchange organization.
  • In older restore points of organizations using modern app-only authentication, the user type property value is changed from User to Shared Mailbox after such a mailbox has been resolved and backed up as a ‘Shared Mailbox’ with Veeam Backup for Microsoft 365 build 7.0.0.4388 (patch P20231015) or later.
  • In the already existing backup jobs, the type for shared mailboxes is not automatically updated after the product is upgraded to Veeam Backup for Microsoft 365 build 7.0.0.4388 (patch P20231015) or later.
  • In a session action log, action timestamps are displayed in the timezone of a backup proxy server that executed the action.
  • Backup of on-premises Microsoft Exchange and Microsoft SharePoint organizations, as well as hybrid organizations, is not supported on Linux backup proxies. Processing of on-premises organizations requires the usage of WS-Management (WSMan) Remoting in PowerShell which is not supported on non-Windows platforms. For more information, see this Microsoft article.

Exchange Data

  • To back up public folder mailboxes, the Veeam service account must have a valid Exchange Online license and an active mailbox within the Microsoft 365 organization.
  • When creating public folder backups, you can select only the primary hierarchy mailbox for the backup.
  • If you modify the retention policy tag for a folder in Exchange Server, Veeam Backup for Microsoft 365 will perform full synchronization of that folder during the next job run. The reason is that any change to the retention policy makes changes to all items in the folder (modifies tag, updates last modification time). Such changes are treated by the synchronization mechanism as the new item version, which, in turn, automatically initiates full sync. For more information, see this Microsoft article.
  • Permissions for sharing mailbox folders and Calendar are not supported for backup.
  • Grouping of lists with To Do tasks is ignored during backup.
  • The ‘TeamsMessagesData’ folder is not supported for backup.

SharePoint and OneDrive Data

  • Selecting group objects is not supported for on-premises Microsoft SharePoint organizations.
  • To back up and restore SharePoint sites with certain specific templates, such as Business Intelligence Center, Product Catalog, and Visio Process Repository, an organization must have a valid SharePoint license.
  • SharePoint Online personal site and OneDrive account backup will fail if the site has reached its storage space quota and if your service account is not granted with the Site Collection Administrator permissions for this site.
  • A backup of a SharePoint site created within the last 24 hours before the backup job run may be performed with an error because of the time required for its configuration update.
  • Due to API limitations, version history backup is not supported for the Microsoft SharePoint .aspx web pages.
  • Backup of the SharePoint App Store applications added to a site is not supported.
  • Backup of the SharePoint App Store applications that use JavaScript redirects is not supported.
  • When an existing SharePoint Online backup job is reconfigured to work with a different repository, the Change API mechanism cannot be supported on the next job run. A full synchronization will be performed, but only changed data will be transferred during this session.
  • Resolving site collections fails for on-premises SharePoint organizations added to the Veeam Backup for Microsoft 365 scope using their fully qualified domain name (FQDN).
  • On-premises OneDrive backup fails with the error: “OneDrive was not found”, if the corresponding root site collection is missing.
  • Backup of the publishing pages web parts is not supported for on-premises Microsoft SharePoint organizations older than SharePoint Server 2016 security update KB 4018381.
  • For organizations added using modern app-only authentication, enabling the ability to change web parts export mode for an organization after the first SharePoint backup job run does not take effect on incremental runs if no changes have occurred to the source data after the initial backup job run. As a workaround, use the Start-VBOJob cmdlet with the -Full parameter to enforce the full backup run and apply the exportable mode to site web parts.
  • For organizations added using modern app-only authentication, SharePoint web parts export mode can only be changed automatically if such type of a property is supported and can be modified in the source SharePoint Online site or OneDrive account.
  • Comments on SharePoint list items are not supported for backup.
  • In organizations with the renamed SharePoint domain, sites explicitly selected for backup need to be re-added to a backup job.
  • If a SharePoint item has several versions with identical owshiddenversion values, only the latest version of this item is backed up, all the rest versions are skipped from processing.
  • The write rate may occasionally decrease during SharePoint backup to a repository extended with object storage.
  • In the New Backup Job wizard, search within sites works only by URL while sites are being enumerated.
  • After a SharePoint site URL has been changed, a site with an old URL can still be selected for backup. Processing of a site with an old URL will fail with the warning: Site was moved to another URL. As a workaround, to suppress the unwanted warnings, you can exclude these unneeded sites from a backup job.
  • Backup of personal SharePoint sites that use the SPSPERS#1–SPSPERS#10 templates and are not associated with any user fails with the warning: “Cannot resolve personal site owner. The user may not have a valid Microsoft Office 365 license with SharePoint plan enabled”.
  • Backup of a SharePoint team site that has the information barriers mode set to Implicit fails with error: “Exception from HRESULT: 0x87FA0080”.
  • Items count in a backed-up OneDrive folder is not updated on incremental backup job runs. When exploring OneDrive backups, you will see the item count as it was at the time of the first full backup run.
  • Backup of a personal view of a SharePoint list is not supported.
  • Managed Metadata columns are not supported for restore.
  • Managed Metadata columns are displayed incorrectly after restoring SharePoint list items.
  • OneDrive folders that have been excluded from processing via PowerShell will remain permanently excluded from all future incremental runs of a backup job. If you remove such a OneDrive from a job and later re-add it, the folders that were previously excluded will not be backed up.
  • SharePoint sites created by the Microsoft Loop app are not supported and are skipped from processing by default.

Microsoft Teams Data

  • Wiki tabs are not supported for backup when protecting Microsoft Teams objects.
  • Microsoft Teams applications from Microsoft AppSource Marketplace and custom applications from the organization’s app store are not supported for backup.
  • Microsoft Teams calls, meeting notes, and meeting chats are not supported for backup.
  • Code snippets in Microsoft Teams posts are not supported for backup.
  • Microsoft Teams tags are not supported for backup.
  • The ‘Allow members to upload custom apps’ team property in Microsoft Teams is not supported for backup.
  • Instant meetings (Meet Now) and scheduled meeting cards in Microsoft Teams posts are not supported for backup.
  • Team channel settings are not supported for backup.
  • In Multi-Geo organizations, backup of a team with a preferred data location set to a region different from the initial region may fail with the error: “(502) Bad Gateway”.
  • Backup of team chats using Teams Export APIs is not supported for Microsoft 365 organizations in the China, Germany, and US Government regions.
  • Backup of team chats using Teams Export APIs requires access to Microsoft Graph Teams Export APIs. For more information, see KB4322.
  • After October 1st, 2022, backup jobs processing Teams objects may fail with the error: “Folder TeamsMessagesData was skipped from processing. For more details, see KB4340”.
  • In organizations using the protected Teams Export APIs, team posts are not protected by default if a backup job includes the entire organization.
  • Team tabs linked to files stored in personal OneDrive accounts are not supported for backup.
  • Backup of a team linked to a SharePoint site that has the information barriers mode set to Implicit fails with error: “Exception from HRESULT: 0x87FA0080”.
  • The latest version of a Teams channel message with an attachment may not be returned by the Microsoft Graph Teams Export APIs, and consequently, such a message may be missing from a backup. This behavior is due to the current limitations of the Microsoft Graph Teams Export APIs.
  • Older channel messages created or modified in 2020 or earlier might not be returned by Team Export APIs and hence could be missing in a backup.

Backup Copy and Data Retrieval

  • For archive tier repositories configured with Item-level retention, an increase in retention period does not result in copying older restore points to this repository on the next backup copy job run.
  • Under certain conditions, data retrieved for either a team or its corresponding site might be available for browsing with both Veeam Explorer for Microsoft SharePoint and Veeam Explorer for Microsoft Teams.
  • Copying backups to an Amazon S3 Glacier or Glacier Deep Archive object storage may take up to 3x more time compared to copying backups to an Azure Blob Storage Archive.
  • Under certain conditions, exporting retrieved Teams posts for a selected time period may fail.
  • The availability period for retrieved data cannot be reduced if an archive tier repository with an already requested data retrieval has been removed and then re-added to Veeam Backup for Microsoft 365.
  • The number of items transferred by a copy job targeted at a repository with Item-level retention may mismatch the number of items transferred by a corresponding backup job.
  • Active data retrievals are not displayed in the Veeam Backup for Microsoft 365 Console if the corresponding archive tier repository has been re-attached to a different proxy after the retrieval process had been initiated.
  • In the job statistics, the amount of data transferred by a backup job and its corresponding backup copy job may not match. This discrepancy is caused by differences in the data layout between the backup and backup copy jobs.

Restore Portal

  • A Microsoft Entra application used for Restore Portal cannot be created automatically on a host where only the Veeam Backup for Microsoft 365 remote REST service is installed.
  • On the Restore List tab, an item’s restore status may be displayed incorrectly if multiple items of the same data type (Exchange, SharePoint or OneDrive) have been restored simultaneously and some of the items failed to be restored or restored with warnings. Restore Status is displayed according to the entire restore session result.
  • A Microsoft Entra application used for Restore Portal cannot be automatically configured for multiple organizations added to the Veeam Backup for Microsoft 365 scope. To make Restore Portal work in a multitenant environment, you need to configure your Microsoft Entra application manually.
  • Restore sessions are not closed automatically and keep running for an hour after a user who logs in to the Restore Portal refreshes their browser during the current login attempt.
  • A user or a restore operator cannot perform a restore via Restore Portal if the corresponding organization has been removed from the Veeam Backup for Microsoft 365 scope during this Restore Portal session.
  • On the Restore List tab, sorting items in the list by Restore Status is not supported.
  • Searching by part of a word is not supported. Only word prefix search is supported.
  • Restore points created by Veeam Backup for Microsoft 365 of a version earlier than 6.0 (build 6.0.0.367) are not available for selection in Restore Portal.
  • Restore of Teams system event messages is not supported. For more details, see KB4513.

Veeam Explorers

  • Sending in attachments backed-up items bigger than 25 MB is displayed as successful, while the email is not sent. This issue only applies to sending emails on behalf of your Google Gmail account. For more information, see this Google article.

Veeam Explorer for Microsoft Exchange

  • If you want to restore In-Place Hold Items or Litigation Hold Items to the original location (that is, original mailbox system folders), consider the following limitations:

    • Restore of In-Place Hold Items is not supported for on-premises Exchange Server 2013 due to EWS limitations.
    • To restore In-Place Hold Items of Exchange 2016 mailboxes, these mailboxes must have In-Place Hold enabled and applied at least once with the DiscoveryHolds system folder creation. Otherwise, restore of In-Place Hold Items will fail with an error: “Failed to restore In-Place Hold Items. Restore of In-Place Hold Items into Exchange 2013 is not supported”. For information on enabling In-Place Hold and Litigation Hold, see this Microsoft article.
    • Browsing and restoring items from the Versions subfolder of the Recoverable Items folder used by In-Place Hold and Litigation Hold to preserve items is not supported.
  • 1-Click Restore is not supported for the following scenarios:

    • Restore of an Exchange Online archive mailbox to an on-premises Exchange archive mailbox.
    • Restore of an Exchange Online mailbox to an on-premises Exchange mailbox.
  • For users migrated from Microsoft 365 to on-premises Exchange, mailbox restore to the original location is supported via the restore wizard only until a new backup is performed after the migration.
  • Search results for queries built with the ‘is not’ and ‘doesn’t contain’ criteria will not include emails where the corresponding fields are empty.
  • Restore of the Team Chat and TeamsMessagesData folders is not supported.
  • Restore of group mailboxes and comparing them to production using a username and an app password for authentication is not supported.
  • Bulk restore (restore of multiple objects) using modern authentication with the Microsoft Entra application certificate is not supported for public folder mailboxes. Use the regular per-object restore instead.

Veeam Explorer for Microsoft SharePoint

  • The following limitations apply for restoring data with modern app-only authentication (for more information, see KB3146):

    • OneNote restore is not supported.
    • The SharePoint web part customized template cannot be preserved upon a restore. All web parts will be restored with the default template.
    • The Allow multiple responses setting in survey lists within team modern sites is not preserved upon a restore.
  • Restoring a SharePoint team site does not preserve the team site owner, nor are Microsoft 365 Group members restored.
  • SharePoint root site node restore is not supported if only subsites of this root are included in a backup. The node is displayed and accessible for restore in the UI, but the restore will finish with a new web part created and a warning that no master page is available for this web part.
  • SharePoint App Store applications restore is not supported.
  • Restore to on-premises SharePoint sites that are enabled for mixed ‘Windows Authentication’ and ‘Forms Authentication’ fails with the “The remote server returned an error: “(403) Forbidden”.
  • If a personal SharePoint Online site was enabled for Multi-Geo after it had been backed up, it can only be restored to the location that was current at the time of backup. Restore to a new location after a site has been moved to a new geo is not supported. For more information, see KB3098.
  • SharePoint Team site restore to a new alias or to another location is not supported for the STS#0 and STS#3 site templates.
  • SharePoint site custom RSS settings are not preserved upon site restore. RSS settings are restored with the default configuration.
  • Restore of custom apps added to a SharePoint site from the organization’s App Catalog is not supported.
  • SharePoint site group settings are not preserved upon site restore. Group settings are restored with the default configuration.
  • Custom SharePoint site templates are not preserved upon site restore.
  • Information Rights Management (IRM) settings for SharePoint lists and libraries are not preserved upon restore.
  • A personal site is restored with errors if the ‘Add And Customize Pages’ permission for the user is set to ‘Deny’. For more information, see this Microsoft article.
  • Hidden lists are not supported for restore.
  • Shortcuts to shared folders are not supported for restore.
  • Restore from SharePoint Online to SharePoint Subscription Edition is not supported for sites using the SITEPAGEPUBLISHING#0 and GROUP#0 templates.
  • Restore of personal sites to an organization where the Custom Scripts option is disabled for personal sites is not supported.
  • Team sites restore to a Multi-Geo organization using Basic authentication is not supported.
  • Restore of a personal site to another location is not supported if this user account does not exist in the target organization.
  • SharePoint site restore from SharePoint Online to SharePoint 2016 is not supported.
  • A SharePoint item with minor versions is restored with major versions if the target library or list is set for major versions only.
  • SharePoint item might be incompletely restored to another location, if this item has references to other items in its original location.
  • Restore of a subsite to another organization fails if this subsite uses a template is does not exist in the target organization.
  • Site collection features may not be preserved upon a site restore to another organization. After restore, such features can be activated for a subsite manually in Microsoft 365.
  • The approval status of SharePoint items of the Document Set type is restored to Pending if an item is restored to another location.
  • Restore of shortcuts to shared folders is not supported.
  • In a site ULR, a SharePoint domain is changed to a target organization after the site restore to another location.
  • Field value in a list column changes to the default after restore, if the field value has not been specified.
  • Item size is displayed as zero bytes if this item was being uploaded to SharePoint during backup.
  • Empty root nodes of SharePoint sites that are out of retention are displayed in Veeam Explorer.
  • On the Restore List tab, an item’s restore status may be displayed incorrectly if multiple items of the same data type (Exchange, SharePoint or OneDrive) have been restored simultaneously and some of the items failed to be restored or restored with warnings. Restore Status is displayed according to the entire restore session result.
  • OneNote notebooks that you save locally as files are opened in a read-only state. For more information, see KB4402.
  • Connections using TLS 1.3 are not supported.
  • Restore of a folder named Folder and the items within it to a new location fails with the warning: “A file or folder with the name %URL% already exsists”.
  • Restoring custom columns for folders and document sets to on-premises Microsoft SharePoint is not supported.
  • Restoring SharePoint sites created for Teams’ private and shared channels fails with the error: “Web template not found: TEAMCHANNEL#1” if these sites are restored to a different location or to their original location where the parent site no longer exists.

Veeam Explorer for Microsoft OneDrive for Business

  • Restoring Shortcuts to shared folders is not supported.
  • Item size is displayed as zero bytes if this item was being uploaded to OneDrive during backup.
  • Empty root nodes of OneDrive accounts that are out of retention are displayed in Veeam Explorer.
  • OneNote notebooks that you saved locally as files are opened in a read-only state. For more information, see KB4402.
  • If the size of a OneNote notebook is greater than 2 GB, this OneNote notebook is saved as a folder with OneNote items.

Veeam Explorer for Microsoft Teams

  • Teams restore is not supported in the modern authentication mode with legacy protocols allowed (using a username and an app password). To restore Teams data, use modern app-only or basic authentication.
  • OneNote files restore is not supported in the modern app-only authentication mode.
  • Teams group settings are restored as default when using the modern app-only authentication mode.
  • In the restore wizard, team guest members are shown as regular members. For restore, guest membership status is preserved.
  • Membership permissions cannot be downgraded during the entire team restore if the team exists in an organization. For example, the ‘Owner’ role in the production Teams environment cannot be overwritten with the ‘Member’ role.
  • Some channels may be skipped during the restore if the total number of restored channels plus the existing channels (including deleted) in the target team exceeds 200. For more information, see this Microsoft article.
  • An entire team restore fails with the error “The directory object quota limit for the Tenant has been exceeded”, if the number of teams (including archived teams) in this Microsoft 365 organization exceeds 500,000. For more information, see this Microsoft article.
  • For a team with 100 owners, backup and restore fails with the error: “Unable to perform operation as '101' would exceed the maximum quota count '100' for forward-link 'owners”. For more information, see this Microsoft article.
  • Headlines of announcement posts are not shown in the Posts view of Veeam Explorer for Microsoft Teams. Subheadings of announcement posts are shown in the Subject field.
  • Restore of a tab with more than 127 characters in its name fails with the error: “DisplayName is too long”.
  • Restore of a team with more than 127 characters in its name fails with the error: “Resource provisioning is in progress. Please try again.”.
  • Teams objects restore fails if the team site cannot be accessed.
  • Long channel names are cut to 31 characters after restoring to include the restore timestamp and fit the maximum of 50 allowed characters.
  • Restoring a team within less than 10 minutes from its deletion may fail with the error: “Failed to restore Team: The object id "%value%" is invalid”.
  • If a user never opened the Files tab of a team channel in Microsoft Teams before data backup, files from this tab are not displayed in Veeam Explorer for Microsoft Teams.
  • In organizations using modern app-only authentication, during backup and restore of an archived team, Veeam Backup for Microsoft 365 does not preserve the Make the SharePoint site read-only for team members property of the team on the Microsoft 365 side.
  • Team posts restore fails with the error: “App id com.microsoft.teamspace.tab.web needs to be installed to the scope … and be in an unblocked state to install/update a tab”, if the WebSite Teams App has been manually blocked via Teams Admin Center.
  • Teams posts may duplicate when browsing an organization’s backup if the same team has been processed on both a proxy using Teams Export APIs and on a proxy that uses EWS APIs for team chats backup.
  • Team posts may duplicate when browsing a standalone backup database that includes Team chats data backed up via both the EWS APIs and Teams Export APIs.
  • Team posts are displayed as deleted and with empty content, if in the production environment a channel with these posts has been deleted and then restored natively via Microsoft Teams tools.
  • The timestamp of a scheduled meeting is displayed incorrectly in posts backed up via Teams Export APIs.
  • Restore of a deleted private Teams channel may fail with the error: “No active channel found with channel id: %ID%”. This issue is caused by the behavior of Microsoft Graph API and may occur if a tab is restored immediately after restoring the private channel.
  • The author name is displayed incorrectly for Teams channel messages with scheduled meetings. This issue is caused by the incorrect displayName parameter returned by Microsoft Graph APIs.
  • Restore of files belonging to Teams channels of different types is not supported.
  • Deleted Teams channel messages are displayed using the Show items that have been deleted by user option, but restore actions cannot be performed to these items.
  • A deleted Teams channel message is displayed twice when you explore a restore point with both the Show items that have been deleted by user and Show all versions of items that have been modified by user options selected.
  • When you restore a deleted team, a renamed General channel and its content are restored as a separate channel. A new default General channel is created during the team restoration and it remains empty.

PowerShell

  • PowerShell modules may not be imported automatically after installing Veeam Backup for Microsoft 365 on Windows Core OS. To workaround, restart CMD via Task Manager, or log off the operating system and log back on.
  • Moving SharePoint data from a local JET-based backup repository to object storage in an asynchronous mode using the Move-VBOEntityData cmdlet may fail with the error: “Cannot find web”. The error occurs on subsites if their corresponding root site has been moved first.
  • Team channel messages are skipped from processing when a full backup is enforced using the Start-VBOJob cmdlet with the -Full parameter and using Teams Export APIs is enabled.
  • The Move-VBOEntityData cmdlet allows performing an unsupported action to move backup data to an immutable object storage repository. For more details, see KB4644.
  • The Get-VBOEntityData cmdlet returns shared mailboxes with the ‘User’ account type. This issue applies to Microsoft 365 organizations with modern app-only authentication and restore points created by Veeam Backup for Microsoft 365 build 7.0.0.4388 (patch P20231015) or later.
  • .NET 4.7.2 cmdlets do not work when initiated via PowerShell 7.3.3 modules from Veeam Backup for Microsoft 365 v8. Use either pwsh.exe along with .NET 6 cmdlets, or powershell.exe along with .NET 4.7.2 cmdlets.
  • The IsTeamsGraphAPIBackupEnabled parameter returned by the Get-VBOProxy cmdlet is deprecated. Starting v8, Teams channel messages backup uses protected APIs by default ignoring previous modifications of proxy configuration related to using of these APIs.
  • A full backup of Teams channel messages is performed after moving a team with private and shared channels between JET-based repositories using the Move-VBOEntityData cmdlet. This issue may result in additional costs of using Teams Export APIs.

REST API

  • The frequency of requests to obtain access and refresh tokens through the /token endpoint is limited to 1 per second, 5 per minute, and 1500 per hour. These limits do not apply to requests made from localhost.
  • The href links in responses do not include either the DNS name or IP address of the Veeam Backup for Microsoft 365 server or the port number.
  • All href links in responses have the /v8/<Resource-URL> syntax.
  • The ManagedBy parameter of a distribution group is not displayed in the response to the (GET) /v8/Organizations/{organizationId}/Groups request. For more details, see this Microsoft article.
  • The /v8/RestorePoints endpoints do not return any protected data for restore points created by Veeam Backup for Microsoft 365 earlier than v6 (build 6.0.0.367).
  • The following requests return shared mailboxes with the ‘User’ account type:

    • (GET) /v8/BackupRepositories/{repositoryId}/UserData
    • (GET) /v8/protectedUsers

    This issue applies to Microsoft 365 organizations with modern app-only authentication and restore points created by Veeam Backup for Microsoft 365 build 7.0.0.4388 (patch P20231015) or later.

  • The (GET) v8/BackupRepositories/{Id}/OneDriveData request returns an outdated OneDrive URL if a username has been changed.
  • Audit email notifications are sent only when you perform operations on data belonging to the backed-up object. If notifications are configured for an associated object, they will not be sent. For example, if you configure audit notifications for a group associated with a team and perform actions on backed-up Teams data, notifications will not be sent.
  • The (POST) /v8/RestoreSessions/{restoreSessionId}/organization/teams/{teamId}/channels/{channelId}/restore request returns an incorrect error message: “Nullable object must have a value”, if some of the mandatory parameters, such as the restoreChangedItems and restoreMissingItems, are missing in the request body.
  • The (GET) /v8/RestoreSessions/{id}/Statistics request does not return any statistics if the requested restore session is currently running.
  • The following endpoints are deprecated in v8:

    • (GET) /RestorePoints/{restorePointId}/protectedMailboxes
    • (GET) /RestorePoints/{restorePointId}/protectedOnedrives
    • (GET) /RestorePoints/{restorePointId}/protectedTeams
    • (GET) /RestorePoints/{restorePointId}/protectedSites
    • (GET) /RestorePoints/{restorePointId}/protectedUsers
    • (GET) /RestorePoints/{restorePointId}/protectedGroups

    To get information on protected mailboxes and OneDrives, use the following endpoints instead:

    • (GET) /v8/ProtectedUsers
    • (GET) /v8/ProtectedUsers/{protectedUserId}
    • (GET) /v8/ProtectedGroups
    • (GET) /v8/ProtectedGroups/{protectedGroupId}
    • (GET) /v8/ProtectedSites
    • (GET) /v8/ProtectedSites/{protectedSiteId}
    • (GET) /v8/ProtectedTeams
    • (GET) /v8/ProtectedTeams/{protectedTeamId}
  • The following endpoints are deprecated in v8:

    • (GET) /JobSessions/Changes
    • (GET) /RestorePoints/Changes

    To get information on changes that appeared in job sessions and restore points, use the following endpoint instead:

    • (GET) /v8/Events
  • The (GET) /v8/Events endpoint does not return the following job statuses for the JobSessionUpdate event:

    • None
    • Disconnected
    • Queued
    • Updating
  • For each restore operation initiated using REST APIs, a separate restore session is created. For example, separate restore sessions are created for browsing backed-up data and for data restoration.
  • Partial match is not supported to query objects that the server will return in response.
  • The (GET) /v8/licensing/statistic/usage does not include backed-up users with a ‘TemporaryAssigned’ licensed status. Users with the ‘TemporaryAssigned’ status are considered licensed and must be included in the licensing count. To get the correct current licensed users count, use the following methods:

    • The (GET) /v8/License request
    • The (GET) /v8/LicensedUsers request
    • The Get-VBOLicense PowerShell cmdlet
    • The Get-VBOLicensedUser PowerShell cmdlet
    • The License information window in the product UI
    • The Licenses used count in the product UI

Reporting

  • The Mailbox Protection report generated for the root Organizations node will fail if any issues occur when connecting to one of the organizations in the scope.
  • When Veeam Backup for Microsoft 365 is installed on a machine running Microsoft Windows Server core editions, creating of the Mailbox Protection report will fail with the error: “Could not find file.” For more information, see this Microsoft article.
  • In the generated reports, the product name may be displayed as outdated (Veeam Backup for Microsoft Office 365) if a license file installed on the Veeam Backup for Microsoft 365 server contains the outdated product name.
  • Timestamps in the generated reports are provided in the following format: MM/dd/yyyy HH:mm:ss and may not respect the local machine Date and Time format settings.

Installing Veeam Backup for Microsoft 365

Before You Install

If you have participated in the public technical preview testing program for Veeam Backup for Microsoft 365 v8, before running the setup be sure to:

  1. Remove all remote backup proxies.
  2. Uninstall the pre-release versions of Veeam Backup for Microsoft 365, Veeam Explorer for Microsoft Exchange, Veeam Explorer for Microsoft SharePoint, and Veeam Explorer for Microsoft Teams.
  3. Manually remove the following:

    • The default VeeamRepository folder.
    • The target folders in object storage: <bucket_name/container_name>/Veeam/Backup365/.
    • PostgreSQL configuration databases created for the pre-release version of Veeam Backup for Microsoft 365.
    • NATS streams created by Veeam Backup for Microsoft 365. By default, streams are located in the C:\Users\Administrator\AppData\Local\Temp\2\nats\jetstream\$G directory.

    Note, that v8 is incompatible with pre-release backup repositories, object storage, and configuration databases.

  4. Manually delete the content of the C:\ProgramData\Veeam\Backup365 directory.

Installation

To install Veeam Backup for Microsoft 365, do the following:

  1. Download the latest ISO version which has the latest available cumulative patch built in.
  2. Mount the ISO image and run the Veeam.Setup.exe file.
  3. Select which component(s) you want to install. The following components can be installed on the same or different servers: Veeam Backup for Microsoft 365 server, user interface Console, PowerShell extension module, and the REST API plugin.
  4. Read and accept the terms of the license agreement.
  5. Provide a license file.
  6. Review the information from the System configuration check for any potential installation problems.
  7. Change the default installation directory if needed.
  8. Select a PostgreSQL database instance for Veeam Backup for Microsoft 365 configuration data.
  9. Select a NATS server instance.
  10. Review your installation settings and click Install to begin the installation.

Consider the following:

  • If you want to use a PostgreSQL instance other than version 15.8 included in the Veeam Backup for Microsoft 365 setup, you must install it yourself.
  • If you want to use an already installed PostgreSQL instance, ensure that the instance contains the default postgres database.
  • If you install a new PostgreSQL instance using the Veeam Backup for Microsoft 365 installation wizard, the postgres database is created on the instance automatically.
  • Do not rename the postgres database after the installation. Veeam Backup for Microsoft 365 connects to the postgres database to access the configuration database.

Uninstalling Veeam Backup for Microsoft 365

To uninstall Veeam Backup for Microsoft 365, do the following:

  1. Stop and disable all backup jobs.
  2. Close all restore sessions in Veeam Explorer for Microsoft Exchange, Veeam Explorer for Microsoft SharePoint, Veeam Explorer for Microsoft OneDrive for Business, and Veeam Explorer for Microsoft Teams.
  3. Open Veeam Backup for Microsoft 365, go to Backup Infrastructure > Backup Proxies and remove all remote backup proxies.
  4. Open Control Panel > Programs and Features.
  5. In the programs list, right-click Veeam Backup for Microsoft 365, and select Uninstall.
  6. At the Uninstall step, select check boxes next to the items that you want to uninstall and click Remove. Mind that the Veeam Backup for Microsoft 365 uninstallation wizard uninstalls Veeam Explorers that are included in the Veeam Backup for Microsoft 365 installation package if you have only Veeam Backup for Microsoft 365 on your machine.

Consider the following:

  • The installation package includes a new EXO V3 PowerShell Module component. The uninstallation wizard does not uninstall it automatically. If you want to remove it from your machine, you need to uninstall it manually.
  • The uninstallation wizard does not automatically uninstall the NATS server (the nats-server service) deployed along with Veeam Backup for Microsoft 365. If you want to remove it from your machine, you need to uninstall it manually.
  • Note that repository data in the target locations is not affected when Veeam Backup for Microsoft 365 is uninstalled.

Upgrading Veeam Backup for Microsoft 365

Veeam Backup for Microsoft 365 v8 supports upgrades from the following versions:

  • 7.0 (builds 7.0.0.2911 - 7.0.0.4901)
  • 7a (builds 7.1.0.1301 - 7.1.0.2031)

Before You Upgrade

Consider the following when planning for an upgrade to Veeam Backup for Microsoft 365 v8:

  • Backup job settings and global configuration options (including notifications, file exclusions, etc.) will be preserved after the upgrade.
  • All backup jobs, including those running on a schedule, will be stopped during the upgrade.
  • Ensure you have sufficient space on the disk where you locate your PostgreSQL database instance. Note that during the upgrade to v8 all the existing databases, including configuration SQLite and persistent cache databases from local and remote proxies, will be transferred to the centralized PostgreSQL database.
  • Install Microsoft .NET Runtime 8.0.7 or later and Windows PowerShell 7.4.2 or later on the hosts running remote backup proxies.
  • Important: Upgrade from the beta and technical preview versions of Veeam Backup for Microsoft 365 v8 is not supported.

Upgrade Window

During the upgrade to Veeam Backup for Microsoft 365 v8, all existing product databases, including configuration SQLite and persistent cache databases from local and remote proxies, will be transferred to the centralized PostgreSQL database.

To plan for the appropriate maintenance window, consider the following:

  • Upgrade to v8 is performed in two steps:

    • Upgrade of the Veeam Backup for Microsoft 365 server and Console. On average, a server with a 50 GB configuration database upgrades to v8 in up to 15 minutes.
    • Upgrading other existing product databases in the background. Upgrading a Veeam Backup for Microsoft 365 server with an average of 1 million sessions in its history typically requires up to 16 hours.
  • When your backup repositories are being upgraded, they are unavailable for use.

    • On average, an object storage repository containing 1 TB of backup data upgrades to v8 in up to 15 minutes. Parallel upgrade of over 1,500 object storage repositories on average requires up to 30 minutes.
    • On average, a JET-based repository upgrades to v8 within minutes.
  • Backup data from an upgraded repository is automatically indexed to the centralized database. Accessing backups from a repository that is currently being indexed may be limited. On average, indexing a repository with 10,000 restore points requires up to 5 minutes.

Upgrade

To upgrade Veeam Backup for Microsoft 365 to v8, do the following:

  1. Download the latest ISO version which has the latest available cumulative patch built in.
  2. Mount the ISO image and run the Veeam.Setup.exe file. Follow the wizard steps to install Veeam Backup for Microsoft 365.

After upgrading to v8, all backup repositories and backup proxies will be marked as Out of Date. You need to upgrade these components manually from the Veeam Backup for Microsoft 365 Console.

If you have the REST API component installed on a separate host, you must manually upgrade it on this machine after upgrading Veeam Backup for Microsoft 365 to v8. For more information, see the Upgrading REST API on Separate Machine section of the Veeam Backup for Microsoft 365 User Guide.

Licensing

Veeam Backup for Microsoft 365 is licensed per Microsoft 365 user across all organizations.

After you install Veeam Backup for Microsoft 365 and its components, you will have a Community Edition mode that allows you to process up to 10 user accounts in all organizations including 1 TB of Microsoft SharePoint data and up to 10 teams. Such mode suggests using the Community license, which is not limited in time, nor implies any limitations in terms of program functionality.

Monitoring Veeam Backup for Microsoft 365 infrastructure and data protection operations with Veeam ONE v12, requires a new Veeam Backup for Microsoft 365 license file with the M365Suite package value. To download the license file manually, go to my.veeam.com.

To install your paid, fully functional product license, do the following:

  1. Start the program and open the main menu (the upper left of the Console).
  2. In the main menu, click License.
  3. In the License Information window, click Install and specify the path to your license file.

For more information on licenses and how to retrieve them, see the FAQ. To renew your contract, please contact Veeam at: .

Technical Documentation References

If you have any questions about Veeam Backup for Microsoft 365, you may use the following resources:

To view the product help, press the F1 key or select Help and Support > Online help from the main menu.

Technical Support

We offer email and phone technical support for customers on maintenance and during the official evaluation period. For a better experience, please provide the following when contacting our technical support:

  • Version information for the product and all infrastructure components.
  • Error message and/or accurate description of the problem you are having.
  • Log files. To export the log files, select Help and Support > Support information from the main menu, and follow the wizard to export the relevant set of log files.

To submit your support ticket or obtain additional information please visit https://www.veeam.com/support.html.

TIP: Before contacting Veeam Customer Support, consider searching for a resolution on Veeam R&D forums at www.veeam.com/forums.

Contacting Veeam Software

At Veeam Software we pay close attention to the feedback from our customers. It is important to us not only to quickly help you with your technical support issues - we make it our mission to listen to your input, and to build our products with your suggestions in mind.

Should you have a Customer Support issue or question, please feel free to contact us. We have qualified technical and customer support staff available 24 hours a day, 7 days a week who will help you with any inquiry that you may have.

Customer Support

For the most up-to-date information about our support practices, business hours, and contact details, please visit https://www.veeam.com/support.html. You can also use this page to submit a support ticket and download the support policy guide.

Company Contacts

For the most up-to-date information about company contacts and office locations, please visit www.veeam.com/contacts.

Document updated 11/26/2024

Document content applies to build 8.0.5.20

View all results across Veeam
Back to document search