Below are details about each of the Cumulative Patches that have been released for Veeam Backup for Microsoft 365 version 7 (7.0.x).

Each subsequent Cumulative Patch also includes all fixes present in the previous Cumulative Patches.

P20231218 (7.0.0.4551)

Resolved Issues

• Exchange backup fails with the following errors:

  There is an error in XML document
  

  and

  The specified type was not recognized: name='SharingMessage'
  

  For more information, review: KB4527

P20231015 (7.0.0.4388)

Resolved Issues

• In a backup job configured to process an entire organization, user and shared mailboxes are skipped from processing if the Exchange.ManageAsApp permission and the Global Reader role are not assigned to the backup application. 

• The 'Veeam Backup for Microsoft 365 Service' gets stuck in the Starting state until the indexing query for objects from all Microsoft 365 organizations added to Veeam Backup for Microsoft 365 is queued for execution.
  

Backup and Backup Copy

• Exchange backup to a local Jet-based repository may fail with the error:

  JetError -1605, JET_errKeyDuplicate, Illegal duplicate key
  

• A backup job may remain displayed with a Running state after all the processed objects in the job have failed.
• A backup copy job targeted to an immutable repository on a Hitachi S3 compatible storage fails with the error:

  There is an error in XML document (1, 1)
  

• SharePoint and OneDrive backups may fail with the error:

  Invalid MIME content-length header encountered on read
  

• After the connection to Microsoft 365 endpoints fails, a backup job may be completed with the warning:

  Nothing to process
  

Restore

• OneNote files larger than 2 GB are not exported when saving a backed-up OneDrive as ZIP.
• The folder hierarchy is not preserved upon restoring a backed-up SharePoint library.
• In Veeam Explorer for Microsoft SharePoint, authentication to Microsoft 365 fails for an organization in the U.S. Government GCC High region.
• In Veeam Explorer for OneDrive for Business, copying an item that was previously restored from a backup to the original location using the 'Keep' option fails with the error:

  File not found
  

• The %\ProgramData\Veeam\Backup365\Dumps folder may get filled with dump files generated for items that failed during restore or export operations initiated via REST APIs.

PowerShell

• Teams channel posts export with the Export-VETPost PowerShell cmdlet completes with an empty HTML file.

P20230704 (7.0.0.3968)

What’s new

• Added support for backup and restore of public folder and discovery search mailboxes for organizations using modern app-only authentication.
• Identification of a shared mailbox user type in organizations using modern app-only authentication.
• 2x increase of the license grace limits for user accounts when the "Update license automatically" option is enabled.
  • Subscription: 10 user accounts or 10% of the license count >> 20 user accounts or 20% of the license count
  • Rental: 20 user accounts or 20% of the license count >> 40 user accounts or 40% of the license count
• Logging of previously installed private fixes for Veeam Backup for Microsoft 365.

Enhancements

• Up to 43% faster move of Exchange backup data between a JET database-based repository and an object storage repository.
• Restore, save, and export operations for a SharePoint site with a complex hierarchy are initiated up to 30x faster from an object storage repository and up to 1.3x faster for a local JET database-based repository.

Resolved Issues

General

• Attempting to add an Amazon S3 object storage with a bucket located in the following regions fails:
  • Europe (Zurich) eu-central-2
  • Asia Pacific (Hyderabad) ap-south-2
  • Asia Pacific (Melbourne) ap-southeast-4
  • Europe (Spain) eu-south-2
  • Europe (Zurich) eu-central-2
  • Middle East (UAE) me-central-1
• Restarting a forcibly stopped or crashed Veeam.Archiver.Proxy service may fail with the error:

  Write lock may not be acquired with read lock held. This pattern is prone to deadlocks.
  

• Organization may remain displayed as stored in a repository after all its backup data have been deleted.
• Under certain conditions, an incremental synchronization of an organization cache may fail with the warning:

  SQLite Error 19: 'UNIQUE constraint failed: GroupMembers.GroupInternalAccountId, GroupMembers.MemberInternalAccountId'.
  

• Slow repositories upgrade and remote backup proxy rescan after upgrading to Veeam Backup for Microsoft 365 7.

Backup and Backup Copy

• A backup copy job performed via an archiver appliance is displayed in the running state after the job is stopped by a user or failed.
• A backup job containing multiple OneDrive for Business objects fails if the processing of some of the objects fails with the error:

  SharePoint Foundation is not the owner of this file.
  

• Backup of Microsoft Teams channel messages fails with the error:

  An item with the same key has already been added.
  

• Backup of an Exchange mailbox may fail with the error:

  Index was outside the bounds of the array.
  

• Under certain conditions, a backup job on a retry may mistakenly processes all objects, including those that have been backed up successfully on the first backup run.
• When using modern app-only authentication, a SharePoint backup job that is processing OneNote files may complete with the warning:

  Download request retry timeout exceeded.
  

• Under certain conditions backup of a personal SharePoint site may fail with the error:

  Object reference not set to an instance of an object.
  

• Backup of Microsoft Teams channel messages may fail with any of the following errors:

  UnknownError
  

  Object reference not set to an instance of an object
  

  The remote server returned an error: (404) Not Found.
  

• If a backup job that includes an entire organization completes with some errors including the warning:

  Mailbox does not have a valid Microsoft 365 license, a subsequent job retry also performs an attempt to resolve users without a valid Microsoft 365 license and completes with a warning state.
  

• A backup copy job that includes Exchange mailboxes with a large number of folders runs with low processing rates.
• A SharePoint backup job targeted to a local Jet database-based repository runs with low processing and saving rates.
• Synchronization of a repository extended to object storage may fail with the error:

  1605, JET_errKeyDuplicate, Illegal duplicate key.
  

Restore

• When browsing backup with Veeam Explorer for Microsoft Exchange via Veeam Cloud Connect, loading backup data may take hours.
• Restoring SharePoint items to a specific list may fail with the error:

  Failed to convert field: Service (value: %value%, type: LookupMulti). The field was skipped.
  

• A SharePoint or OneDrive restore initiated via REST APIs may fail with the error: User does not have sufficient permissions to perform restore operation.
• After restoring a deleted team, the account used to log in to Microsoft 365 during Microsoft Teams restore becomes an owner of this team.
• Exporting an Exchange mailbox to a PST file may fail with the error:

  The value 98634 must be in the range from 0 to 98633. Parameter name: value.
  

• When browsing Exchange backups stored in an object storage repository a mailbox may be displayed as empty and in product logs the following error is displayed:

  -1605, JET_errKeyDuplicate, Illegal duplicate key.
  

• When restoring  SharePoint data from an object storage repository, the amount data downloaded from object storage exceeds the size of data to restore.

Restore Portal

• In the Restore Portal, the Restore Status of an active Microsoft Teams restore session is displayed as Never started.
• Authentication to the Restore Portal fails if the Veeam Backup for Microsoft 365 server uses an internet proxy server as a connection gateway.
• Under certain conditions, backup data may not be immediately displayed in the Restore Portal after a point in time is selected.
• In the Restore Portal, opening a list of available restore points requires significant time.

REST APIs

• The (GET) v7/Jobs request doesn’t return the "lastBackup" parameter for backup jobs that have finished with warnings.
• The (GET) v7/Jobs request incorrectly displays the "lastRun" value for backup jobs that are in the running state.
• The (GET) /v7/RestoreSessions/<restore-session-id>/organization/teams request incorrectly returns the "privacy" parameter value for teams that are set with the "HiddenMembership" privacy attribute.
• An empty folder is created after exporting an Exchange mailbox or a mailbox folder to a PST via REST APIs.
• The (GET) /v7/objectstoragerepositories/ request fails to return Amazon S3 Glacier object storage repositories with the error:

  500 Internal Server
  

• In larger environments with multiple organizations in the Veeam Backup for Microsoft 365 scope, the (GET) /v7/Organization/OrganizationID/Jobs returns a list of backup jobs with a significant delay.

PowerShell

• Starting a remote Exchange restore session with the Start-VBOExchangeItemRestoreSession cmdlet may fail with the error:

  Cannot access a disposed object.
  

• The Get-VBOBackupApplication cmdlet returns an array when only one application is configured.
• The Set-VBOBackupApplication cmdlet incorrectly returns the value ‘00000000-0000-0000-0000-000000000000’ as an application ID.
• The Set-VBOBackupApplication cmdlet does not update an application certificate thumbprint.

Integration

• Veeam Service Provider Console Administrator Portal displays a managed Veeam Backup for Microsoft 365 server with the Outdated state if the retention period on a repository is set with a specified number of days.

P20230512 (7.0.0.3604)

Resolved Issues

General

• Repository upgrades take additional time after upgrading to Veeam Backup for Microsoft 365 7.
• After the Veeam.Archiver.Proxy service process fails or is terminated manually, the Veeam Proxy service fails to restart automatically with the error:

   Write lock may not be acquired with read lock held. This pattern is prone to deadlocks.
  

• When applying retention on Object Storage Repositories, the Retention Job downloads an excessive amount of metadata.

Backup

• If there were zero new messages written to a Teams Channel on the last run, the Teams channel posts are requested again after a full sync has been initiated for a Teams backup job. 

• On incremental OneDrive and SharePoint backup job runs, new items may be skipped from a backup if, between backup job runs, a large number of items or folders were added/created in the source and then deleted in bulk.

  For more information, review: KB4447
• Team tabs added with the + button in the Teams app and linked to Word, Excel, PowerPoint, or Visio applications may be skipped from a backup.
  
  For more information, review: KB4448

 REST APIs

• The (GET) v7/Jobs request returns an incorrect value for the "lastRun" parameter.

• The (GET) v7/Jobs request doesn’t return the "lastBackup" parameter for backup jobs that have finished with warnings.

P20230421 (7.0.0.3007)

Resolved Issues

General

• Veeam Backup for Microsoft 365 7 writes successful authorization attempts to the Microsoft Windows event log every second, flooding the log with 4904/4905 security events.

Backup

• A SharePoint backup job may fail with the error:

  Failed to process site: %name% (%site URL%). The remote server returned an error: (429).
  

  For more information, review KB4442.
• Backup to object storage may fail on synchronizing metadata to the local cache with the error:

  JetError -1605 pattern cannot be determined
  

• Job session average ‘Read rate’ and ‘Write rate’ metrics are displayed incorrectly after the completion of a backup job targeted to an object storage repository.

• A Microsoft Teams backup job may fail on processing team tabs with the error:

  Object reference not set to an instance of an object.
  

  For more information, review: KB4201
• A SharePoint backup job that includes sites created by the Loop app fails with the following:

  The remote server returned an error: (401) Unauthorized. SharePoint Loop app is currently available in Preview, and sites that it creates are unsupported and will be skipped from processing.
  

  This cumulative patch does not add support for sites created by Loop; it allows Veeam Backup for Microsoft 365 jobs to skip such sites silently.
  For more information, review: KB4440
   

REST APIs

• The (GET) /v7/DataRetrievalSessions may fail with the error:

  Object reference not set to an instance of an object.
  

• The (GET) /v5/JobSessions request may fail with the error:

  Object reference not set to an instance of an object.
  

P20230302 (7.0.0.2914)

Resolved Issues

• The following warning may be displayed in the action log of a backup job configured to process an entire organization:

  Mailbox does not have a valid Microsoft 365 license
  

  These warnings were suppressed in Veeam Backup for Microsoft 365 v6a P20221215 (build 6.1.0.438). However, upon additional observation and testing after the release of that cumulative patch, we have identified some edge cases where the fix may not help. Starting with Veeam Backup for Microsoft 365 v7 (build 7.0.0.2911), the suppression of the warning was rolled back.

To manually update an existing Veeam Backup for Microsoft 365 version 7 (7.0.x) deployment to the latest Cumulative Patch listed on this page, follow the same steps as upgrading Veeam Backup for Microsoft 365.

1. Ensure that there are no active Backup or Restore sessions running.
2. Close all Veeam Backup for Microsoft 365 and PowerShell consoles.
3. Mount the ISO on the Veeam Backup for Microsoft 365 server.
4. Run Veeam.Setup from the ISO
5. Click Update and follow the prompts to update the software.