Release Information for Veeam Backup for Microsoft 365 8.6 and Cumulative Patches

KB ID: 4913
Product: Veeam Backup for Microsoft 365 | 8.6
Published: 2026-09-14
Last Modified: 2026-11-13
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Requirements

This release can be used to:

  • upgrade an existing v8, v8.1, v8.2, v8.3, v8.4, v8.5, or v8.6 deployment of Veeam Backup for Microsoft 365 to v8.6 P2.
  • install a new deployment of Veeam Backup for Microsoft 365 v8.6 P2.

After installing this release, the Veeam Backup for Microsoft 365 build number will be 8.6.0.5021.

Release Information

8.6.0.5021

2026-11-18

Bug Fixes

General
  • After upgrading to version 8.6, backup or restore of SharePoint and OneDrive data stored in a JET-based repository fails with the error:
    JetError -1504, JET_errNullInvalid, Null not valid
    
Backup and Backup Copy
  • OneDrive backup to an immutable Azure Blob Storage repository fails with the error:
    Failed to apply immutability to object {path} because the object is already immutable.
    
Restore
  • Restoring or exporting OneDrive data from a JET-based repository with Veeam Explorer for Microsoft OneDrive fails or completes with failed items, with one of the following errors:
    Parent of the item not found
    
    or
    The given key '{key}' was not present in the dictionary.
    

8.6.0.5011

2026-10-27

Security

  • CVE-2026-106078 | Severity: Medium (6.9)
    A vulnerability allowing an unauthenticated attacker to bypass REST API authentication with a forged federation token and receive responses from REST API endpoints that do not call the Veeam Backup for Microsoft 365 backup service.
  • CVE-2025-64394 | Severity: Medium (4.3)
    A vulnerability allowing a low-privileged local user to write arbitrary files with SYSTEM privileges during the installation of Veeam Backup for Microsoft 365, which can lead to privilege escalation or denial of service.
  • The following .NET components were updated to version 8.0.31:
    • Microsoft ASP.NET Core Runtime
    • Microsoft .NET Desktop Runtime
    • Microsoft .NET Runtime
  • The following libraries were updated:
    • AngleSharp to version 1.7.2
    • MailKit to version 4.16.0
    • MessagePack to version 2.5.302
    • MimeKit to version 4.16.0
    • System.Formats.Asn1 to version 8.0.2
    • System.Security.Cryptography.Xml to version 8.0.4

New Features and Enhancements

  • When Exchange Online does not respond to a folder export request, the affected folder is now skipped, the mailbox backup completes with a Warning status, and a restore point is created. The skipped folder is retried during the next incremental backup.
  • When the Sync Issues folder cannot be retrieved, the folder is now skipped and the mailbox backup creates a restore point instead of failing.
  • Placeholder objects left after a public folder migration from on-premises Microsoft Exchange are no longer added to the backup, which prevents the following error:
    ErrorNonExistentMailbox
    
    Public folders are now protected through the root public folder mailbox, which is displayed as a single object in the job.
  • Legacy bot sites (http://bot/<ID>/) no longer cause SharePoint backup jobs to fail with the error:
    This can happen if the application has not been installed by the administrator of the tenant
    
    Such sites are now skipped, including when they are excluded from the backup. These sites are still displayed in the list of organization sites.
  • Retries of throttled Microsoft Graph and SharePoint requests that run in parallel are now spread over time to avoid repeated throttling.
  • SharePoint backup to a JET-based repository no longer fails after the retry window is exhausted when Microsoft Graph throttling occurs. The wait time between retries is now aligned with the delay recommended by Microsoft 365.
  • Calendar items with meeting attendees that have no email address are now restored with the attendee's display name only, instead of the attendees being dropped.
  • The Mailbox Protection report is now generated for the remaining mailboxes when a discovery mailbox has no primary SMTP address. Such mailboxes are skipped with a warning that contains the mailbox ID.
  • Retention tasks that resume after an interruption now skip objects that were processed in the previous run.
  • Improved the error message shown when OneDrive or SharePoint data is restored to a site that does not exist. The "Cannot connect to Microsoft 365" error now includes the reason "The requested site does not exist."
  • Veeam Backup for Microsoft 365 now identifies its requests to Microsoft Graph, Exchange Web Services, and SharePoint Online using the User-Agent format that Microsoft recommends for independent software vendors, which reduces throttling.

Bug Fixes

General
  • Retry delays for throttled Microsoft Graph and SharePoint requests are calculated incorrectly.
  • After the NATS server is unavailable for several minutes, operations that rely on the backup proxy repeatedly fail with a timeout until the proxy service is restarted.
  • Job sessions get stuck and do not complete when the connection between a backup proxy and the NATS server stops responding while still appearing active. The proxy does not recover until its service is restarted.
  • Enabling or disabling a backup job in the Veeam Backup for Microsoft 365 console fails with the error:
    Unable to cast object of type 'Veeam.Archiver.Interfaces.DataContracts.JobConfig[]' to type 'System.Int32'.
    
  • A retention task on an object storage repository with SharePoint data fails with the error:
    Cannot find versioned blob.
    
Backup and Backup Copy
  • When Microsoft 365 throttles requests at the start of the job, a SharePoint backup job is not retried and fails with the error:
    Objects resolve error
    
  • When the personal site owner is not set in SharePoint Online, OneDrive is skipped with the error:
    Failed to resolve personal site owner. The user may not have a valid Microsoft 365 license with a SharePoint plan enabled
    
  • SharePoint and OneDrive backup jobs complete with the warning:
    Data location is undefined.
    
  • Backup jobs that include Microsoft 365 groups may occasionally skip some of the groups or not back up all of their members. The issue mostly affects organizations with a large number of groups.
Restore
  • Restoring or exporting SharePoint and OneDrive data fails with one of the following errors:
    Cannot find a SharePoint item
    
    or
    Cannot find a folder
    
    or
    Parent of the item not found
    
    The restore may also complete with a warning and restore folders without the files they contain.
  • When browsing a restore point, an outdated version of a SharePoint or OneDrive item may be shown as the current one.
  • When a mailbox is explored with the Show all versions of items that have been modified by user option enabled, restoring it to the original location leaves each item in its oldest backed-up version instead of the version from the selected restore point.
  • When a deleted SharePoint site is restored to the original location, the default document library is restored with a number appended to its name, and the restore completes with warnings.
  • When the Show deleted items and Show all versions options are enabled and a file was moved to the OneDrive root and edited between two backups, browsing or searching OneDrive data in Veeam Explorer for Microsoft OneDrive fails with the error:
    An item with the same key has already been added
    
  • Restoring OneDrive data to another location fails when the name of the target folder starts with a dot.
REST APIs
  • Session events for a bulk mailbox restore started with the (POST) v8/RestoreSessions/{restoreSessionId}/Organization/Mailboxes/restore endpoint show "itemSizeBytes": 0 instead of the actual size of the restored data.
PowerShell and Data Management
  • After a repository repair, the integrity check reports SharePoint files whose actual content is an HTML error page as corrupted, even though these files were backed up correctly.
  • After a repository repair, some SharePoint files with corrupted data remain unrepaired, and the integrity check still reports them as corrupted. This occurs when the corrupted data is stored in a different location in the object storage repository than expected.
  • When an integrity check runs while a SharePoint backup job is in progress, data of some files uploaded by the job is removed, and these files are reported as having missing file data.
  • Repository repair logs report the same misplaced corrupted SharePoint file twice, as missing and as misplaced, and misplaced files are not taken into account in repair reports.

8.6.0.1102

2026-09-14

Security

  • CVE-2026-106077 | Severity: High (8.3)
    A vulnerability allowing a user with the Veeam Backup for Microsoft 365 Administrator role to read arbitrary files on the backup server with LocalSystem privileges.
  • CVE-2026-106076 | Severity: Critical (9.0)
    A vulnerability allowing an authenticated organization-transfer peer to inject SQL into the configuration database of the source Veeam Backup for Microsoft 365 server, leading to cross-tenant read and write of configuration data and remote code execution as the PostgreSQL service account.

New Features and Enhancements

  • Added PowerShell cmdlets to remediate data in JET-based repositories, repositories with backup copies, and immutable repositories affected by the issue described in KB4835. For more information, see KB4874.
Veeam Backup for Microsoft 365 v8.6 includes enhanced Integrity Check capabilities that provide broader validation coverage for the issue described in KB4835. Customers who ran the Integrity Check from KB4874 with version 8.5 are strongly encouraged to upgrade to version 8.6 and rerun the Integrity Check for each applicable repository before considering the environment fully reviewed.
  • When an organization is added or edited, the backup app registrations in Microsoft Entra ID automatically receive the permissions required to support Exchange mailbox protection after EWS retirement. For more information, see KB4820.
  • Added the ability to place object storage backup repositories into maintenance mode using PowerShell cmdlets or the REST API. While a repository is in maintenance mode, Veeam Backup for Microsoft 365 blocks all operations on that repository, allowing administrators to safely perform storage-level maintenance without interference.

Bug Fixes

General
  • A retention task gets stuck and times out after the NATS server restarts.
Backup and Backup Copy
  • When the public folder hierarchy root stored in the backup no longer matches the root folder reported by Microsoft 365, public folder mailbox backup fails while processing the hierarchy root (IPM_SUBTREE) with the error:
    Object reference not set to an instance of an object
    
  • In multi-geo organizations where location protection is disabled, SharePoint backup jobs fail with the error:
    Failed to resolve sites: ambiguous locations found
    
  • SharePoint incremental backup jobs process all site changes from the beginning instead of continuing from the last backup point after SharePoint rejects a change token as outdated.
  • When redirect site URL lookups are throttled and cannot acquire a request slot within the allowed wait time, even if throttling is not reported at the tenant level, a SharePoint backup job fails at the site resolution stage with the error:
    Request must be retried
    
  • In organizations with a hybrid Exchange deployment, some mailboxes are skipped during backup with the warning:
    Exchange account was not found.
    
  • A backup job that fails at the resolve stage because of Microsoft 365 throttling is reported as Failed. No restore point is created and no retry is attempted, even when some objects were processed successfully.
  • A backup job processing SharePoint or Teams data does not trigger a retry run when all objects fail with the error:
    Access to this site is blocked.
    
  • In multi-geo Microsoft 365 organizations, a throttling event in one geo region causes backup jobs in all other regions to slow down or fail.
  • A Teams backup job fails with an out-of-memory error when processing channels that contain a very large number of messages.
  • In multi-geo SharePoint environments, a backup job fails for sites whose data location cannot be resolved to any configured geo region.
  • A SharePoint backup job intermittently fails during the resolve stage with the error:
    Object reference not set to an instance of an object
    
  • When the backup scope includes archived Microsoft Teams, a backup job fails with the error:
    The response status code does not indicate success: 400 (Bad Request)
    
Restore
  • Browsing or restoring OneDrive and SharePoint data from archive-tier object storage hangs and eventually times out.
  • Search in Veeam Explorer for Microsoft Exchange fails with an ArgumentOutOfRangeException error when a mailbox item contains an RTF-formatted body with emoji or other characters outside the Basic Multilingual Plane.
  • Saving OneDrive items using Veeam Explorer for Microsoft OneDrive fails with the error:
    Object reference not set to an instance of an object.
    
REST APIs
  • Advanced search across Exchange items filtered by DateReceived using an ISO-8601 UTC timestamp, for example 2025-01-02T05:59:59Z, fails with HTTP 500.
  • The (GET) v8/BackupRepositories/{repositoryId}/UserData REST API endpoint responds very slowly on large repositories.
PowerShell and Data Management
  • Repository integrity check and repair operations fail with an out-of-memory error on large repositories.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.