Release Information for Veeam Backup for Microsoft 365 8.5

New Features and Enhancements

• Added new PowerShell cmdlets to remediate data stored in object storage repositories that is affected by the issue described in KB4835. For more information, see KB4874.
• Additional Microsoft Graph permissions are required for the backup app registrations in Microsoft Entra ID to support Exchange mailbox protection after EWS retirement. For more information, see KB4820.
• Added support for Microsoft Exchange Server Subscription Edition.
• SharePoint site permissions and members are now preserved when restoring a site to another location within the same Microsoft 365 organization.
• Microsoft Teams channel messages are now referred to as "posts" instead of "chats", to better reflect Microsoft's own terminology. REST API and PowerShell parameter names are not affected.
• Improved SharePoint backup and object storage repository performance by extending asynchronous processing to list content retrieval and file cache operations.
• Improved Exchange backup performance for mailboxes with large numbers of emails in a single month.
• Reduced memory usage and improved backup job performance for repositories containing SharePoint data.
• Improved backup performance for SharePoint sites containing large numbers of items by optimizing internal database queries for large datasets, improving query completion time from minutes to milliseconds.
• Improved SharePoint backup job throughput.
• Optimized how object storage consumption metrics are updated during backup jobs and retention tasks, reducing PostgreSQL load for large repositories.
• Reduced Exchange backup job duration by up to 26% for large mailboxes by parallelizing sync and repository write operations.
• Optimized processing of backup job and restore session events to prevent uncontrolled growth of the NATS controller stream.

Bug Fixes

General

• The backup proxy service on a Linux machine may crash during an OS base system update.
• The Veeam Backup for Microsoft 365 upgrade stalls if services, including Veeam.Archiver.Shell and Veeam.Archiver.Proxy, do not terminate properly before starting.
• Backup or restore sessions get stuck in the Running state during Veeam Backup for Microsoft 365 upgrades when proxies are running different product versions simultaneously.
• In large-scale environments, retention tasks run longer than expected or fail intermittently.
• Re-adding an immutable object storage repository after deletion fails with an error stating the S3-compatible object storage already exists at the specified location.
• Organization cache synchronization intermittently fails on group members with errors such as:

  A web error occurred when invoking {path}. The response status code does not indicate success: 400 (Bad Request).
  

• Editing an organization to enable Teams chat protection fails with the error:

  New configuration must point to the same Exchange organization.
  

• The retention task fails on immutable S3-compatible repositories when all blob versions have unexpired locks with the error:

  Sequence contains no elements
  

• Duplicate geolocation entries are not detected after the organization configuration is loaded, resulting in unexpected behavior in multi-geo environments.

Backup and Backup Copy

• OneDrive backup copy jobs to an immutable repository fail with the error:

  The file content stream must be read to obtain: ContentOffset.
  

• A SharePoint backup job gets stuck in the Running state with no progress, reporting a large number of failed items with the error:

  An invalid file cache context was detected.
  

• Exchange backup jobs intermittently fail to download individual mailbox items, displaying the error:

  Failed to download some of the items.
  

• A SharePoint backup job stalls after this error occurs:

  The value must be greater or equal to {value}. (Parameter 'to')
  

• Backup jobs fail during the object resolve phase if processed objects have properties, such as display names or office locations, containing \0 characters.
• Backup copy job transfers restore points exceeding the retention period set on the target repository.
• Backup copy to an immutable repository fails with an error indicating the immutability period has not yet expired.
• Teams and SharePoint backup jobs fail with the error:

  Index was outside the bounds of the array.
  

• When the organization contains Microsoft Loop content storage sites that use the new URL format, the SharePoint backup job fails with the error:

  Attempted to perform an unauthorized operation.
  

• After a repository resync on immutable S3-compatible storage, the Exchange backup job fails with the error:

  Failed to apply immutability to object {path} because the object is already immutable
  

• Backup copy job intermittently fails with the error:

  Resolve failed: Cannot access a disposed object.
  

• SharePoint list entities that are deleted and recreated in production are not correctly re-added to the backup during incremental job runs.
• Exchange backup jobs run longer than expected when the Exchange Online REST API is temporarily unavailable.
• Backup jobs processing SharePoint and OneDrive data fail with the error:

  PostgreSQL database operation failed multiple times with transient error.
  

• A backup job fails with the error:

  Failed to resolve some objects.
  

Restore

• SharePoint item restore fails if the item contains a _CopySource property.
• Restoring a OneDrive to another OneDrive account with the same display name using the 'Copy To' option fails with the error:

  There are multiple OneDrive accounts with the specified username. Please select the account explicitly.
  

• Microsoft sensitivity labels applied to a SharePoint site or list are not preserved when the site or list is restored to a different location.
• The Restore Portal fails to open after upgrading from Veeam Backup for Microsoft 365 v7.
• The Advanced Find feature in Veeam Explorer for Microsoft Exchange may return incomplete or incorrect results.
• Restore sessions on JET-based repositories fail due to excessive organization verification.
• In organizations where the user has both a member account and a legacy guest/external account after a cross-tenant migration, restoring that user's OneDrive in Veeam Explorer for Microsoft OneDrive fails with the error:

  There are multiple OneDrive accounts with the specified username
  

• Performing an Exchange restore operation when the recipient list contains a skipped or unresolvable element fails with the error:

  An internal server error occurred
  

• After migrating backup data from a JET-based repository to object storage, mailbox restore points do not appear in the Restore Portal.
• Restore of a SharePoint site to another geo region within the same Microsoft 365 organization fails with the error:

  This parameter is incompatible with restoring to another location: RestorePermissions.
  

• Changing the scope in the Restore Portal fails with repeated PostgreSQL transient errors.

REST APIs

• The (GET) v8/backuprepositories/{id}/SiteData REST API endpoint responds slowly on larger repositories.
• Teams restores initiated via legacy v7 REST API fail with the error:

  Failed to get task result because the task does not exist.
  

• OneDrive restore using the 'Copy To' option initiated via REST API automatically cancels after processing for a period without completing.
• The REST API returns incorrectly formatted date/time values on servers configured with northern European system locales.
• The REST API returns an invalid endTime value for backup job sessions in progress, missing the UTC designator in the timestamp.
• For organizations configured to protect only the Exchange service, backup jobs configured via the REST API attempt to access SharePoint and fail with the error:

  HostNotFound
  

• The (GET) v8/RestoreSessions/{restoreSessionId}/Events endpoint returns an incorrect restore target for SharePoint and OneDrive restore sessions.
• The changedItems and deletedItems parameters are ignored when restoring a OneDrive to the same or a different location using the copyTo REST API endpoints.

PowerShell and Data Management

• Data move jobs fail with the error:

  Object reference not set to an instance of an object.
  

• Data move job fails with the error:

  Failed to move team posts: No JSON content found.
  

• When the organization has already been removed from the Veeam Backup for Microsoft 365 Console, deleting backups from a JET-based repository using the Remove-VBOEntityData cmdlet fails with one of the following errors:

  An item with the same key has already been added
  

  or

  Organization does not exist
  

• Data move jobs transferring Teams data fail with the error:

  Object reference not set to an instance of an object.
  

• Data move jobs fail with a duplicate key error:

  (error code -1605)
  

• The Get-VBOEntityData cmdlet fails with the error:

  An item with the same key has already been added.