Veeam Support Knowledge Base

The HTTP request was forbidden with client authentication scheme

2026-07-02T00:00:00Z

The HTTP request was forbidden with client authentication scheme

KB ID:	4796
Product:	Veeam Data Cloud for Microsoft 365 Veeam Backup for Microsoft 365
Published:	2025-11-25
Last Modified:	2026-07-02

July 2, 2026 — Issue Recurrence

Starting on July 2, 2026, Veeam Customer Technical Support began observing an increase in cases reporting that jobs were failing with the same error documented in this article. The Solution provided in this article has not reliably resolved these recent cases. This issue is under active review in collaboration with Microsoft Support, and updates will be communicated as additional information becomes available.

Veeam Data Cloud for Microsoft 365 Configuration Check Notice

On 2026-05-22, an update to the Veeam Data Cloud for Microsoft 365 services introduced a configuration check to proactively detect configuration issues that may cause the issue described in this article's Challenge section. The Cause and Solution section of this article remains relevant and should be used to resolve the configuration issue and pass the configuration check.

Challenge

Microsoft 365 backups display the following error:

The HTTP request was forbidden with client authentication scheme 'Anonymous'.

This error typically occurs when specific mailboxes are accessed during backup jobs.

Cause

It was confirmed on March 27th, 2026, that Microsoft recently applied a patch to correct how Exchange Online enforces Exchange Web Services (EWS) access. Previously, some environments were able to access mailboxes via EWS even when it was not explicitly enabled (i.e., $Null status). After Microsoft corrected this behavior, EWS must now be explicitly enabled at both the organization and mailbox levels for backups to succeed.

For more information, please reference: The way to control EWS usage in Exchange Online is changing

For details about the occurrence of this issue from December 2025, please refer to the More Information section at the bottom of this article.

Solution

Microsoft provides training resources for utilizing PowerShell to manage Exchange Online:
Microsoft Learning Center: Manage Exchange Online by using Windows PowerShell

To address the root cause of the problem, confirm and configure EWS access to be explicitly enabled at both the organization and mailbox levels:

Part 1: Set the `EwsEnabled` Flag at the Tenant (Organization) Level

Review the EWS enablement status using the following PowerShell command:

#Get the organization's EwsEnabled state.
Get-OrganizationConfig | Fl EwsEnabled

If the output is anything other than an explicit $true, access via EWS must be enabled using the following command:

#Set the organization's EwsEnabled state to $true.
Set-OrganizationConfig -EwsEnabled $true

Part 2: Set the `EwsEnabled` Flag at the User (Mailbox) Level

Review the list of mailboxes where the EwsEnabled flag is not $true using the following PowerShell command:

#Get all mailboxes where EwsEnabled state is not set to $true.
Get-CASMailbox -ResultSize Unlimited | Where-Object { $_.EwsEnabled -ne $true } | Select-Object Identity, PrimarySmtpAddress, EwsEnabled

Any mailbox listed in the results from the previous step that needs to be backed up must have the EwsEnabled flag set to $true using the following command:

#Set a single mailbox's EwsEnabled state to $true
Set-CASMailbox mailbox@address.com -EwsEnabled $true

Optionally, customers may choose to set the EwsEnabled flag to $true for all mailboxes using the following PowerShell command:

#Bulk set EwsEnabled to $true for all mailboxes where it is not already set to $true.
Get-CASMailbox -ResultSize Unlimited | Where-Object { $_.EwsEnabled -ne $true } | Set-CASMailbox -EwsEnabled $true

Part 3: Wait and Verify Results

Wait. The new values may take up to 24 hours to replicate and take effect.
Re-check the backup job.

More Information

Similar Issue from December 2025

Challenge

Microsoft 365 backups display the following error:

The HTTP request was forbidden with client authentication scheme 'Anonymous'.

This error typically occurs when specific mailboxes are accessed during backup jobs.

Cause

Following a coordinated investigation with Microsoft, we have confirmed that certain subscription plans, such as Exchange Online Kiosk and similar limited-service SKUs, may not support the API required by Veeam Backup for Microsoft 365.

As a result, calls to the API return an HTTP 403 Forbidden error, causing backup jobs to fail.

Solution

Status: This issue is resolved as of December 2025.
Issue Root Cause: Mailboxes licensed with Exchange Online Kiosk, Microsoft 365, and Office 365 F1, and Microsoft 365 and Office 365 F3, were temporarily blocked from accessing the API used by Veeam for backup operations. The access has been restored, and the issue has been resolved.

For more information, please refer to the following Microsoft article: Update to EWS Access for Kiosk / Frontline Worker Licensed Users.

Veeam R&D continues to work closely with Microsoft on the upcoming deprecation of the EWS API. A future update will address these changes. A Veeam Support Statement regarding EWS deprecation is available on KB4820.

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.

Release Information for Veeam Backup for Microsoft 365 8.5

2026-06-29T00:00:00Z

Release Information for Veeam Backup for Microsoft 365 8.5

KB ID:	4873
Product:	Veeam Backup for Microsoft 365 \| 8
Published:	2026-06-29
Last Modified:	2026-07-01

Requirements

This release can be used to:

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

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

Release Information

8.5.0.1014

2026-06-30

Release Notes 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 using the REST API.
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.
Teams post timestamps in exported HTML files were displayed in the timezone of the machine running the REST API server instead of UTC, causing dates to appear incorrect when compared to Microsoft Teams.

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.

Download Information

Download VB365 8.5 ISO

See Veeam Backup for Microsoft 365 Current Version Download Page for ISO hashes.

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.

How to Identify and Repair Files That Cannot Be Opened After Restore

2026-06-29T00:00:00Z

How to Identify and Repair Files That Cannot Be Opened After Restore

KB ID:	4874
Product:	Veeam Backup for Microsoft 365 \| 8
Published:	2026-06-29
Last Modified:	2026-06-29

Purpose

This article provides steps to identify and repair SharePoint, OneDrive, Teams files, and list attachments that were backed up with corrupted content due to the issue described in KB4835.

Note: These instructions apply only to non-immutable object storage repositories that contain backups. Verification and remediation for JET-based repositories and backup copies will be provided in a future update.

Solution

Before You Begin

Ensure you’re running Veeam Backup for Microsoft 365 version 8.5 or later before proceeding.

Repair Procedure

The following steps are to be completed for each non-immutable object storage repository that contains SharePoint, OneDrive, and Teams files. The steps in this section use PowerShell commands that reference variables set in one step and called in later steps.

Step 1: Run an Integrity Check

Open PowerShell and import the Veeam Backup for Microsoft 365 PowerShell module:

Import-Module "C:\Program Files\Veeam\Backup365\Veeam.Archiver.PowerShell.dll"

Run the following cmdlet for the repository being investigated:

$repository = Get-VBORepository -Name "Repository Name"
Test-VBORepository -Repository $repository

Step 2: Review the Results

If the Test-VBORepository output contains either of the following messages, proceed to Step 3:

The following site has corrupted file data

The following list contains items referencing corrupted files

If neither message appears, no further action is required for that repository.

Step 3: Scan Repository and Flag Affected Items

Run the following cmdlet to scan the repository and flag the affected items for re-backup. Their correct content will be redownloaded during the next backup job run in Step 4. Note that during scanning, the repository remains locked for any other operations, including backups, restores, and management. All backup and restore sessions related to this repository must be closed before running a repair session.

$session = Start-VBORepositoryRepairSession -Repository $repository -Type CleanMissingFilesData -Mode Full -Scope Full
                     
                    

To limit the scope to a specific SharePoint site, use the -WebIds parameter:

$session = Start-VBORepositoryRepairSession -Repository $repository -Type CleanMissingFilesData -Mode Full -WebIds '{InternalWebId}','{InternalWebId}'
                     
                    

Wait for the session to complete before proceeding to Step 4. To verify that a session has completed, check its status using the session object returned in Step 3:

Get-VBORepositoryRepairSession -Id $session.Id
                     
                    

Step 4: Run Backup Jobs

After the repair session has finished, run the backup jobs containing impacted SharePoint, OneDrive, and Teams files data. Files that are still present in production will be redownloaded with their correct content.

Step 5: Review Outcome and Identify Unrecoverable Files

To identify files that could not be redownloaded in Step 4, run the following cmdlet:

Test-VBORepository -Repository $repository -DetailedOutput
                     
                    

The output will be saved to logs located in: C:\ProgramData\Veeam\Backup365\Logs\IntegrityVerification\

Files that could not be redownloaded will have log entries containing the following two messages:

Backed-up file is empty:

RepairHistory: FileWasReset

Error Line Example:

[Info] Integrity verifier generated message (repository ID: {repo-guid}, tenant ID: {tenantID}, type: FilesIntegrityVerifier, severity: Error, text: Backed-up file is empty: OrganizationId: {orgGuid}, SiteId: {siteID-guid}, WebId: {webID-guid}, InternalWebId: {intwebID-guid} (file: Id: {fileID-guid}, Version: 513, ContentLength: 0, BytesInStorage: 0, StorageType:None, RepairHistory: FileWasReset).)

To simplify this process, open the log files in Notepad++ and use the following regex search:

^(?=.*Backed-up file is empty)(?=.*RepairHistory: FileWasReset).*$

More Information

For the description of the root cause, see KB4835: Potential Issue With Backing up SharePoint, OneDrive, Teams Files, and List Attachments.

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.

Email item data export from EWS failed

2026-06-29T00:00:00Z

Email item data export from EWS failed

KB ID:	4867
Product:	Veeam Data Cloud for Microsoft 365 Veeam Backup for Microsoft 365
Published:	2026-06-03
Last Modified:	2026-06-29

Challenge

Exchange Online backup jobs in Veeam Backup for Microsoft 365 and Veeam Data Cloud for Microsoft 365 may fail to process mailboxes, returning one of the following errors:

Processing mailbox  failed with error: Email item data export from EWS failed (item IDs: [...]). The operation has timed out.

Or:

The server cannot service this request right now. Try again later.

Cause

This issue occurs when an Exchange Web Services (EWS) export operation takes longer to complete than the default timeout allows. Exporting very large mailbox items or encountering EWS throttling can prolong the operation past the timeout, causing the backup job to fail.

Solution

For Veeam Data Cloud for Microsoft 365
A fix has been deployed to the environment. No action is needed from Veeam Data Cloud for Microsoft 365 customers.
For Veeam Backup for Microsoft 365
A fix has been included with Veeam Backup for Microsoft 365 8.5.

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.

Potential Issue With Backing up Sharepoint, Onedrive, Teams Files, and List Attachments

2026-06-29T00:00:00Z

Potential Issue With Backing up Sharepoint, Onedrive, Teams Files, and List Attachments

KB ID:	4835
Product:	Veeam Data Cloud for Microsoft 365 Veeam Backup for Microsoft 365 \| 7.0 \| 7a \| 8 \| 8.1 \| 8.2 \| 8.3
Published:	2026-03-31
Last Modified:	2026-07-01

Challenge

Backup of SharePoint, OneDrive, and Teams data completes successfully, and subsequent restores of this protected data are successful. However, when opening some of the restored files or list attachments, users may find that these items do not open correctly in their associated applications (e.g., Microsoft Word, Excel, PowerPoint, and Adobe Acrobat).

Common errors reported by customers are:

“The file is either not a supported file type or has been damaged.”

“Word found unreadable content…”

“Excel cannot open the file ... because the file format or file extension is not valid.”

“Sorry, this document can't be opened for editing.”

The affected files retain their original names and extensions (e.g., .docx, .pdf) but cannot be viewed or edited.

Cause

During backup operations, files, list attachments, or images from SharePoint, OneDrive, or Teams were saved with the contents of the HTML error pages returned by the API, rather than their actual file content.

Veeam first observed this issue in early March 2026.

This issue impacts Veeam Data Cloud for Microsoft 365 and all supported versions of Veeam Backup for Microsoft 365. It is independent of repository type, affecting both JET-based and object storage repositories.

No errors are shown in backup jobs or restore tasks; the issue surfaces only when the user attempts to open the restored file.

Solution

Veeam Data Cloud for Microsoft 365

No action is required from Veeam Data Cloud for Microsoft 365 users. The platform has been automatically updated to the latest version to address the root cause, ensuring that newly created and changed items are backed up correctly.

Affected items in the backups, if any, that have not changed in production since the last backup remain impacted by the issue. Veeam Data Cloud for Microsoft 365 will remediate the impacted items automatically where possible.

Starting June 30, 2026, a granular remediation process began on a tenant-by-tenant basis. A special maintenance message will be displayed in the UI when the process starts for your organization. During the remediation process, subsequent backup job runs may take longer than usual as all impacted data is reprocessed.

Veeam Backup for Microsoft 365

The root cause of the issue described in this article was resolved starting in Veeam Backup for Microsoft 365 v8.4 (build 8.4.0.1457), ensuring that new and changed items are backed up correctly. All Veeam Backup for Microsoft 365 customers are advised to upgrade to the latest version as soon as possible.

Affected items in the backups, if any, that have not changed in production since the last backup remain impacted by the issue.

Veeam Backup for Microsoft 365 v8.5 (build 8.5.0.1014 introduced a method for customers to remediate those impacted items.
For more information, please review: KB4874: How to Identify and Repair Files That Cannot Be Opened After Restore

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.

External Client App (ECA) for Veeam Data Cloud — Adapting to New Salesforce Security Requirements

2026-06-29T00:00:00Z

External Client App (ECA) for Veeam Data Cloud — Adapting to New Salesforce Security Requirements

KB ID:	4812
Product:	Veeam Data Cloud for Salesforce
Published:	2026-03-30
Last Modified:	2026-06-29

Support Statement

Summary of Changes to Salesforce Security Protocols

Salesforce has introduced new security protocols for third-party applications accessing Salesforce organizations. This change affects all third-party products that integrate with Salesforce, requiring those vendors to transition from legacy Connected Apps to External Client Apps (ECAs). As part of this shift, organizations using external products for data backup must update their integrations to comply with these new requirements and prepare for the eventual deprecation of Connected Apps.

Introducing the External Client App (ECA) for Veeam Data Cloud

To meet Salesforce’s new security requirements, Veeam has released the External Client App (ECA) for Veeam Data Cloud managed package. This package enables customers to securely connect Veeam Data Cloud for Salesforce to their Salesforce organizations, in compliance with Salesforce standards. Upon installation, the package creates an External Client App with the necessary permissions for Veeam Data Cloud to perform backups. It also automates client key and secret rotation, simplifying ongoing security management. Installation of this package is required for each Salesforce organization that will be protected with Veeam Data Cloud before it can be added and backed up.

Existing Veeam Data Cloud for Salesforce Customers

For Salesforce organizations added to Veeam Data Cloud for Salesforce before the Salesforce Winter ’26 release, Salesforce will provide a transition period during which the Connected App can continue to be used. However, all customers are encouraged to transition to the External Client App (ECA) for Veeam Data Cloud managed package and re-authorize their Salesforce organizations in Veeam Data Cloud. This approach ensures integration with Salesforce’s latest security protocols and helps prevent any last-minute changes when the Connected App is eventually deprecated.

Additional Security Enhancements for Salesforce Connections

To further align with Salesforce security standards, the following security options are enabled on both the External Client App and the legacy Connected App (the latter for customers who have not yet transitioned to the ECA):

Proof Key for Code Exchange — Already Enabled
Refresh Token Rotation — Already Enabled
Refresh Token 30-Day Idle Timeout — Already Enabled
Allowlist Ranges for Refresh Tokens — Will be enabled on July 6th, 2026.

After these options take effect, an existing refresh token may no longer be valid under the new rules the next time a Salesforce access token expires. If this occurs, a prompt to re-authorize the Salesforce connection is displayed so that a new, compliant refresh token can be issued.

In addition, once Allowlist Ranges for Refresh Tokens is enabled, customers who have Login IP Ranges configured for the backup user must add the following IP addresses, which are used for token refresh, to the allowed list:

EMEA: 4.223.102.146 , 9.223.216.186
APJ: 52.253.96.103 , 130.33.216.155
AMER: 52.238.211.143 , 20.236.255.222

This change might also require re-authorization of connections to Salesforce organizations.

Recommended action: To avoid missing an expired-connection event, log in to the product as soon as possible and verify that the alert for an expired Salesforce connection token is configured with a valid email address for notifications. For instructions, see Managing Notifications in the Veeam Data Cloud for Salesforce User Guide.

Supported Salesforce Editions

The External Client App (ECA) for Veeam Data Cloud managed package is supported for:

Salesforce Enterprise
Unlimited
Developer
Professional editions
^{Note: API access must be enabled for Professional editions.}

ECA Configuration Considerations

After the managed package is installed, the External Client App can be modified in Salesforce to apply additional security restrictions, such as limiting access to specific user accounts or adjusting the token refresh policy.

However, the Immediately expire refresh token option in OAuth Policies > App Authorization must not be enabled. If this option is selected, Veeam Data Cloud cannot maintain an active connection to the Salesforce organization, and the backup policy will require manual re-authorization each day to run.

Troubleshooting Deployment of External Client App (ECA) for Veeam Data Cloud

If the following error occurs when installing the managed package:

Missing feature: Installing this package requires the following feature and its associated permissions: External Client Applications

Please ensure that:

The installing user has the Create, Edit, and Delete External Client Apps permission enabled under System Permissions.
The External Client Applications feature is enabled for the organization.
This can be verified by confirming that External Client App Manager appears in Setup. If it does not, navigate to Setup > External Client App > Settings, select the Opt in for external client apps checkbox, and click Save.

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.

Shared Server Compatibility of Veeam Backup for Microsoft 365 and Veeam Backup & Replication

2026-06-29T00:00:00Z

Shared Server Compatibility of Veeam Backup for Microsoft 365 and Veeam Backup & Replication

KB ID:	4325
Product:	Veeam Backup & Replication \| 12 \| 12.1 \| 12.2 \| 12.3 \| 13 Veeam Backup for Microsoft 365 \| 8 \| 8.1 \| 8.2 \| 8.3 \| 8.4 \| 8.5
Published:	2022-08-10
Last Modified:	2026-06-29

Purpose

It is important to remember that Veeam Backup for Microsoft 365 and Veeam Backup & Replication are separate backup products designed to operate separately from each other. However, both Veeam Backup for Microsoft 365 and Veeam Backup & Replication utilize Veeam Explorers as secondary applications to perform application item restores. The Veeam Explorers are installed alongside either backup application. Due to this shared use of the Veeam Explorer applications, it is imperative that when both Veeam Backup for Microsoft 365 and Veeam Backup & Replication are installed on the same server, that only specific compatible versions be installed (see table below). Failure to ensure compatibility could lead to a situation where one backup product may not be able to utilize the Veeam Explorer application installed by the other backup product, thus causing application item restores to fail.

Solution

When installing Veeam Backup & Replication (VBR) and Veeam Backup for Microsoft 365 (VB365) on the same server, be mindful of the following compatibility when upgrading.

Note: As new versions of either product are released, they will be added to the table, and as versions reach End of Support, they will be removed. The release schedule of these products is not synchronized. If a version of either product is released before the compatible version of the other, it is critical to wait until inter-compatible versions are available. For example, if a new version of Veeam Backup & Replication is released and a compatible version of Veeam Backup for Microsoft 365 is not available yet, upgrading Veeam Backup & Replication would lead to the issue documented in KB3028.

	VBR 13	VBR 12.1, 12.2, 12.3	VBR 12.0
VB365 8.5	^[1], [2]	^[1], [2]	^[1]
VB365 8.4	^[1], [2]	^[1], [2]	^[1]
VB365 8.3	^[1], [2]	^[1], [2]	^[1]
VB365 8.2	^[1], [2]	^[1], [2]	^[1]
VB365 8.1	^[1], [2]	^[1], [2]	^[1]
VB365 8	^[1], [2]	^[1], [2]	^[1]

This table lists only actively supported versions.

Swipe to show more of the table

¹ KB4638: How to Use Existing Veeam Backup & Replication PostgreSQL instance for Veeam Backup for Microsoft 365 Deployment

² KB4639: Veeam Backup & Replication Install Fails with: "A later version of Veeam Explorer for Microsoft Exchange is already installed."

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.

Build Numbers and Versions of Veeam Backup for Microsoft 365

2026-06-29T00:00:00Z

Build Numbers and Versions of Veeam Backup for Microsoft 365

KB ID:	4106
Product:	Veeam Backup for Microsoft 365 \| 6.0 \| 7.0 \| 7a \| 8 \| 8.1 \| 8.2 \| 8.3 \| 8.4 \| 8.5 Veeam Backup for Microsoft Office 365 \| 1.0 \| 1.5 \| 2.0 \| 3.0 \| 4.0 \| 5.0
Published:	2021-02-17
Last Modified:	2026-06-29

This KB article lists all versions of Veeam Backup for Microsoft 365 and their respective build numbers.

For more information on downloading the latest version of Veeam Backup for Microsoft 365, visit:

_{Note: Prior to version 6.0, the product was known as Veeam Backup for Microsoft Office 365.}

Version	Console Build	Build in Logs	Release Date	Release Notes
*Veeam Backup for Microsoft 365* 8.5 Releases**
Veeam Backup for Microsoft 365 8.5	8.5.0.1014	13.5.0.1014	2026-06-29	KB4873 HTML
*Veeam Backup for Microsoft 365* 8.4 Releases**
Veeam Backup for Microsoft 365 8.4	8.4.0.1457	13.4.0.1457	2026-04-16	KB4843 HTML
*Veeam Backup for Microsoft 365* 8.3 Releases**
Veeam Backup for Microsoft 365 8.3	8.3.0.2201	13.3.0.2201	2025-12-18	KB4809 HTML
*Veeam Backup for Microsoft 365* 8.2 Releases**
Veeam Backup for Microsoft 365 8.2 P20251031	8.2.0.2202	13.2.0.2202	2025-11-06	KB4751
Veeam Backup for Microsoft 365 8.2	8.2.0.2008	13.2.0.2008	2025-10-23	KB4751 HTML
*Veeam Backup for Microsoft 365* 8.1 Releases**
Veeam Backup for Microsoft 365 8.1.2.3301	8.1.2.3301	13.1.2.3301	2025-10-24	KB4711 HTML
Veeam Backup for Microsoft 365 8.1.2.180	8.1.2.180	13.1.2.180	2025-07-01
Veeam Backup for Microsoft 365 8.1.1.159	8.1.1.159	13.1.1.159	2025-04-02
Veeam Backup for Microsoft 365 8.1.0.3503	8.1.0.3503	13.1.0.3503	2025-02-27
Veeam Backup for Microsoft 365 8.1.0.331	8.1.0.331	13.1.0.331	2025-02-11
Veeam Backup for Microsoft 365 8.1	8.1.0.305	13.1.0.305	2025-01-23
*Veeam Backup for Microsoft 365* 8 Releases**
Veeam Backup for Microsoft 365 8.0.5	8.0.5.20	13.0.5.20	2024-11-14	KB4656 HTML
Veeam Backup for Microsoft 365 8.0.4	8.0.4.29	13.0.4.29	2024-10-30
Veeam Backup for Microsoft 365 8.0.3.1073	8.0.3.1073	13.0.3.1073	2024-10-16
Veeam Backup for Microsoft 365 8 P20241004	8.0.3.1044	13.0.3.1044	2024-10-08
Veeam Backup for Microsoft 365 8 P20240910	8.0.2.200	13.0.2.200	2024-09-11
Veeam Backup for Microsoft 365 8	8.0.2.159	13.0.2.159	2024-09-03
*Veeam Backup for Microsoft 365* 7a Releases**
Veeam Backup for Microsoft 365 7a P20240418	7.1.0.2031	12.1.0.2031	2024-04-24	KB4533
Veeam Backup for Microsoft 365 7a P20240411	7.1.0.1502	12.1.0.1502	2024-04-15
Veeam Backup for Microsoft 365 7a P20240123	7.1.0.1501	12.1.0.1501	2024-01-25
Veeam Backup for Microsoft 365 7a P20231218	7.1.0.1401	12.1.0.1401	2023-12-26
Veeam Backup for Microsoft 365 7a	7.1.0.1301	12.1.0.1301	2023-12-05	PDF
*Veeam Backup for Microsoft 365* 7 Releases**
Veeam Backup for Microsoft 365 7 P20240123	7.0.0.4901	12.0.0.4901	2024-01-25	KB4425
Veeam Backup for Microsoft 365 7 P20231218	7.0.0.4551	12.0.0.4551	2023-12-25
Veeam Backup for Microsoft 365 7 P20231015	7.0.0.4388	12.0.0.4388	2023-10-15
Veeam Backup for Microsoft 365 7 P20231005	7.0.0.4385	12.0.0.4385	2023-10-12
Veeam Backup for Microsoft 365 7 P20230704	7.0.0.3968	12.0.0.3968	2023-07-13
Veeam Backup for Microsoft 365 7 P20230512	7.0.0.3604	12.0.0.3604	2023-05-24
Veeam Backup for Microsoft 365 7 P20230421	7.0.0.3007	12.0.0.3007	2023-04-25
Veeam Backup for Microsoft 365 7 P20230302	7.0.0.2914	12.0.0.2914	2023-03-09
Veeam Backup for Microsoft 365 7	7.0.0.2911	12.0.0.2911	2023-02-28	PDF
*Veeam Backup for Microsoft 365* 6 Releases**
Veeam Backup for Microsoft 365 6a P20230322	6.1.0.1015	11.2.0.1015	2023-03-28	KB4347
Veeam Backup for Microsoft 365 6a P20221215	6.1.0.438	11.2.0.438	2022-12-20
Veeam Backup for Microsoft 365 6a P20220926	6.1.0.423	11.2.0.423	2022-10-06
Veeam Backup for Microsoft 365 6a P20220825	6.1.0.254	11.2.0.254	2022-08-25
Veeam Backup for Microsoft 365 6a	6.1.0.222	11.2.0.222	2022-08-10	PDF KB4344
Veeam Backup for Microsoft 365 6 P20220718	6.0.0.400	11.1.0.400	2022-07-27	KB4285
Veeam Backup for Microsoft 365 6 P20220524	6.0.0.385	11.1.0.385	2022-05-31
Veeam Backup for Microsoft 365 6 P20220413	6.0.0.379	11.1.0.379	2022-05-05
Veeam Backup for Microsoft 365 6 GA	6.0.0.367	11.1.0.367	2022-03-09	PDF KB4286
*Veeam Backup for Microsoft Office 365* 5 Releases**
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4278	5.0.3.1063	10.0.5.1063	2022-02-08	KB4278
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4270	5.0.3.1060	10.0.5.1060	2022-01-10	KB4270
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4235	5.0.3.1051	10.0.5.1051	2021-12-16	KB4235
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4222	5.0.3.1035	10.0.5.1035	2021-10-22	KB4222
Veeam Backup for Microsoft Office 365 5d	5.0.3.1033	10.0.5.1033	2021-09-22	PDF KB4203
Veeam Backup for Microsoft Office 365 5c Cumulative Patch KB4187	5.0.2.42	10.0.4.42	2021-09-01	KB4187
Veeam Backup for Microsoft Office 365 5c	5.0.2.22	10.0.4.22	2021-06-28	KB4181
Veeam Backup for Microsoft Office 365 5b Cumulative Patch KB4158	5.0.1.252	10.0.3.252	2021-05-31	KB4158
Veeam Backup for Microsoft Office 365 5b Cumulative Patch KB4135	5.0.1.225	10.0.3.225	2021-04-12	KB4135
Veeam Backup for Microsoft Office 365 5b Cumulative Patch KB4124	5.0.1.207	10.0.3.207	2021-03-12	KB4124
Veeam Backup for Microsoft Office 365 5b	5.0.1.179	10.0.3.179	2021-02-08	PDF KB4092
Veeam Backup for Microsoft Office 365 5a	5.0.0.1070	10.0.2.1070	2020-12-14	PDF KB4082
Veeam Backup for Microsoft Office 365 5 Day 0 Update	5.0.0.1063	10.0.2.1063	2020-12-04	PDF
Veeam Backup for Microsoft Office 365 5 GA	5.0.0.1061	10.0.2.1061	2020-12-03	PDF
*Veeam Backup for Microsoft Office 365* 4 Releases**
Veeam Backup for Microsoft Office 365 4c Cumulative Patch KB4099	4.0.1.625	10.0.1.625	2021-02-16	KB4099
Veeam Backup for Microsoft Office 365 4c Cumulative Patch KB4083	4.0.1.612	10.0.1.612	2020-12-24	KB4083
Veeam Backup for Microsoft Office 365 4c Cumulative Patch KB3222	4.0.1.545	10.0.1.545	2020-07-09	KB3222
Veeam Backup for Microsoft Office 365 4c Day 0 Update	4.0.1.531	10.0.1.531	2020-06-16	KB3145
Veeam Backup for Microsoft Office 365 4b Cumulative Patch KB3119	4.0.0.2549	9.6.6.2549	2020-03-31	KB3119
Veeam Backup for Microsoft Office 365 4b	4.0.0.2516	9.6.6.2516	2020-01-31	KB3065
Veeam Backup for Microsoft Office 365 4a Cumulative Patch KB3089	4.0.0.1580	9.6.6.1580	2020-03-10	KB3089
Veeam Backup for Microsoft Office 365 4a	4.0.0.1553	9.6.6.1553	2020-01-21	KB3035
Veeam Backup for Microsoft Office 365 4 GA	4.0.0.1345	9.6.6.1345	2019-11-26	PDF
*Veeam Backup for Microsoft Office 365* 3 Releases**
Veeam Backup for Microsoft Office 365 3 GA	3.0.0.422	9.6.5.422	2019-04-02	PDF
*Veeam Backup for Microsoft Office 365* 2 Releases**
Veeam Backup for Microsoft Office 365 2 Cumulative Patch KB2809	2.0.0.814	9.6.3.814	2018-12-28	KB2809
Veeam Backup for Microsoft Office 365 2 Cumulative Patch KB2765	2.0.0.594	9.6.3.594	2018-09-26	KB2765
Veeam Backup for Microsoft Office 365 2 GA	2.0.0.567	9.6.3.567	2018-07-24	PDF
*Veeam Backup for Microsoft Office 365* 1 Releases**
Veeam Backup for Microsoft Office 365 1.5 GA	1.5.0.1099	9.6.0.1099	2017-10-03	PDF
Veeam Backup for Microsoft Office 365 1 Update 1	1.0.0.912	9.5.0.912	2017-01-20	KB2224 PDF
Veeam Backup for Microsoft Office 365 1 GA	1.0.0.860	9.5.0.860	2016-11-29	PDF

Swipe to show more of the table

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.

Veeam Backup for Microsoft 365 Upgrade Paths

2026-06-29T00:00:00Z

Veeam Backup for Microsoft 365 Upgrade Paths

KB ID:	4098
Product:	Veeam Backup for Microsoft 365 \| 8
Published:	2021-02-09
Last Modified:	2026-06-29

Shared Server with Veeam Backup & Replication

If Veeam Backup & Replication is installed on the same server as Veeam Backup for Microsoft 365, upgrade Veeam Backup for Microsoft 365 before upgrading Veeam Backup & Replication.

Shared Server Compatibility of Veeam Backup for Microsoft 365 and Veeam Backup & Replication

Purpose

This article documents the upgrade path to be taken to get to the most recent version of Veeam Backup for Microsoft 365.

Solution

Consider the following when planning for an upgrade:

All backup jobs are stopped during the upgrade process.
After the upgrade, backup jobs settings and global configuration options (e.g., notifications and file exclusions) will be preserved.
After the upgrade, Repositories, Proxy Servers, and Proxy Pools may require manual interaction to upgrade.
Veeam Explorers must be upgraded along with Veeam Backup for Microsoft 365.

End of Support Upgrade Path

If you are using a version of Veeam Backup for Microsoft 365 (VB365) that has reached its End of Support (EOS) and cannot be directly upgraded to a supported version, you will need to install a new instance of VB365 using the latest VB365 version.

Clarification: If the Upgrade Instructions in the User Guide for a currently supported version of VB365 include an upgrade path from an older, unsupported version, this upgrade pathway is still considered supported. This article provides details on upgrade processes for such situations, provided that a currently supported version of VB365 supports a direct upgrade from these older versions.

For example:

When VB365 versions 7 and 7a were supported, they provided an upgrade path from VB365 versions 5 and 6. However, VB365 version 8 does not support upgrading directly from those versions. As a result, after VB365 versions 7 and 7a reached EOS, the upgrade paths for VB365 versions 5 and 6 were removed from this document.
VB365 version 8.4, which is currently supported, allows upgrading directly from VB365 versions 7 and 7a. Thus, although VB365 7 and 7a are no longer supported themselves, the upgrade details for 7 and 7a are included in this document because an upgrade to VB365 8.4 from those versions is officially supported.

7 to 8.5

Path: 7 (7.0.x) → 8.4 → 8.5

7a to 8.5

Path: 7a (7.1.x) → 8.4 → 8.5

8.0 to 8.5

Path: 8.0 (8.0.x) → 8.5

Upgrade to Veeam Backup for Microsoft 365 8.5

8.1 to 8.5

Path: 8.1 (8.1.x) → 8.5

Upgrade to Veeam Backup for Microsoft 365 8.5

8.2 to 8.5

Path: 8.2 (8.2.x) → 8.5

Upgrade to Veeam Backup for Microsoft 365 8.5

8.3 to 8.5

Path: 8.3 (8.3.x) → 8.5

Upgrade to Veeam Backup for Microsoft 365 8.5

8.4 to 8.5

Path: 8.4 (8.4.x) → 8.5

Upgrade to Veeam Backup for Microsoft 365 8.5

What You Do After Upgrade

After upgrading Veeam Backup for Microsoft 365, be sure to review the "What You Do After Upgrade" section of the user guide.

More Information

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.

Restore to AWS EC2 Fails with: "ClientError: Unknown OS / Missing OS files" or "FirstBootFailure"

2026-06-25T00:00:00Z

Restore to AWS EC2 Fails with: "ClientError: Unknown OS / Missing OS files" or "FirstBootFailure"

KB ID:	4814
Product:	Veeam Backup & Replication \| 12.3 \| 12.3.1 \| 12.3.2 \| 13
Published:	2026-01-21
Last Modified:	2026-06-25

Challenge

When restoring a VM to AWS EC2, one of the following errors occurs:

StatusMessage: "CLIENT_ERROR : ClientError: Unknown OS / Missing OS files."

Failed to import machine to Amazon EC2: CLIENT_ERROR : FirstBootFailure: This import request failed because the instance failed to boot and establish network connectivity.

Cause

This issue occurs because Amazon recently began encrypting disks upon creation, resulting in new disks containing random data rather than zeros. When restoring to EC2 using the helper appliance, Veeam Backup & Replication restores backup data onto those disks, which are then sent for AWS import. However, since the disks contain extraneous random data in addition to the restored data, the AWS import process may fail to correctly identify boot partitions for certain guest operating systems, resulting in the reported errors.

Solution

Direct recovery to AWS EC2 without using the helper appliance works successfully and does not encounter this issue.

Note: This issue does not affect the restore of AWS EC2-native VMs. For those EC2-native VMs, it is recommended to use the helper appliance.

For Veeam Backup & Replication 13.0.x

In Veeam Backup & Replication 13.0.x (e.g., 13.0 and 13.0.1), disable the option "Use the helper appliance" in the restore wizard.

Reference: Restoring to Amazon EC2 > Step 8. Configure Helper Appliance

Note: A solution to resolve the root issue will be included in a future Veeam Backup & Replication release.

For Veeam Backup & Replication 12.3.x

In Veeam Backup & Replication v12.3.x (e.g., 12.3, 12.3.1, and 12.3.2), the option for "Use the helper appliance" during the restore process is greyed out and cannot be disabled. To make the option selectable, create the following registry value on the Veeam Backup Server. After configuring the registry value, the “Use helper appliance” option should be disabled when restoring non-AWS EC2-native VMs to AWS EC2.

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: PublicCloudRestoreEnableApplianceSelection
Value Type: DWORD (32-Bit) Value
Value Data: 1

Note: The Veeam Backup & Replication Console must be closed and reopened for the setting to take effect.

PowerShell command to set registry value:

New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam Backup and Replication\' -Name 'PublicCloudRestoreEnableApplianceSelection' -Value "1" -PropertyType DWORD -Force
                     
                    

If the Helper Appliance Cannot Be Avoided

Restoring without the helper appliance, as described above, is the recommended approach. When restoring without the helper appliance is not possible, the AmazonZeroDisksOnRestore registry value can be created to enable a disk pre-zeroing mechanism that allows the restore to complete successfully while the helper appliance is used.

Note: The pre-zeroing mechanism significantly increases restore time. The restore can be two to three times slower than a regular data upload.

This registry value is available in Veeam Backup & Replication 12.3.2.4465 and later.

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: AmazonZeroDisksOnRestore
Value Type: DWORD (32-Bit) Value
Value Data: 1

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.

Veeam My Account Portal - MFA Guide

2026-06-23T00:00:00Z

Veeam My Account Portal - MFA Guide

KB ID:	4716
Published:	2025-02-26
Last Modified:	2026-06-24

Updated MFA Requirements

Starting July 7, 2026, logging in to Veeam Data Cloud (cloud.veeam.com) using a Veeam Account will require that the Veeam Account have Multi-Factor Authentication (MFA) enabled.

Please note: if MFA is already enabled on your Veeam Account, no action is required.

When accessing Veeam Data Cloud, customers are prompted to "Choose a sign in method," and when the "Continue with Veeam" option is selected, they are redirected to the Veeam Account login page to authenticate. Access to Veeam Data Cloud using that Veeam Account will require that MFA be enabled. (Customers who utilize the "Continue with Microsoft" option are not impacted by this change.)

For information about enabling MFA, review the Solution section below.

Purpose

This article documents how to enable and manage the Multifactor Authentication (MFA) option available for the Veeam My Account portal login (my.veeam.com).

Solution

The MFA option allows users to enhance the security of their Veeam Account using Time-based One-Time Passwords (TOTP) from authenticator apps.

Below are the most Frequently Asked Questions, click on a question to see more information.

How do I enable MFA for my Veeam Account login?

How to Enable the Firewall Rules Required by Veeam ONE for Event Collection

2026-06-18T00:00:00Z

How to Enable the Firewall Rules Required by Veeam ONE for Event Collection

KB ID:	2696
Product:	Veeam ONE \| 12
Published:	2018-07-30
Last Modified:	2026-06-18

Purpose

This article describes how to enable the Microsoft Windows Firewall rules that Veeam ONE requires to collect event data from monitored Windows servers, such as Hyper-V hosts and Veeam Backup & Replication servers.

Solution

Using Windows Defender Firewall with Advanced Security

On a server with the Desktop Experience, enable the rules using the firewall management console:

Open Windows Defender Firewall with Advanced Security ( wf.msc ).
Select Inbound Rules.
Locate each rule listed below, right-click it, and select Enable Rule.
- Remote Event Log Management (NP-In)
- Remote Event Log Management (RPC)
- Remote Event Log Management (RPC-EPMAP)
- COM+ Network Access (DCOM-In)

Using PowerShell

Alternatively, launch an Administrative PowerShell terminal and run the following commands:

Set-NetFirewallRule -Name 'RemoteEventLogSvc-NP-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'RemoteEventLogSvc-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'RemoteEventLogSvc-RPCSS-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'ComPlusNetworkAccess-DCOM-In' -Enabled True
                     
                    

More Information

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.

Onboarding a Microsoft 365 Organization Fails with: service principal name is already present for the tenant

2026-06-16T00:00:00Z

Onboarding a Microsoft 365 Organization Fails with: service principal name is already present for the tenant

KB ID:	4871
Product:	Veeam Data Cloud for Microsoft 365
Published:	2026-06-16
Last Modified:	2026-06-16

Challenge

When signing in with a device code during onboarding of a Microsoft 365 organization in Veeam Data Cloud for Microsoft 365, the following error occurs:

AADSTS650051: Consent action for Application '' failed due to following error: The  service principal name is already present for the tenant  paramName: ServicePrincipalName, paramValue: , objectType: System.String

Cause

This error occurs when a service principal from a previous onboarding attempt is still present in the customer tenant.

Under normal conditions, onboarding proceeds as follows:

The user signs in with a device code, and a new service principal is created in the customer tenant.
When Connect is clicked, the onboarding process uses that service principal to obtain an authentication token, then deletes the service principal and begins onboarding the organization.

However, if an error occurs during organization onboarding (for example, the account does not have sufficient permissions, or an organization with the same domain already exists), onboarding fails after the service principal has been deleted. If a new device code is then generated and used to sign in again too soon, the onboarding process attempts to create a service principal with the same name as the one from the failed attempt. Because service principal deletion is a soft delete that takes approximately 5 to 15 minutes to complete in Azure, the name remains in the tenant even though the Azure portal no longer displays the service principal. As a result, the error occurs.

Solution

If this error occurs, wait approximately 15 minutes for the soft-deleted service principal to be fully removed, then regenerate the device code and sign in again.

Deleting the Enterprise application will not speed up removal of the soft-deleted service principal and should not be performed.

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.

List of Security Fixes and Improvements in Veeam Kasten for Kubernetes

2026-06-16T00:00:00Z

List of Security Fixes and Improvements in Veeam Kasten for Kubernetes

KB ID:	4825
Product:	Veeam Kasten for Kubernetes \| 7 \| 7.5 \| 8 \| 8.5 Kasten K10 by Veeam \| 3 \| 5 \| 5.5 \| 6 \| 6.5
Published:	2026-03-02
Last Modified:	2026-06-16

Purpose

This article describes all security-related fixes and improvements introduced in each release or update of Veeam Kasten for Kubernetes.

This article aims to provide our customers' security and compliance teams with detailed information on security improvements.

Full product release notes are available here:

Veeam Kasten for Kubernetes — Release Notes

Security Fixes and Improvements

**Veeam Kasten for Kubernetes 8.5.12**

Upgraded to the latest UBI base image to resolve CVE-2026-45186 and CVE-2026-45447
Upgraded to Go 1.26.4 to resolve CVE-2026-42504
Kasten Multi-cluster Permissions: Hardened multi-cluster security by tightening the permissions granted to the impersonation `ClusterRole` on managed secondary clusters and removing sensitive token values from debug logs.

**Veeam Kasten for Kubernetes 8.5.10**

Upgraded to latest UBI base image to resolve CVE-2026-40356 and CVE-2026-4878
Immutability regression in Kasten 8.5.1–8.5.9 (S3 / GCS / Azure)
Newly written backup objects were not stamped with a retain-until date at write time and remained deletable until the Blob Lifecycle Manager applied protection on its next refresh cycle. A user, script, or attacker with bucket delete permissions could permanently delete those objects during this window, potentially rendering the affected restore points unrecoverable.

Mitigation: Configure a bucket-level Default Object Lock retention so the object store stamps new objects at write time, or upgrade to Kasten 8.5.10.

**Veeam Kasten for Kubernetes 8.5.5**

Upgrade to Go 1.26.1 to address CVE-2026-25679 and CVE-2026-27142
Updated the UBI base image to address CVE-2026-4111

**Veeam Kasten for Kubernetes 8.5.3**

Upgrade to Go 1.25.7 to address CVE-2025-61732.

**Veeam Kasten for Kubernetes 8.5.2**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.

**Veeam Kasten for Kubernetes 8.5.1**

Upgrade to Go 1.25.6 to address CVEs:
Updated base image used to build Veeam Kasten container images to pull in latest security updates.

**Veeam Kasten for Kubernetes 8.0.15**

Upgrade to Go 1.25.5 to address CVE-2025-61727 and CVE-2025-61729.
Updated base image used to build Veeam Kasten container images to pull in latest security updates.

**Veeam Kasten for Kubernetes 8.0.14**

Improved logging security for specific block mode datamover upload Pod invocations. It is recommended to upgrade Veeam Kasten to get this fix.

**Veeam Kasten for Kubernetes 8.0.13**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.

**Veeam Kasten for Kubernetes 8.0.11**

Upgrade to Go 1.25.3 to mitigate security vulnerabilities.
Upgrade to golang.org/x/net@v0.46.0 to address CVE-2025-58190 and CVE-2025-47911.
Updated base image used to build Veeam Kasten container images to pull in latest security updates.

**Veeam Kasten for Kubernetes 8.0.10**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.

**Veeam Kasten for Kubernetes 8.0.8**

Upgrade to Go 1.24.7 to mitigate security vulnerabilities.

**Veeam Kasten for Kubernetes 8.0.7**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.

**Veeam Kasten for Kubernetes 8.0.6**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.
Upgrade to Go 1.24.6 to mitigate security vulnerabilities.

**Veeam Kasten for Kubernetes 8.0.5**

Increased the security of the generated backup repository passwords.
Updated base image used to build Veeam Kasten container images to pull in latest security updates.

**Veeam Kasten for Kubernetes 8.0.4**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.
Upgrade to Go 1.24.5 to mitigate security vulnerabilities.

**Veeam Kasten for Kubernetes 8.0.3**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.

**Veeam Kasten for Kubernetes 8.0.2**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.
Upgrade to Go 1.24.4 to mitigate security vulnerabilities.

**Veeam Kasten for Kubernetes 8.0.1**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.
Upgrade to Go 1.24.3 to mitigate CVE-2025-22873.

**Veeam Kasten for Kubernetes 8.0.0**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.5.9**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.
Upgrade to Go 1.23.8 to mitigate CVE-2025-22871.

**Veeam Kasten for Kubernetes 7.5.8**

Updated base image used to build Veeam Kasten container images to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.5.5**

Upgrade to Go 1.23.7 to mitigate security vulnerabilities.

**Veeam Kasten for Kubernetes 7.5.4**

Update K10 services base image to pull in latest security updates.
Updated base image used to build Veeam Kasten container images to pull in latest security updates.
Upgrade to Go 1.23.6 to mitigate security vulnerabilities.

**Veeam Kasten for Kubernetes 7.5.3**

Upgraded Prometheus to chart version v26.1.0 to pull in latest security updates.
Update K10 services base image to pull in latest security updates.
Redacted sensitive information in Kasten logging.

**Veeam Kasten for Kubernetes 7.5.2**

Update K10 services base image to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.5.1**

Basic users are now restricted from viewing application details of applications in other namespaces.
Basic users now require specific permission to view each action type through the Veeam Kasten dashboard.
Update K10 services base image to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.5.0**

Improved algorithm for authentication cookie validation in OIDC mode. All the users will need to re-login.

**Veeam Kasten for Kubernetes 7.0.14**

Update K10 services base image to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.0.13**

Update Grafana version to 8.5.8 to pull in the latest security updates.
Upgraded Prometheus chart version to 25.28.0 to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.0.10**

Update K10 services base image to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.0.9**

Update K10 services base image to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.0.8**

Update K10 services base image to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.0.6**

Fixed critical authentication vulnerability. This upgrade is recommended for all users.

**Veeam Kasten for Kubernetes 7.0.5**

Update K10 services base image to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.0.4**

Upgrade Fluent Bit to mitigate CVE-2024-4323.
Upgrade to Go 1.22.5 to mitigate security vulnerabilities.

**Veeam Kasten for Kubernetes 7.0.2**

Upgrade Python packages to mitigate security vulnerabilities.
Update K10 services base image to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.0.1**

Upgrade to Go 1.22.4 to mitigate security vulnerabilities.
Update K10 services base image to pull in latest security updates.

**Veeam Kasten for Kubernetes 7.0.0**

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.14

Limited the scope of infrastructure credentials to improve security posture.
Upgrade to Go 1.22.3 to mitigate security vulnerabilities.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.13

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.11

Upgraded to Go v1.21.9 to mitigate security vulnerabilities.

Kasten K10 by Veeam 6.5.9

Users are now restricted from listing actions in namespaces without proper authorization. All customers are encouraged to upgrade to get the fix for this issue.

Kasten K10 by Veeam 6.5.7

Upgraded google.golang.org/protobuf to mitigate CVE-2024-24786.
Upgraded to Go v1.21.8 to mitigate security vulnerabilities.
Changes in SecurityContextConstraints resource were made to reflect the latest securityContext updates on K10 workloads.
Explicitly set runAsNonRoot=true, seccompProfile=RuntimeDefault, allowPrivilegeEscalation=false and capabilities.drop=["ALL"] for K10 service containers.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.4

Explicitly set runAsNonRoot=true, seccompProfile=RuntimeDefault, allowPrivilegeEscalation=false and capabilities.drop=["ALL"] for K10 service containers.
Users are now restricted from restoring data without proper authorization. All customers are encouraged to upgrade to get the fix for this issue.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.3

Improve logging to prevent logging of sensitive backup location connection details.

Kasten K10 by Veeam 6.5.2

Upgrade golang.org/x/crypto to mitigate security vulnerability CVE-2023-48795.
Updates dependencies to address security vulnerabilities in 3rd party libraries.

Kasten K10 by Veeam 6.5.1

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.5.0

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.0.10

Upgrade to Go v1.21.3 to mitigate security vulnerabilities.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.0.8

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.0.7

Upgrade to Go 1.20.8 to mitigate security vulnerabilities.

Kasten K10 by Veeam 6.0.5

Upgrade golang.org/x/net to v0.13.0 to mitigate CVE-2023-3978.
Upgrade to Go 1.20.7 to mitigate security vulnerabilities.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 6.0.3

Updates emissary's Go dependencies to address security vulnerabilities.
Upgrade to Go 1.20.6 to mitigate security vulnerabilities.

Kasten K10 by Veeam 6.0.2

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.11

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.9

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.7

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.6

Upgrade to Go 1.19.6 to mitigate security vulnerabilities.

Kasten K10 by Veeam 5.5.5

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.4

Basic users are now restricted from using transforms in RestoreActions.

Kasten K10 by Veeam 5.5.3

It is now possible to prevent basic users from creating ImportActions or RestoreActions. In some multi-tenant environments, these actions should only be available to administrators.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.2

Upgrade to Go 1.19.4 to mitigate security vulnerabilities.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.1

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.5.0

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.0.11

Upgrade Dex image to mitigate security vulnerabilities.
Upgrade to Go 1.19.2 to mitigate security vulnerabilities.

Kasten K10 by Veeam 5.0.9

Update Grafana version to 9.1.5 to pull in the latest security updates.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.0.8

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 5.0.5

Update K10 services base image to pull in latest security updates.
Update Emissary Ingress to 3.1.0 to include latest security updates.

Kasten K10 by Veeam 5.0.3

Upgrade to Go 1.17.12 to include the latest security patches.

Kasten K10 by Veeam 5.0.2

Update K10 services base image to pull in latest security updates.
Update Emissary Ingress (Ambassador) to 3.0.0 to include latest security updates.

Kasten K10 by Veeam 5.0.0

Upgrade to Go 1.17.10 to include the latest security patches.

Kasten K10 by Veeam 4.5.15

Update Grafana version to 8.5.0 to pull in the latest security updates.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.5.13

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.5.12

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.5.11

Update Ambassador to 1.14.3 to include latest security updates.

Kasten K10 by Veeam 4.5.10

Upgrade to Go 1.17.7 to mitigate CVE-2022-23772 and CVE-2022-23806.

Kasten K10 by Veeam 4.5.9

Fix CVE-2021-23017 discovered in the previous nginx versions.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.5.7

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.5.6

Update Grafana version to pull in fix for CVE-2021-43798.

Kasten K10 by Veeam 4.5.2

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.13

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.10

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.9

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.6

Fix proxy requests to secondary clusters to be restricted to the secondary cluster.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.5

Update Go to pull in latest security fixes.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.4

Update Ambassador to 1.13.6 to include latest security updates.
Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 4.0.3

Upgrade golang.org/x/net prevent denial of service (CVE-2021-33194).

Kasten K10 by Veeam 4.0.2

Update K10 services base image to pull in latest security updates.

Kasten K10 by Veeam 3.0.13

Update Ambassador version to pull in security fixes in Envoy 1.15.4

Kasten K10 by Veeam 3.0.1

Mitigate potential crashes caused by malicious certificates.

Kasten K10 by Veeam 2.5.14

Module upgrades to address CVE-2020-14040.
Upgraded Ambassador to incorporate the Envoy 1.14.3 security update.

Kasten K10 by Veeam 2.5.12

When K10 is deployed with OIDC, user-initiated actions (via the API, CLI, or the dashboard) will be attributed to the user instead of the K10 service account.

Kasten K10 by Veeam 2.5.9

Upgraded several JavaScript packages to address recently disclosed CVEs.

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.

How to use SQL Management Studio to Apply SQL-Based Hotfixes to the Veeam ONE Database

2026-06-15T00:00:00Z

How to use SQL Management Studio to Apply SQL-Based Hotfixes to the Veeam ONE Database

KB ID:	4414
Product:	Veeam ONE \| 10 \| 11 \| 12 \| 12.1 \| 12.2 \| 12.3 \| 13
Published:	2023-03-07
Last Modified:	2026-06-15

Purpose

This article documents applying a SQL query script-based hotfix for the Veeam One database.

Solution

Identify the Location of the Veeam ONE Database

If Veeam ONE is installed, open the Veeam ONE Settings Utility to view the current SQL Server settings.
C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

Alternatively, check the following registry values in the following key:
HKLM\SOFTWARE\Veeam\Veeam ONE Monitor\db_config
- host
- db_name

Hotfix Deployment Guide

Disable and Stop all Veeam ONE Services
1. Veeam ONE v13:
  - Veeam Analytics Service
  - Veeam ONE Monitoring Service
  - Veeam ONE Error Reporting Service
  - Veeam ONE Reporting Service
  - Veeam ONE Caching Service
2. Veeam ONE v12:
  - Veeam ONE Monitoring Service
  - Veeam ONE Reporting Service
  - Veeam ONE Error Reporting Service
  - Veeam ONE Agent Service

To automate this, run the following commands in an Administrative Command Prompt.
^{Command prompt is used instead of PowerShell because older versions of PowerShell were unable to set service startup to delayed start.}

For Veeam ONE v13:

net stop VeeamOAS
net stop VeeamDCS
net stop VeeamERS
net stop VeeamRSS
net stop VeeamCHS
sc config VeeamOAS start= disabled
sc config VeeamDCS start= disabled
sc config VeeamERS start= disabled
sc config VeeamRSS start= disabled
sc config VeeamCHS start= disabled
echo Services stopped and startup types set to disabled.
                     
                    

For Veeam ONE v12:

net stop VeeamDCS
net stop VeeamOneAgentSvc
net stop VeeamRSS
net stop VeeamCRS
sc config VeeamDCS start= disabled
sc config VeeamCRS start= disabled
sc config VeeamOneAgentSvc start= disabled
sc config VeeamRSS start= disabled
echo Services stopped and startup types set to disabled.
                     
                    

Download the hotfix provided by the Veeam Technical Support engineer.
Unpack the hotfix archive.
Back up the Veeam ONE database. See KB2356.
Open Microsoft SQL Management Studio and connect to the SQL Instance hosting the Veeam One database.

Note:
- You may need to launch SQL Management Studio using Run as Administrator.
- If the account you signed in to the SQL server does not have permission to access the SQL instance, you may have to use Run as different user to launch SQL Management Studio as a user who has access to the SQL instance.
In Microsoft SQL Management Studio, use the Ctrl+O hotkey to open the hotfix script.

Ensure that the correct database is selected from the drop-down list.

Execute the hotfix query.

Review the results and ensure that the script completes without errors.

Enable the Veeam One services and Start them.
1. Veeam ONE v13:
  - Veeam Analytics Service – set to Automatic (Delayed Start)
  - Veeam ONE Caching Service – set to Automatic
  - Veeam ONE Error Reporting Service – set to Automatic
  - Veeam ONE Monitoring Service – set to Automatic
  - Veeam ONE Reporting Service – set to Automatic (Delayed Start)
2. Veeam ONE v12:
  - Veeam ONE Monitoring Service – set to Automatic
  - Veeam ONE Reporting Service – set to Automatic (Delayed Start)
  - Veeam ONE Error Reporting Service – set to Automatic
  - Veeam ONE Agent Service – set to Automatic (Delayed Start)

To automate this, run the following commands in an Administrative Command Prompt.
^{Command prompt is used instead of PowerShell because older versions of PowerShell could not set service startup to delayed start.}

For Veeam ONE v13:

sc config VeeamOAS start= delayed-auto
sc config VeeamCHS start= auto
sc config VeeamERS start= auto
sc config VeeamDCS start= auto
sc config VeeamRSS start= delayed-auto
net start VeeamERS
net start VeeamDCS
net start VeeamOAS
net start VeeamRSS
net start VeeamCHS
echo Service startup set to default and started.

                     
                    

For Veeam ONE v12:

sc config VeeamDCS start= auto
sc config VeeamCRS start= auto
sc config VeeamOneAgentSvc start= delayed-auto
sc config VeeamRSS start= delayed-auto
net start VeeamCRS
net start VeeamDCS
net start VeeamOneAgentSvc
net start VeeamRSS
echo Service startup set to default and started.
                     
                    

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.

Support Statement — Exchange Web Services (EWS) Deprecation

2026-06-12T00:00:00Z

Support Statement — Exchange Web Services Deprecation

KB ID:	4820
Product:	Veeam Data Cloud for Microsoft 365 Veeam Backup for Microsoft 365
Published:	2026-03-25
Last Modified:	2026-06-18

Challenge

Microsoft has announced the deprecation of Exchange Web Services (EWS) in Exchange Online, with the initial phase-out target of October 1, 2026.

Veeam Backup for Microsoft 365 and Veeam Data Cloud for Microsoft 365 currently leverage EWS for Exchange Online backup functionality.

Note: This article previously stated, "Starting July 1, 2026, Microsoft will begin blocking EWS access for Frontline Worker mailbox types (Kiosk, F1, and F3) as the first enforcement step of the EWS deprecation." However, on June 11, Microsoft updated the blog post titled "Update to EWS Access for Kiosk / Frontline Worker Licensed Users" to change that deadline to October 1, 2026.

Solution

Veeam software that currently uses EWS will be transitioned to the Microsoft Graph API to ensure continued compatibility and data protection capabilities.

As part of this transition, permission changes are required for all Veeam customers protecting Microsoft 365 data.

For Veeam Data Cloud for Microsoft 365 customers, the application logic will be updated in the service. Performing app reauthorization will assign the permissions necessary.
For Veeam Backup for Microsoft 365, an upcoming release will provide support for the transition from EWS to Microsoft Graph.

Preparing for the October 1, 2026 EWS Retirement

Although EWS remains available today, administrators can prepare now so that backups continue without interruption once EWS access is retired. Complete the applicable steps below for your Veeam product.

**Veeam Data Cloud for Microsoft 365 — Required Action**

To prepare for the retirement of EWS access, a Microsoft 365 Global Admin must reauthorize the Veeam Data Cloud application:

Log in to the Veeam Data Cloud portal.
Go to Settings → Microsoft 365 → Reauthorize Veeam Data Cloud.
Click Reauthorize existing app registration.

**Veeam Backup for Microsoft 365 — Required Action**

To prepare for the retirement of EWS access, add the following Microsoft Graph permissions to the backup app registrations in Microsoft Entra ID.

For Backup Operations

Permission	Type
`User.Read.All`	Application
`MailboxItem.ImportExport.All`	Application
`MailboxItem.Read.All`	Application
`MailboxFolder.ReadWrite.All`	Application

Note: User.Read.All (Application) is already present in your backup app registration if you are protecting SharePoint Online. No action is needed for this permission in that case.

Swipe to show more of the table

For Restore Operations

Permission	Type
`User.Read.All`	Delegated
`MailboxItem.ImportExport`	Delegated
`MailboxItem.Read`	Delegated
`MailboxFolder.ReadWrite`	Delegated

Swipe to show more of the table

What happens if permissions are not added before the EWS deprecation?

Once Microsoft retires EWS access, backups will fail until the required permissions are added. You can add the permissions at any time and backups will resume; however, the first backup afterward will be a full sync backup, and a coverage gap will exist during the period the permissions were missing.

Veeam Backup for Microsoft 365 customers will also need to upgrade to the upcoming release once it becomes available.

More Information

Should you find that EWS has been turned off for your Microsoft 365 organization before the expected Microsoft EWS phase-out date, you can manually configure EWS access with PowerShell (see Control access to EWS in Exchange).

Note: The default value for Get-OrganizationConfig -EwsEnabled is $null. We recommend you set this to Set-OrganizationConfig -EwsEnabled $true until the phase-out period to avoid possible service interruptions.

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.

Build Numbers and Versions of Veeam Plug-ins for Enterprise Applications

2026-06-11T00:00:00Z

Build Numbers and Versions of Veeam Plug-ins for Enterprise Applications

KB ID:	4474
Product:	Veeam Backup & Replication \| 9.5 \| 10 \| 11 \| 12 \| 12.1 \| 12.2 \| 12.3 \| 12.3.1 \| 12.3.2 \| 13
Published:	2023-07-14
Last Modified:	2026-06-11

Plug-In Download

The latest version of all Plug-Ins for Enterprise Applications can be found at the bottom of the My Products page within the My Portal, in the Application Plug-Ins under Additional downloads.

This table lists the Veeam Plug-ins for Enterprise Applications organized by their build number and the corresponding Veeam Backup & Replication version's ISO in which they were packaged.

Note: The table on this tab only displays entries for changes in Plug-ins for Enterprise Applications build numbers. This means that some Veeam Backup & Replication versions may be missing because a plug-in's version did not change between Veeam Backup & Replication releases. If you prefer to view a list of all Veeam Backup & Replication releases and the corresponding Plug-ins for Enterprise Applications packaged with each version, switch to the 'View by Veeam Backup & Replication Release' tab.

Plug-in Build	Veeam Backup & Replication Version	ISO Name ^{⟁The ISO filenames in this list are accurate to the best of our ability. However, please note that there may be discrepancies in cases where a Veeam Backup & Replication version's ISO had to be repackaged, resulting in a change in the date stamp within the filename. It is important to be aware that the Cumulative Patch PYYYYMMDD may not always match the date stamp in the filename.}
Veeam Plug-in for SAP HANA Releases
13.0.3.29	Veeam Backup & Replication 13.0.2	VeeamBackup&Replication_13.0.2.29_20260522.iso
13.0.2.2067	Veeam Backup & Replication 13.0.1 P2	VeeamBackup&Replication_13.0.1.2067_20260310.iso
13.0.1.180	Veeam Backup & Replication 13.0.1	VeeamBackup&Replication_13.0.1.180_20251114.iso
13.0.0.4967	Veeam Backup & Replication 13 (Veeam Software Appliance)	Independent Application Plug-in Download
12.3.2.4854	Veeam Backup & Replication 12.3.2 P3	VeeamBackup&Replication_12.3.2.4854_20260605.iso
12.3.2.4465	Veeam Backup & Replication 12.3.2 P2	VeeamBackup&Replication_12.3.2.4465_20260307.iso
12.3.2.4165	Veeam Backup & Replication 12.3.2 P1	VeeamBackup&Replication_12.3.2.4165_20251006.iso
12.3.1.1139	Veeam Backup & Replication 12.3.1	VeeamBackup&Replication_12.3.1.1139_20250315.iso
12.3.0.310	Veeam Backup & Replication 12.3	VeeamBackup&Replication_12.3.0.310_20241201.iso
12.2.0.334	Veeam Backup & Replication 12.2	VeeamBackup&Replication_12.2.0.334_20240824.iso
12.1.2.172	Veeam Backup & Replication 12.1.2	VeeamBackup&Replication_12.1.2.172_20240515.iso
12.1.0.2131	Veeam Backup & Replication 12.1	VeeamBackup&Replication_12.1.0.2131_20231129.iso
12.0.3.1423	Veeam Backup & Replication 12 P20230718	VeeamBackup&Replication_12.0.0.1420_P20230718.iso
12.0.2.1422	Veeam Backup & Replication 12 P20230412	VeeamBackup&Replication_12.0.0.1420_P20230412_20230606.iso
12.0.0.1420	Veeam Backup & Replication 12 GA	VeeamBackup&Replication_12.0.0.1420_20230209.iso
12.0.0.1402	Veeam Backup & Replication 12 RTM	VeeamBackup&Replication_12.0.0.1402_20230127.iso
11.0.1.1261	Veeam Backup & Replication 11a	VeeamBackup&Replication_11.0.1.1261_20211005.iso
11.0.0.837	Veeam Backup & Replication 11 GA	VeeamBackup&Replication_11.0.0.837_20210220.iso
11.0.0.825	Veeam Backup & Replication 11 RTM	VeeamBackup&Replication_11.0.0.825.iso
10.0.1.4854	Veeam Backup & Replication 10a GA	VeeamBackup&Replication_10.0.1.4854_20200723.iso
10.0.1.4848	Veeam Backup & Replication 10a RTM	VeeamBackup&Replication_10.0.1.4848.iso
10.0.0.4461	Veeam Backup & Replication 10 GA	VeeamBackup&Replication_10.0.0.4461.iso
10.0.0.4442	Veeam Backup & Replication 10 RTM	VeeamBackup&Replication_10.0.0.4442.iso
9.5.4.2866	Veeam Backup & Replication 9.5 U4b	VeeamBackup&Replication_9.5.4.2866.Update4b_20191210.iso
9.5.4.2753	Veeam Backup & Replication 9.5 U4a	VeeamBackup&Replication_9.5.4.2753.Update4a.iso
9.5.4.2615	Veeam Backup & Replication 9.5 U4	VeeamBackup&Replication_9.5.4.2615.Update4.iso
Veeam Plug-in for Oracle RMAN Releases
13.0.3.29	Veeam Backup & Replication 13.0.2	VeeamBackup&Replication_13.0.2.29_20260522.iso
13.0.2.2067	Veeam Backup & Replication 13.0.1 P2	VeeamBackup&Replication_13.0.1.2067_20260310.iso
13.0.1.180	Veeam Backup & Replication 13.0.1	VeeamBackup&Replication_13.0.1.180_20251114.iso
13.0.0.4967	Veeam Backup & Replication 13 (Veeam Software Appliance)	Independent Application Plug-in Download
12.3.2.4854	Veeam Backup & Replication 12.3.2 P3	VeeamBackup&Replication_12.3.2.4854_20260605.iso
12.3.2.4465	Veeam Backup & Replication 12.3.2 P2	VeeamBackup&Replication_12.3.2.4465_20260307.iso
12.3.2.4165	Veeam Backup & Replication 12.3.2 P1	VeeamBackup&Replication_12.3.2.4165_20251006.iso
12.3.1.1139	Veeam Backup & Replication 12.3.1	VeeamBackup&Replication_12.3.1.1139_20250315.iso
12.3.0.310	Veeam Backup & Replication 12.3	VeeamBackup&Replication_12.3.0.310_20241201.iso
12.2.0.334	Veeam Backup & Replication 12.2	VeeamBackup&Replication_12.2.0.334_20240824.iso
12.1.2.172	Veeam Backup & Replication 12.1.2	VeeamBackup&Replication_12.1.2.172_20240515.iso
12.1.0.2131	Veeam Backup & Replication 12.1	VeeamBackup&Replication_12.1.0.2131_20231129.iso
12.0.3.1423	Veeam Backup & Replication 12 P20230718	VeeamBackup&Replication_12.0.0.1420_P20230718.iso
12.0.2.1422	Veeam Backup & Replication 12 P20230412	VeeamBackup&Replication_12.0.0.1420_P20230412_20230606.iso
12.0.0.1420	Veeam Backup & Replication 12 GA	VeeamBackup&Replication_12.0.0.1420_20230209.iso
12.0.0.1402	Veeam Backup & Replication 12 RTM	VeeamBackup&Replication_12.0.0.1402_20230127.iso
11.0.101.1264	Veeam Backup & Replication 11a P20211211	VeeamBackup&Replication_11.0.1.1261_20211211.iso
11.0.100.1261	Veeam Backup & Replication 11a	VeeamBackup&Replication_11.0.1.1261_20211005.iso
11.0.2.839	Veeam Backup & Replication 11 P20210507	VeeamBackup&Replication_11.0.0.837_20210507.iso
11.0.0.837	Veeam Backup & Replication 11 GA	VeeamBackup&Replication_11.0.0.837_20210220.iso
11.0.0.825	Veeam Backup & Replication 11 RTM	VeeamBackup&Replication_11.0.0.825.iso
10.0.3.4856	Veeam Backup & Replication 10a CU 20210609	VeeamBackup&Replication_10.0.1.4854_20210609.iso
10.0.2.4855	Veeam Backup & Replication 10a CU 20201202	VeeamBackup&Replication_10.0.1.4854_20201202.iso
10.0.1.4854	Veeam Backup & Replication 10a GA	VeeamBackup&Replication_10.0.1.4854_20200723.iso
10.0.1.4848	Veeam Backup & Replication 10a RTM	VeeamBackup&Replication_10.0.1.4848.iso
10.0.0.4461	Veeam Backup & Replication 10 GA	VeeamBackup&Replication_10.0.0.4461.iso
10.0.0.4442	Veeam Backup & Replication 10 RTM	VeeamBackup&Replication_10.0.0.4442.iso
9.5.4.2866	Veeam Backup & Replication 9.5 U4b	VeeamBackup&Replication_9.5.4.2866.Update4b_20191210.iso
9.5.4.2753	Veeam Backup & Replication 9.5 U4a	VeeamBackup&Replication_9.5.4.2753.Update4a.iso
9.5.4.2615	Veeam Backup & Replication 9.5 U4	VeeamBackup&Replication_9.5.4.2615.Update4.iso
Veeam Plug-in for SAP on Oracle Releases
13.0.3.29	Veeam Backup & Replication 13.0.2	VeeamBackup&Replication_13.0.2.29_20260522.iso
13.0.2.2067	Veeam Backup & Replication 13.0.1 P2	VeeamBackup&Replication_13.0.1.2067_20260310.iso
13.0.1.180	Veeam Backup & Replication 13.0.1	VeeamBackup&Replication_13.0.1.180_20251114.iso
13.0.0.4967	Veeam Backup & Replication 13 (Veeam Software Appliance)	Independent Application Plug-in Download
12.3.2.4854	Veeam Backup & Replication 12.3.2 P3	VeeamBackup&Replication_12.3.2.4854_20260605.iso
12.3.2.4465	Veeam Backup & Replication 12.3.2 P2	VeeamBackup&Replication_12.3.2.4465_20260307.iso
12.3.2.4165	Veeam Backup & Replication 12.3.2 P1	VeeamBackup&Replication_12.3.2.4165_20251006.iso
12.3.1.1139	Veeam Backup & Replication 12.3.1	VeeamBackup&Replication_12.3.1.1139_20250315.iso
12.3.0.310	Veeam Backup & Replication 12.3	VeeamBackup&Replication_12.3.0.310_20241201.iso
12.2.0.334	Veeam Backup & Replication 12.2	VeeamBackup&Replication_12.2.0.334_20240824.iso
12.1.2.172	Veeam Backup & Replication 12.1.2	VeeamBackup&Replication_12.1.2.172_20240515.iso
12.1.0.2131	Veeam Backup & Replication 12.1	VeeamBackup&Replication_12.1.0.2131_20231129.iso
12.0.3.1423	Veeam Backup & Replication 12 P20230718	VeeamBackup&Replication_12.0.0.1420_P20230718.iso
12.0.2.1422	Veeam Backup & Replication 12 P20230412	VeeamBackup&Replication_12.0.0.1420_P20230412_20230606.iso
12.0.0.1420	Veeam Backup & Replication 12 GA	VeeamBackup&Replication_12.0.0.1420_20230209.iso
12.0.0.1402	Veeam Backup & Replication 12 RTM	VeeamBackup&Replication_12.0.0.1402_20230127.iso
11.0.1.1261	Veeam Backup & Replication 11a	VeeamBackup&Replication_11.0.1.1261_20211005.iso
11.0.0.837	Veeam Backup & Replication 11 GA	VeeamBackup&Replication_11.0.0.837_20210220.iso
11.0.0.825	Veeam Backup & Replication 11 RTM	VeeamBackup&Replication_11.0.0.825.iso
Veeam Plug-in for Microsoft SQL Server Releases
13.0.3.29	Veeam Backup & Replication 13.0.2	VeeamBackup&Replication_13.0.2.29_20260522.iso
13.0.2.2067	Veeam Backup & Replication 13.0.1 P2	VeeamBackup&Replication_13.0.1.2067_20260310.iso
13.0.1.180	Veeam Backup & Replication 13.0.1	VeeamBackup&Replication_13.0.1.180_20251114.iso
13.0.0.4967	Veeam Backup & Replication 13 (Veeam Software Appliance)	Independent Application Plug-in Download
12.3.2.4854	Veeam Backup & Replication 12.3.2 P3	VeeamBackup&Replication_12.3.2.4854_20260605.iso
12.3.2.4465	Veeam Backup & Replication 12.3.2 P2	VeeamBackup&Replication_12.3.2.4465_20260307.iso
12.3.2.4165	Veeam Backup & Replication 12.3.2 P1	VeeamBackup&Replication_12.3.2.4165_20251006.iso
12.3.1.1139	Veeam Backup & Replication 12.3.1	VeeamBackup&Replication_12.3.1.1139_20250315.iso
12.3.0.310	Veeam Backup & Replication 12.3	VeeamBackup&Replication_12.3.0.310_20241201.iso
12.2.0.334	Veeam Backup & Replication 12.2	VeeamBackup&Replication_12.2.0.334_20240824.iso
12.1.2.172	Veeam Backup & Replication 12.1.2	VeeamBackup&Replication_12.1.2.172_20240515.iso
12.1.0.2131	Veeam Backup & Replication 12.1	VeeamBackup&Replication_12.1.0.2131_20231129.iso
12.0.3.1423	Veeam Backup & Replication 12 P20230718	VeeamBackup&Replication_12.0.0.1420_P20230718.iso
12.0.2.1422	Veeam Backup & Replication 12 P20230412	VeeamBackup&Replication_12.0.0.1420_P20230412_20230606.iso
12.0.0.1420	Veeam Backup & Replication 12 GA	VeeamBackup&Replication_12.0.0.1420_20230209.iso
12.0.0.1402	Veeam Backup & Replication 12 RTM	VeeamBackup&Replication_12.0.0.1402_20230127.iso
Veeam Plug-in for IBM Db2 Releases
13.0.3.29	Veeam Backup & Replication 13.0.2	VeeamBackup&Replication_13.0.2.29_20260522.iso
13.0.2.2067	Veeam Backup & Replication 13.0.1 P2	VeeamBackup&Replication_13.0.1.2067_20260310.iso
13.0.1.180	Veeam Backup & Replication 13.0.1	VeeamBackup&Replication_13.0.1.180_20251114.iso
13.0.0.4967	Veeam Backup & Replication 13 (Veeam Software Appliance)	Independent Application Plug-in Download
12.3.2.4854	Veeam Backup & Replication 12.3.2 P3	VeeamBackup&Replication_12.3.2.4854_20260605.iso
12.3.2.4465	Veeam Backup & Replication 12.3.2 P2	VeeamBackup&Replication_12.3.2.4465_20260307.iso
12.3.2.4165	Veeam Backup & Replication 12.3.2 P1	VeeamBackup&Replication_12.3.2.4165_20251006.iso
12.3.1.1139	Veeam Backup & Replication 12.3.1	VeeamBackup&Replication_12.3.1.1139_20250315.iso
12.3.0.310	Veeam Backup & Replication 12.3	VeeamBackup&Replication_12.3.0.310_20241201.iso
12.2.0.334	Veeam Backup & Replication 12.2	VeeamBackup&Replication_12.2.0.334_20240824.iso
12.1.2.172	Veeam Backup & Replication 12.1.2	VeeamBackup&Replication_12.1.2.172_20240515.iso
12.1.0.2131	Veeam Backup & Replication 12.1	VeeamBackup&Replication_12.1.0.2131_20231129.iso

Swipe to show more of the table

This table lists every Veeam Backup & Replication releases that has included Veeam Plug-ins for Enterprise Applications, along with the corresponding versions of those plugins that were included.

Note: The table on this tab may contain redundant entries as plug-in versions do not always change between Veeam Backup & Replication cumulative patch releases. If an entry is not present for a plug-in under a specific version of Veeam Backup & Replication, it indicates that the corresponding plug-in had not been released yet (e.g., Veeam Plug-in for Microsoft SQL was first released with Veeam Backup & Replication 12).

Plug-In Name	Build
Veeam Backup & Replication 13.0.2
Veeam Plug-in for SAP HANA	13.0.3.29
Veeam Plug-in for Oracle RMAN	13.0.3.29
Veeam Plug-in for SAP on Oracle	13.0.3.29
Veeam Plug-in for Microsoft SQL Server	13.0.3.29
Veeam Plug-in for IBM Db2	13.0.3.29
Veeam Backup & Replication 13.0.1 P2
Veeam Plug-in for SAP HANA	13.0.2.2067
Veeam Plug-in for Oracle RMAN	13.0.2.2067
Veeam Plug-in for SAP on Oracle	13.0.2.2067
Veeam Plug-in for Microsoft SQL Server	13.0.2.2067
Veeam Plug-in for IBM Db2	13.0.2.2067
Veeam Backup & Replication 13.0.1
Veeam Plug-in for SAP HANA	13.0.1.180
Veeam Plug-in for Oracle RMAN	13.0.1.180
Veeam Plug-in for SAP on Oracle	13.0.1.180
Veeam Plug-in for Microsoft SQL Server	13.0.1.180
Veeam Plug-in for IBM Db2	13.0.1.180
Veeam Backup & Replication 13.0.0.4967 (Veeam Software Appliance)
Veeam Plug-in for SAP HANA	13.0.0.4967
Veeam Plug-in for Oracle RMAN	13.0.0.4967
Veeam Plug-in for SAP on Oracle	13.0.0.4967
Veeam Plug-in for Microsoft SQL Server	13.0.0.4967
Veeam Plug-in for IBM Db2	13.0.0.4967
Veeam Backup & Replication 12.3.2 P3
Veeam Plug-in for SAP HANA	12.3.2.4854
Veeam Plug-in for Oracle RMAN	12.3.2.4854
Veeam Plug-in for SAP on Oracle	12.3.2.4854
Veeam Plug-in for Microsoft SQL Server	12.3.2.4854
Veeam Plug-in for IBM Db2	12.3.2.4854
Veeam Backup & Replication 12.3.2 P2
Veeam Plug-in for SAP HANA	12.3.2.4465
Veeam Plug-in for Oracle RMAN	12.3.2.4465
Veeam Plug-in for SAP on Oracle	12.3.2.4465
Veeam Plug-in for Microsoft SQL Server	12.3.2.4465
Veeam Plug-in for IBM Db2	12.3.2.4465
Veeam Backup & Replication 12.3.2 P1
Veeam Plug-in for SAP HANA	12.3.2.4165
Veeam Plug-in for Oracle RMAN	12.3.2.4165
Veeam Plug-in for SAP on Oracle	12.3.2.4165
Veeam Plug-in for Microsoft SQL Server	12.3.2.4165
Veeam Plug-in for IBM Db2	12.3.2.4165
Veeam Backup & Replication 12.3.1
Veeam Plug-in for SAP HANA	12.3.1.1139
Veeam Plug-in for Oracle RMAN	12.3.1.1139
Veeam Plug-in for SAP on Oracle	12.3.1.1139
Veeam Plug-in for Microsoft SQL Server	12.3.1.1139
Veeam Plug-in for IBM Db2	12.3.1.1139
Veeam Backup & Replication 12.3
Veeam Plug-in for SAP HANA	12.3.0.310
Veeam Plug-in for Oracle RMAN	12.3.0.310
Veeam Plug-in for SAP on Oracle	12.3.0.310
Veeam Plug-in for Microsoft SQL Server	12.3.0.310
Veeam Plug-in for IBM Db2	12.3.0.310
Veeam Backup & Replication 12.2
Veeam Plug-in for SAP HANA	12.2.0.334
Veeam Plug-in for Oracle RMAN	12.2.0.334
Veeam Plug-in for SAP on Oracle	12.2.0.334
Veeam Plug-in for Microsoft SQL Server	12.2.0.334
Veeam Plug-in for IBM Db2	12.2.0.334
Veeam Backup & Replication 12.1.2
Veeam Plug-in for SAP HANA	12.1.2.172
Veeam Plug-in for Oracle RMAN	12.1.2.172
Veeam Plug-in for SAP on Oracle	12.1.2.172
Veeam Plug-in for Microsoft SQL Server	12.1.2.172
Veeam Plug-in for IBM Db2	12.1.2.172
Veeam Backup & Replication 12.1.1
Veeam Plug-in for SAP HANA	12.1.0.2131
Veeam Plug-in for Oracle RMAN	12.1.0.2131
Veeam Plug-in for SAP on Oracle	12.1.0.2131
Veeam Plug-in for Microsoft SQL Server	12.1.0.2131
Veeam Plug-in for IBM Db2	12.1.0.2131
Veeam Backup & Replication 12.1
Veeam Plug-in for SAP HANA	12.1.0.2131
Veeam Plug-in for Oracle RMAN	12.1.0.2131
Veeam Plug-in for SAP on Oracle	12.1.0.2131
Veeam Plug-in for Microsoft SQL Server	12.1.0.2131
Veeam Plug-in for IBM Db2	12.1.0.2131
Veeam Backup & Replication 12 P20230718
Veeam Plug-in for SAP HANA	12.0.3.1423
Veeam Plug-in for Oracle RMAN	12.0.3.1423
Veeam Plug-in for SAP on Oracle	12.0.3.1423
Veeam Plug-in for Microsoft SQL Server	12.0.3.1423
Veeam Backup & Replication 12 P20230412
Veeam Plug-in for SAP HANA	12.0.2.1422
Veeam Plug-in for Oracle RMAN	12.0.2.1422
Veeam Plug-in for SAP on Oracle	12.0.2.1422
Veeam Plug-in for Microsoft SQL Server	12.0.2.1422
Veeam Backup & Replication 12 P20230223
Veeam Plug-in for SAP HANA	12.0.0.1420
Veeam Plug-in for Oracle RMAN	12.0.0.1420
Veeam Plug-in for SAP on Oracle	12.0.0.1420
Veeam Plug-in for Microsoft SQL Server	12.0.0.1420
Veeam Backup & Replication 12 GA
Veeam Plug-in for SAP HANA	12.0.0.1420
Veeam Plug-in for Oracle RMAN	12.0.0.1420
Veeam Plug-in for SAP on Oracle	12.0.0.1420
Veeam Plug-in for Microsoft SQL Server	12.0.0.1420
Veeam Backup & Replication 12 RTM
Veeam Plug-in for SAP HANA	12.0.0.1402
Veeam Plug-in for Oracle RMAN	12.0.0.1402
Veeam Plug-in for SAP on Oracle	12.0.0.1402
Veeam Plug-in for Microsoft SQL Server	12.0.0.1402
Veeam Backup & Replication 11a P20230227
Veeam Plug-in for SAP HANA	11.0.1.1261
Veeam Plug-in for Oracle RMAN	11.0.101.1264
Veeam Plug-in for SAP on Oracle	11.0.1.1261
Veeam Backup & Replication 11a P20220302
Veeam Plug-in for SAP HANA	11.0.1.1261
Veeam Plug-in for Oracle RMAN	11.0.101.1264
Veeam Plug-in for SAP on Oracle	11.0.1.1261
Veeam Backup & Replication 11a P20211211
Veeam Plug-in for SAP HANA	11.0.1.1261
Veeam Plug-in for Oracle RMAN	11.0.101.1264
Veeam Plug-in for SAP on Oracle	11.0.1.1261
Veeam Backup & Replication 11a
Veeam Plug-in for SAP HANA	11.0.1.1261
Veeam Plug-in for Oracle RMAN	11.0.100.1261
Veeam Plug-in for SAP on Oracle	11.0.1.1261
Veeam Backup & Replication 11 P20210525
Veeam Plug-in for SAP HANA	11.0.0.837
Veeam Plug-in for Oracle RMAN	11.0.2.839
Veeam Plug-in for SAP on Oracle	11.0.0.837
Veeam Backup & Replication 11 P20210507
Veeam Plug-in for SAP HANA	11.0.0.837
Veeam Plug-in for Oracle RMAN	11.0.2.839
Veeam Plug-in for SAP on Oracle	11.0.0.837
Veeam Backup & Replication 11 P20210401
Veeam Plug-in for SAP HANA	11.0.0.837
Veeam Plug-in for Oracle RMAN	11.0.0.837
Veeam Plug-in for SAP on Oracle	11.0.0.837
Veeam Backup & Replication 11 GA
Veeam Plug-in for SAP HANA	11.0.0.837
Veeam Plug-in for Oracle RMAN	11.0.0.837
Veeam Plug-in for SAP on Oracle	11.0.0.837
Veeam Backup & Replication 11 RTM
Veeam Plug-in for SAP HANA	11.0.0.825
Veeam Plug-in for Oracle RMAN	11.0.0.825
Veeam Plug-in for SAP on Oracle	11.0.0.825
Veeam Backup & Replication 10a P20220304
Veeam Plug-in for SAP HANA	10.0.1.4854
Veeam Plug-in for Oracle RMAN	10.0.3.4856
Veeam Backup & Replication 10a CU 20210609
Veeam Plug-in for SAP HANA	10.0.1.4854
Veeam Plug-in for Oracle RMAN	10.0.3.4856
Veeam Backup & Replication 10a CU 20201202
Veeam Plug-in for SAP HANA	10.0.1.4854
Veeam Plug-in for Oracle RMAN	10.0.2.4855
Veeam Backup & Replication 10a GA
Veeam Plug-in for SAP HANA	10.0.1.4854
Veeam Plug-in for Oracle RMAN	10.0.1.4854
Veeam Backup & Replication 10a RTM
Veeam Plug-in for SAP HANA	10.0.1.4848
Veeam Plug-in for Oracle RMAN	10.0.1.4848
Veeam Backup & Replication 10 P2
Veeam Plug-in for SAP HANA	10.0.0.4461
Veeam Plug-in for Oracle RMAN	10.0.0.4461
Veeam Backup & Replication 10 P1
Veeam Plug-in for SAP HANA	10.0.0.4461
Veeam Plug-in for Oracle RMAN	10.0.0.4461
Veeam Backup & Replication 10 GA
Veeam Plug-in for SAP HANA	10.0.0.4461
Veeam Plug-in for Oracle RMAN	10.0.0.4461
Veeam Backup & Replication 10 RTM
Veeam Plug-in for SAP HANA	10.0.0.4442
Veeam Plug-in for Oracle RMAN	10.0.0.4442
Veeam Backup & Replication 9.5 U4b
Veeam Plug-in for SAP HANA	9.5.4.2866
Veeam Plug-in for Oracle RMAN	9.5.4.2866
VBR: 9.5 U4a
Veeam Plug-in for SAP HANA	9.5.4.2753
Veeam Plug-in for Oracle RMAN	9.5.4.2753
Veeam Backup & Replication 9.5 u4
Veeam Plug-in for SAP HANA	9.5.4.2615
Veeam Plug-in for Oracle RMAN	9.5.4.2615

Swipe to show more of the table

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.

How to Collect Guest Processing Log Files

2026-06-11T00:00:00Z

How to Collect Guest Processing Log Files

KB ID:	1789
Product:	Veeam Backup & Replication Veeam Backup for Nutanix AHV Veeam Plug-In for Proxmox VE Veeam Plug-in for Scale Computing HyperCore
Published:	2013-07-08
Last Modified:	2026-06-11
Languages:	JP

Purpose

This article documents how to locate and gather guest-level log files associated with Application-Aware Processing or VM Guest OS File Indexing that occurs with Veeam Backup & Replication VM backup jobs. While investigating issues related to Guest Processing, additional logs must be collected from the Guest OS of the VM that is failing either task.

Note: These logs are NOT automatically captured by the built-in Support Wizard.

Solution

If Application-Aware Processing was disabled during internal troubleshooting, please enable Application-Aware Processing and rerun the job to update the log files within the Guest OS.

Collecting Logs from Windows-based Guest

Guest Logs may be collected either by using the automated PowerShell script in this article or by manually collecting files from within the guest as documented in the Manual Guest Processing Log Collection section below.

Quick Start Automated Guest OS Log Collection

For VM Guests with an active internet connection, open an Administrative PowerShell Terminal in the Guest OS. Run the following script to download the collection script to %temp%, then execute it.

Invoke-WebRequest https://raw.githubusercontent.com/VeeamHub/powershell/master/BR-Collect-GuestLogs/Collect-GuestLogs.ps1 -OutFile $Env:Temp\Collect-GuestLogs.ps1
PowerShell.exe -ExecutionPolicy ByPass -File $env:temp\Collect-GuestLogs.ps1

Automated Guest Log Collection

A PowerShell script has been created by Veeam Support to simplify the Guest OS Log Collection process.

Details regarding this script can be found here: VeeamHUB > BR-Collect-GuestLogs

Manual Guest Processing Log Collection

The following actions are to be performed within the Guest OS of the VM that is being investigated. Please note that no Veeam Backup & Replication task should be running against the guest in question during this collection process, as that will interfere with the accuracy of the information.

Navigate to the folder:
```
%programdata%\Veeam\Backup\
```
Collect files with the following base name:
- VeeamGuestHelper
- VeeamGuestIndexer
- VeeamVixProxy
- VeeamVssSupport
Open an elevated command prompt and run the following commands:

vssadmin list writers > C:\temp\vsswriters.txt
vssadmin list providers > C:\temp\vssproviders.txt
vssadmin list shadows > C:\temp\vssshadows.txt
vssadmin list shadowstorage > C:\temp\vssshadowstorage.txt
                        
                       

For Hyper-V VMs: Export Windows Event Logs from the Guest OS as shown in KB1873.
Bundle the logs collected in steps 2-4 into a compressed file (zip, 7z, or rar), and attach them to your case.

For information about attaching files to a support case, please review KB4162

Collecting Logs from Linux-based Guest

The following action is to be performed within the Guest OS of the VM that is being investigated. Please note that no Veeam Backup & Replication task should be running against the guest in question during this collection process, as that will interfere with the accuracy of the information.

Collect logs from the following directories:

```
/var/log/VeeamBackup/
```
```
/var/log/veeam/
```
```
/tmp/VeeamBackup/
```

Bundle the collected logs into a compressed file (tar.gz, zip, 7z, or rar), and attach them to your case.

For information about attaching files to a support case, please review KB4162

More Information

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.

Vulnerability Resolved in Veeam Backup & Replication 12.3.2.4854

2026-06-09T00:00:00Z

Vulnerability Resolved in Veeam Backup & Replication 12.3.2.4854

KB ID:	4869
Product:	Veeam Backup & Replication \| 12 \| 12.1 \| 12.2 \| 12.3 \| 12.3.1 \| 12.3.2
Published:	2026-06-09
Last Modified:	2026-06-09

All vulnerabilities documented in this article were resolved in Veeam Backup & Replication 12.3.2.4854.

This vulnerability does not affect any version 13.x build of Veeam Backup & Replication due to architectural changes starting in version 13.

Veeam Software Security Commitment

Veeam® is committed to ensuring its products protect customers from potential risks. As part of that commitment, we operate a Vulnerability Disclosure Program (VDP) for all Veeam products and perform extensive internal code audits. When a vulnerability is identified, our team promptly develops a patch to address and mitigate the risk. In line with our dedication to transparency, we publicly disclose the vulnerability and provide detailed mitigation information. This approach ensures that all potentially affected customers can quickly implement the necessary measures to safeguard their systems. It’s important to note that once a vulnerability and its associated patch are disclosed, attackers will likely attempt to reverse-engineer the patch to exploit unpatched deployments of Veeam software. This reality underscores the critical importance of ensuring that all customers use the latest versions of our software and install all updates and patches without delay.

Issue Details

All vulnerabilities disclosed in this article affect Veeam Backup & Replication 12.3.2.4465 and all earlier version 12 builds.

This vulnerability does not affect any version 13.x build of Veeam Backup & Replication due to architectural changes starting in version 13.

^{Note: Unsupported product versions are not tested, but are likely affected and should be considered vulnerable.}

CVE-2026-44963

A vulnerability allowing remote code execution (RCE) on the Backup Server by an authenticated domain user.

Severity: Critical
CVSS v4 Score: 9.4CVSS: AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Source: Reported by Sina Kheirkhah [@SinSinology] of WatchTowr.

Note: This vulnerability only impacts domain-joined backup servers.
^{Veeam Backup & Replication Security Best Practice Guide > Workgroup or Domain?}

Solution

These vulnerabilities were fixed starting with the following build:

Veeam Backup & Replication 12.3.2.4854

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.

Release Information for Veeam Backup & Replication 12.3

2026-06-09T00:00:00Z

Release Information for Veeam Backup & Replication 12.3 and Updates

KB ID:	4696
Product:	Veeam Backup & Replication \| 12.3 \| 12.3.1 \| 12.3.2
Published:	2024-12-03
Last Modified:	2026-06-10

Requirements

You can check the installed build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

Release Information

12.3.2.4854

2026-06-08

Security

Vulnerabilities

CVE-2026-44963 | Severity: Critical (9.4)
A vulnerability allowing remote code execution (RCE) on the Backup Server by an authenticated domain user.

Resolved issues

Veeam Agents

Veeam Agent for Linux 6.3.2.1405
- Added support for RHEL 10.2 and 9.8.
  (Support for these versions previously required a kernel module patch.)

12.3.2.4465

2026-03-12

Security

Vulnerabilities

^{Indicated severity values are CVSS 3.1 scores.}

CVE-2026-21666 | Severity: Critical (9.9)
A vulnerability allowing an authenticated domain user to perform remote code execution (RCE) on the Backup Server.
CVE-2026-21667 | Severity: Critical (9.9)
A vulnerability allowing an authenticated domain user to perform remote code execution (RCE) on the Backup Server.
CVE-2026-21668 | Severity: High (8.8)
A vulnerability allowing an authenticated domain user to bypass restrictions and manipulate arbitrary files on a Backup Repository.
CVE-2026-21672 | Severity: High (8.8)
A vulnerability allowing local privilege escalation on Windows-based Veeam Backup & Replication servers.
CVE-2026-21708 | Severity: Critical (9.9)
A vulnerability allowing a Backup Viewer to perform remote code execution (RCE) as the postgres user.

Fixes and Improvements

Decode-uri-component upgraded to version 0.2.2
Newtonsoft.Json upgraded to version 13.0.3
Path-to-RegExp upgraded to version 1.9.0

Resolved issues

General

When updating RHEL infrastructure servers with the DISA STIG profile enabled, the public GPG key used to validate Veeam packages will be updated as well.
To ensure a smooth update for these systems, it's recommended to temporarily disable the fapolicyd service (if it's in use) during the update.

Enterprise Manager

PostgreSQL item restore initiated from Enterprise Manager fails due to a deserialization error.

Restore to Microsoft Azure

Restoring a Windows-based machine to Microsoft Azure may result in a non-bootable VM. The restore session log contains the following warning:
```
vdmount::CVhdMounter::Mount: step = 5, error = 1392: 00000570
```

File-Level Restore

Other OS file-level restore (FLR) mounts may take an excessive amount of time when many preferred networks are configured. To work around this issue, configure the preferred IP address used by the mount server to connect to the backup repository by creating the following registry value on the backup server:

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: FlrMountPreferredIp
Value Type: String Value (REG_SZ)
Value Data:

HPE StoreOnce and Dell Data Domain

Added the GatewaySelectionSkipSameSubnet configuration key to allow skipping gateway selection based on the same subnet, enabling the use of all available gateways in certain environments.
The Move operation can fail for encrypted backups on an HPE StoreOnce repository when moving backups locally to another job using the same repository.
The repository rescan operation can hang when source and target repositories of a backup copy job for HPE StoreOnce repositories containing backup files with identical names are scanned simultaneously.

Tape

Restores from legacy tape backups using wide KAD fail due to hardware decryption failures.
Unstructured data backup‑to‑tape jobs hang due to incorrect resource scheduling, blocking incremental tasks.
Jaguar tape drives report incorrect capacity.

Application Plug-ins

The RMAN plug-in manager does not retry connections to VBR if the network connection is interrupted during the execution of the sbtInfo call.
CPU usage when the RMAN plug-in manager is in an idle state may reach up to 25% on the Solaris platform.
Application plug-in installation may fail with a "no digest" error when using the .rpm package.

Veeam Agents

Veeam Agent for Microsoft Windows 6.3.3.38
- Standalone jobs targeting Veeam Backup & Replication v13 fail after editing job settings with a duplicate policy object error.
Veeam Agent for Linux 6.3.2.1307
- Added support for new Linux distributions in ValPackageIndex.xml, including Debian 13 x64, SLES 15 SP7 (x64, ppc64le), SLES 16 (x64, ppc64le), and OpenSUSE Leap 16.0 x64.

Veeam Agent for Mac 2.3.2.1302
- Attempts to mount SMB repositories on macOS 26 failed due to excessive symbolic link levels.

12.3.2.4165

2025-10-14

Security

Vulnerabilities

^{Indicated severity values are CVSS 3.1 scores.}

Veeam Backup & Replication
Note: The Veeam Software Appliance and upcoming Veeam Backup & Replication v13 software for Microsoft Windows are architecturally not impacted by these types of vulnerabilities.

CVE-2025-48983 | Severity: Critical (9.9)
A vulnerability in the Mount service of Veeam Backup & Replication, which allows for remote code execution (RCE) on the Backup infrastructure hosts by an authenticated domain user.

Note: This vulnerability only impacts domain-joined backup infrastructure servers added to Veeam Backup & Replication v12. Backup infrastructure servers that are not domain-joined are not impacted by this vulnerability.
^{Veeam Backup & Replication Security Best Practice Guide > Workgroup or Domain?}
CVE-2025-48984 | Severity: Critical (9.9)
A vulnerability allowing remote code execution (RCE) on the Backup Server by an authenticated domain user.

Note: This vulnerability only impacts domain-joined Veeam Backup & Replication v12 backup servers. Backup servers that are not domain-joined are not impacted by this vulnerability.
^{Veeam Backup & Replication Security Best Practice Guide > Workgroup or Domain?}

Veeam Agent for Microsoft Windows

CVE-2025-48982 | Severity: High (7.3)
This vulnerability in Veeam Agent for Microsoft Windows allows for Local Privilege Escalation if a system administrator is tricked into restoring a malicious file.

More information: Veeam Agent for Microsoft Windows 6.3.2.1302 Private Fix Deployment Information

12.3.2.3617

2025-06-17

Security

Vulnerabilities

^{Indicated severity values are CVSS 3.1 scores.}

Veeam Backup & Replication

CVE-2025-23121 | Severity: Critical (9.9)
A vulnerability allowing remote code execution (RCE) on the Backup Server by an authenticated domain user.

Note: This vulnerability only impacts domain-joined backup servers.
^{Veeam Backup & Replication Security Best Practice Guide > Workgroup or Domain?}
CVE-2025-24286 | Severity: High (7.2)
A vulnerability allowing an authenticated user with the Backup Operator role to modify backup jobs, which could execute arbitrary code.

Veeam Agent for Microsoft Windows

CVE-2025-24287 | Severity: Medium (6.1)
A vulnerability allowing local system users to modify directory contents, allowing for arbitrary code execution on the local system with elevated permissions.

New features and enhancements

Platform Support

NSX-T 4.2.2.1 is now fully supported.

Resolved Issues

Malware Detection

Marking malware events as clean fails with a conversion error when the Microsoft SQL Server hosting the configuration database uses the German (DE) locale.

VMware vSphere

In rare circumstances, application-aware image processing may hang during the guest components installation.
Preferred CDP proxy selection in the CDP policy wizard is not respected.
CDP replica VMs may hang during the commit failback operation.

NAS Backup

A specific sequence of events may result in the NAS backup getting in a state where the retention policy may no longer be applied, with the “Removing non-empty container” operation failing.
NAS backup jobs pointed to an HPE StoreOnce repository may occasionally experience execution delays up to 4 hours.

Application Item Recovery

Veeam Explorer for Active Directory: connection to a target domain controller cannot be established if it has SSL enabled.
Veeam Explorer for Microsoft SQL Server: point-in-time recovery of CDC tables to another SQL server is not possible; Veeam Explorer should now use a mount host automatically when the staging server is unavailable.
Veeam Explorer for Oracle: in certain circumstances, the original database files may be removed when restoring to the original location with a different SID and database name.
Veeam Explorer for PostgreSQL: restoring instances to the latest state and the original location may occasionally fail; the instance restore process fails due to the inability to overwrite a data directory that contains mount points.

Object Storage

Retrieving a certificate revocation list (CRL) may fail due to some firewalls blocking non-RFC-compliant GET requests, resulting in the following error:
```
Certificate revocation check failed
Server error 503: Service Unavailable
Failed to download CRL
```
Background checkpoint removal process may lag behind the addition of new data due to poor deletion API call performance on certain on-prem object storage devices, causing continuous backup accumulation. To work around this issue, these API calls will now be called concurrently instead of sequentially.

Tape

Restores from hardware-encrypted tapes fail with the following error:
```
Illegal Request. Invalid field in parameter list.
```
Slow and unresponsive user interface when browsing media pools with a large amount of tape media, and when thousands of media pools are present.
File-to-Tape jobs may fail to process shares containing large files with the following error:
```
Failed to Unload a Previous Scenario. Old Scenario: ScenarioType: ENasToTape (23).
```
Backup to Tape fails to process NetApp NFS3 share occasionally due to a race condition in the caching mechanism, with the following error:
```
Unable to find ObjectVersion in cache for the file.
```

Veeam Agent for Linux

Addressed compatibility issues with the latest Linux kernel versions, enabling out-of-the-box support for the following distributions:
- Debian 12.10 and 12.11
- Ubuntu 25.04
- Red Hat Enterprise Linux (RHEL) 9.6 and 10.0 (both on x86 and IBM Power)
- Oracle Linux 9.6
- Rocky Linux 9.6 and 10.0
- AlmaLinux 9.6 and 10.0

12.3.1.1139

2025-03-19

Security

Vulnerabilities

^{Indicated severity values are CVSS 3.1 scores.}

Veeam Backup & Replication

CVE-2025-23120 | Severity: Critical (9.9)
A vulnerability allowing remote code execution (RCE) on the Backup Server by an authenticated domain user.

Note: This vulnerability only impacts domain-joined backup servers.
^{Veeam Backup & Replication Security Best Practice Guide > Workgroup or Domain?}

New features and enhancements

Platform Support

VMware vSphere 9.0 readiness based on the pre-release builds. The official support will be confirmed with a full regression testing of the GA build when it becomes available. This article and KB2443 will be updated with a support statement following that.
Update: vSphere 9 is officially supported by this and later Veeam Backup & Replication 12 builds, with a single limitation that 4K native (4Kn) disks are not supported.
NSX-T 4.2.1 is now fully supported.
IBM Db2 plug-in now supports Db2 version 12.1 and SLES 12 SP5.
SAP HANA plug-in now supports SAP HANA 2.0 SPS 08 and SLES 15 SP6 for SAP HANA on IBM Power.

Microsoft Entra ID Backup

Protection of conditional access policies has been backported from the next major release, where it will become available as an option in the user interface. For more information on how to enable this functionality, review this section of the User Guide.
Note: This functionality is only available for Essentials, Advanced, and Premium editions.
License consumption logic was updated to no longer consume licenses for external (guest) users and disabled users. Any licenses associated with previously licensed objects will be released automatically 30 days after installing 12.3.1. Alternatively, you can revoke these licenses immediately using the License Information dialog.

Nutanix AHV

Removed the experimental support designation for malware detection, guest file indexing, and application-aware processing, except database log file shipping, which will still be considered experimental.
Note: The experimental status removal does not retroactively apply to existing 12.3.0 installs and requires updating to 12.3.1 due to the included related bugfix.

Proxmox VE

Updated ProxmoxVE plug-in enables the usage of non-root users to register Proxmox, support for Open vSwitch (OVS) networking, Object Storage API (SOSAPI), Nested Pools for backup jobs scope, and brings further backup performance improvements. For more information, please refer to KB4721.

VMware vSphere

Instant VM Recovery engine improvements deliver a 5x increased number of simultaneous instant VM recoveries: up to 1000 VMs per backup server and up to 200 VMs per vPowerNFS server. The readiness check for VM migration to production storage has also been optimized to improve performance.
Automatically disconnect vPower NFS datastores after Instant VM Recovery sessions are completed, reduce alarms or misleading capacity planning calculations caused by disconnected vPower NFS datastores. To configure, create the following registry value on the backup server:
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: vPowerNFSUnmountDatastore
Value Type: DWORD (32-bit) Value
Value Data: 1

Malware Detection

Custom Internet proxy support has been added for downloading updates to the Veeam Threat Hunter threat signatures. To configure, create the following registry value on the Mount Server:

Key Location: HKLM\ SOFTWARE\Veeam\Veeam Threat Hunter\
Value Name: VTHInternetProxy
Value Type: String Value (REG_SZ)
Value Data: :

Note: The system-wide Internet proxy settings are now also respected; see the Resolved Issues section below.

Object Storage

Automatic bucket creation mode is now used by default for newly created S3-compatible object storage repositories.
Improved object storage compatibility by allowing the backup server to ignore errors caused by S3-compatible object storage using unconventional storage class names. This can be enabled by creating the following registry value on the Veeam Backup Server:

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: S3IgnoreCustomStorageClasses
Value Type: DWORD (32-bit) Value
Value Data: 1

Secondary Storage Integrations

Dell Data Domain DD OS versions 8.2 and 8.3 support added for Data Domain integration as a backup repository.
Microsoft SQL Server plug-in performance improvements when writing to deduplication appliances, thanks to leveraging parallel streams, each using its own VAB file, even when backing up a single database.

Unstructured Data Backup

Metadata captured by the Amazon S3 Metadata service is now included in object storage backups to ensure comprehensive bucket data protection.

Configuration Database

TLS connection support for the PostgreSQL configuration database has been added for improved security when hosting the database on an external server.

Email Notifications

OAuth 2.0 support for nonstandard Azure regions, including the U.S. Government, China, and Germany, is now available for email notifications. To enable this, create the following registry value on the Veeam Backup Server:

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: EmailNotificationMicrosoftCloudInstance
Value Type: String Value (REG_SZ)
Value Data:

Setup

New ISO-based update distribution reduces downtime by accelerating update installation and eliminates the additional disk space requirement on the backup server, which was previously needed for unpacking the update before its installation.
Windows Script Host no longer needs to be temporarily enabled to install product updates.

Veeam Vault

Added automatic upgrade of Veeam Vault V1 backup repositories (shared keys authentication) to V2 (Entra ID authentication) for added security and improved user experience.

API

New REST API capabilities include changing existing password records, rescanning all backup repository types, downloading metadata for Unstructured Data backups, and performing backup deletion.
New PowerShell capabilities include connection to Veeam Vaults, querying, and restoring protected Microsoft Entra ID conditional access policies.

Resolved Issues

Added with ISO's dated 20250331 or later

The install and update ISOs available for 12.3.1 were updated on 2025-03-31 to include a hotfix that resolves the following critical issues:

Microsoft's deprecation of Basic SKU Public IP Addresses prevents the creation of Azure appliances.
SQL restore points do not appear if Veeam Explorer for Microsoft SQL is launched via the ribbon after the upgrade to v12.3.1.
Archival Jobs logs have numerous 'SourceStorageKeysPreparer' entries, and the job throws the error:
```
Array dimensions exceeded supported range
```

General

When deleting backups from disk, the backup console should no longer require a decryption password to be provided for encrypted backups.
Backups in legacy per-VM backup file format should no longer disappear from the Backups > Disk node, preventing you from initiating backup metadata format upgrade.

Proxmox VE

OS type of VMs restored from backups of other hypervisors is erroneously set as Other.
Backups of powered-off VMs with PCIe passthrough devices fail due to an attempt to back up those devices.
Backup of VMs that are linked clones is not supported and will now correctly fail instead of processing only the base disk without capturing delta.

Nutanix AHV

The job scheduler should no longer suspend the initiation of scheduled backup jobs in certain circumstances.
Scheduled or manual active full protection domain backup jobs should no longer create incremental rather than full VM restore points.
Prism Central category-based exclusions can now be set for jobs using cluster as a backup scope.
Nutanix Guest Tools quiescence advanced job settings are not properly communicated to Nutanix clusters during backup jobs.
In rare circumstances, retention policy processing may delete some restore points preemptively.

Agent Management

Backup agents fail to perform retention processing for backups located on SOBR Capacity Tier extents after the backup chain has been evacuated from a Performance Tier extents running in a direct connection mode.
Veeam Agent for Windows Recovery Media created from Microsoft Windows Server 2025 or Microsoft Windows 11 24H2 machines in certain configuration states, fails to boot.

Malware detection

Veeam Threat Hunter signature update process ignores the system-wide Internet proxy settings and may experience intermittent interruptions due to not retrying unexpected HTTP errors.
Indicators of compromise detection remains enabled even if the parent File system activity analysis checkbox is cleared.

Object Storage

Entire VM restore from scale-out repository Archive Tier may fail for encrypted backups with the error:
```
Master key not found for keyset
```
Restoring from a backup that has been retrieved from the scale-out repository Archive Tier may fail with the error:
```
Agent failed to process method {DataTransfer.RestoreText}
```
Reverting Archive Tier to previous checkpoints using the corresponding PowerShell cmdlet is not possible after a scale-out repository has been recreated.
In certain circumstances, if the initial archiving session fails, all subsequent archiving sessions will fail with the error:
```
Index in DB is not synchronized with archive
```
Continuously interrupting Capacity Tier offload sessions may result in checkpoints being deleted before the corresponding restore point can be stored, resulting in all subsequent offload sessions failing with the error:
```
Index is not synchronized
```
Importing encrypted backup containing duplicate encryption keys from Capacity Tier fails with the error:
```
Failed to import backup: Violation of unique key constraint
```

Tape

Backup to Tape jobs will be interrupted by source File Backup job even when the “Prevent this job from being interrupted by source backup jobs” option is selected.
Backup to Tape jobs may experience performance degradation when processing backups produced by File Backup jobs.
The latest firmware updates for some hardware encryption modules cause recovery failures due to the presence of unrecognizable KAD (Key-Associated Data) descriptors.
Configuration database records are not removed after a tape media is erased, causing unnecessary database size growth.

Cloud Connect

Switch-VBRCloudTenantsQuotaRepositoryToSOBR cmdlet fails to execute for tenants with multiple quotas assigned.

12.3.0.310

2024-12-03

Release Information

Download Information

The installed build number can be found in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

Patch for 12.3.2

This patch, available as an ISO or EXE, is intended ONLY for patching existing deployments of Veeam Backup & Replication 12.3.2 (build 12.3.2.3617, 12.3.2.4165, or 12.3.2.4465). All previous versions, including 12.3.0 and 12.3.1, must use the full ISO in the next section to upgrade.

Note: Both the ISO and EXE contain the same patch. The EXE is smaller because it's a self-extracting archive and installer, but it requires more disk space and takes longer to start installing because it first extracts the patch files. The ISO file is larger, but it can be mounted easily, allowing the patch installation to begin right away since all files are already inside the ISO and don't need to be extracted to a temporary folder.

Update and patch deployment information: Veeam Backup & Replication User Guide: Updating Veeam Backup & Replication

If you use Veeam Backup Enterprise Manager, start the update procedure with this component. Veeam Backup & Replication should be updated after that.

Veeam Backup & Replication embedded installation on a Veeam Recovery Orchestrator server

Veeam Recovery Orchestrator 7.2.1 utilizes an embedded deployment of Veeam Backup & Replication 12.3.2.

Customers are encouraged to update the embedded Veeam Backup & Replication deployment using the patch available in this article.

The latest release of Veeam Recovery Orchestrator (also known as Veeam Data Platform Premium) will deploy an embedded Veeam Backup & Replication already patched to the latest update. However, to update existing deployments, customers should use the Veeam Backup & Replication patch EXE or ISO included in this article.

This patch (ISO/EXE) can only be used to patch build 12.3.2.3617, 12.3.2.4165, or 12.3.2.4465. If an earlier version of Veeam Backup & Replication is installed, the installer will display the message:

This update is not compatible with installed product version.

Download Patch ISO

^{Filename: VeeamBackup&Replication_12.3.2.4854_20260605_patch.iso}

Size: 3.8 GB

MD5: 2CE54FA817CB40950696B8EBA6E68923
SHA1: 0C240337811F1AFDE440CAEF58E5F830C4A1AE77
SHA256: F68AD6D924E5EC27ACA29CA570C9B10A18850EC4D74172D184EB63A06C5B4D49

After downloading the ISO, open the file's properties, select the Unblock option, and click OK. Alternatively, unblock the file using this command:

Unblock-File -Path "C:\Path\to\File\VeeamBackup&Replication_12.3.2.4854_20260605_patch.iso"

Failure to unblock the ISO may cause the patch installation to fail with the error:

Could not load file or assembly 'file:///X:\Setup\ServiceOperation.dll' or one of its dependencies. Operation is not supported.

download Patch EXE

^{Filename: VeeamBackup&Replication_12.3.2.4854_20260605_patch.zip}

Size: 1.7 GB

MD5: F7DF9F0424E1A3D85E59DF075068A9E7
SHA1: D799134098D69F3AC8A0D6FDF309464E1CE66584
SHA256: 88DE3CF0C4E6AC3D2F4F84F8B3B3A23B905F08F07242CC2DA7A77B68FDC04635

Upgrading to 12.3.2.4854 From a Previous Version

Note: Existing Veeam Backup & Replication deployments running 12.3.2.3617, 12.3.2.4165, or 12.3.2.4465 can use the smaller patch file above to update.

Use the following ISO for:

New deployments of Veeam Backup & Replication 12.3.2.4854.
Upgrading existing deployments of Veeam Backup & Replication (11a, 12, 12.1, 12.2, 12.3.0, or 12.3.1) to 12.3.2.4854.

Remember to always review the Upgrade Checklist as part of your upgrade process.

DOWNLOAD latest 12.3.2 ISO

See the Previous Versions Download Page for ISO hashes.

Reboot May Be Required

Please note that a reboot may be required after installing the update.

Please plan accordingly.

ISO Release History

^{Previously released files are not publicly available for download. Mouse-over or tap the filenames in the table to view a file's MD5 and SHA1 checksum.}

Release Date	ISO Filename	Changelog
Veeam Backup & Replication 12.3.2.4854 Releases
2026-06-09	VeeamBackup&Replication_12.3.2.4854_20260605.iso^{MD5: 58479AA9246D7F8DF6566380CAB5A806 SHA1: A46E8466D0BBECB6938964B66D43AE4900ACBC37}	Initial Release
Veeam Backup & Replication 12.3.2.4465 Releases
2026-03-12	VeeamBackup&Replication_12.3.2.4465_20260307.iso^{MD5: 7E83F84C7290AC4AC455B46AEAED4DB9 SHA1: CB436F76D6BC7B597C61CB1C80EAE2F08A419711}	Initial Release
Veeam Backup & Replication 12.3.2.4165 Releases
2025-10-20	VeeamBackup&Replication_12.3.2.4165_20251014.iso^{MD5: 2587BBAD43B5C2B59FAEA8B9CBE575E7 SHA1: 064BF8D47B2307601F21EEB6362EACD08A558C20}	Repack to add the "Update remote components automatically" option to update the installer.
2025-10-14	VeeamBackup&Replication_12.3.2.4165_20251006.iso^{MD5: 524D5B0C36E1038289B9F00EF54B2D2B SHA1: 6113385F8ACB9964B2158009F33166C93342E7AA}	Initial Release
Veeam Backup & Replication 12.3.2.3617 Releases
2025-06-17	VeeamBackup&Replication_12.3.2.3617_20250610.iso^{MD5: 0C6340CCD1F8723F2B4AA08F8A51AB21 SHA1: 8973EC50886953921A5B6A8FAE50E2856A52548E}	Initial Release
Veeam Backup & Replication 12.3.1.1139 Releases
2025-03-31	VeeamBackup&Replication_12.3.1.1139_20250331.iso^{MD5: AEEBD18EAE0BB0257E5682325065F78A SHA1: BB94F8A40EDE5F7E55417E018BFF603903AD243A}	Integrated hotfix from KB4727. Review the updated resolved issues list above for more details.
2025-03-27	VeeamBackup&Replication_12.3.1.1139_20250325.iso^{MD5: D3A026912954F7BB93DE38B618E3E65F SHA1: 74A592F9E792ACF69DBB57A457BF105D83C36EC7}	AWS Plug-In for Veeam Backup & Replication package updated. Microsoft Azure Plug-in for Veeam Backup & Replication package updated.
2025-03-19	VeeamBackup&Replication_12.3.1.1139_20250315.iso^{MD5: 447564A6A740479678C18E33E2296CC8 SHA1: BB94F8A40EDE5F7E55417E018BFF603903AD243A}	Initial Release
Veeam Backup & Replication 12.3.0.310 Releases
2025-02-24	VeeamBackup&Replication_12.3.0.310_20250221.iso^{MD5: 3C33E8D6F7F051EEBC642814EA296721 SHA1: 19693E8C8D7EDDAA828745EA59020D4A9DDF7488}	Google Cloud Plug-In for Veeam Backup & Replication package updated.
2024-12-16	VeeamBackup&Replication_12.3.0.310_20241211.iso^{MD5: 6B075E5910D1E2F47B77562FE8C42E16 SHA1: B7BC52A580BAC04A7ECD5DCFFDBD1C4C2E7E62B4}	The installer now checks if Windows Script Host is disabled. (To prevent the issue documented on KB4698.)
2024-12-03	VeeamBackup&Replication_12.3.0.310_20241201.iso^{MD5: 92B9BA7506E07889DAFFE92DB15D093C SHA1: 972A8A38BBDBE80C0D11284E99586AFDF60DD56D}	Initial Release

Swipe to show more of the table

Updater ISO Release History

^{Previously released files are not publicly available for download. Mouse-over or tap the filenames in the table to view a file's MD5 and SHA1 checksum.}

Release Date	Updater ISO Filename	Changelog
Veeam Backup & Replication 12.3.2.4854 Releases
2026-06-08	VeeamBackup&Replication_12.3.2.4854_20260605_patch.iso^{MD5: 2CE54FA817CB40950696B8EBA6E68923 SHA1: 0C240337811F1AFDE440CAEF58E5F830C4A1AE77}	Initial Release
Veeam Backup & Replication 12.3.2.4465 Releases
2026-03-12	VeeamBackup&Replication_12.3.2.4465_20260307_update.iso^{MD5: 79A021EB343BF7AA55200B61C0FBAE27 SHA1: 954C723B295D777C6E5FD03250DBB22667A73508}	Initial Release
Veeam Backup & Replication 12.3.2.4165 Releases
2025-10-20	VeeamBackup&Replication_12.3.2.4165_20251014_patch.iso^{MD5: 163D5CCDDAD235DDE1AF283FC38A067A SHA1: 829373E5C0DA16BEC2A5360FBD82B9D02AB1B9F0}	Repack to add the "Update remote components automatically" option to the installer.
2025-10-14	VeeamBackup&Replication_12.3.2.4165_20251006_patch.iso^{MD5: 341FD85636D40AC143CE3EBF657D1864 SHA1: 236438FFB285CA0109DD8F62158199E73E947C39}	Initial Release
Veeam Backup & Replication 12.3.2.3617 Releases
2025-06-17	VeeamBackup&Replication_12.3.2.3617_20250610_update.iso^{MD5: 39C794906038C819CCBB5A3A8E9EBFD8 SHA1: 3FEC2A95FB93B69E84852F518BAAFED0FA6D0242}	Initial Release
Veeam Backup & Replication 12.3.1.1139 Releases
2025-03-31	VeeamBackup&Replication_12.3.1.1139_20250331_update.iso^{MD5: 3DB2DA33176E7AA06468EA165D325BDA SHA1: 3DE5E7799B58BFBDF03F413DC486BD9158FDCB7A}	Integrated hotfix from KB4727. Review the updated resolved issues list above for more details.
2025-03-27	VeeamBackup&Replication_12.3.1.1139_20250325_update.iso^{MD5: D54AC4CDB46D9E928C82C4FF73709CF6 SHA1: 8671E78B4FDF4565FC9D90F0400F7B688929CA76}	AWS Plug-In for Veeam Backup & Replication package updated. Microsoft Azure Plug-in for Veeam Backup & Replication package updated.
2025-03-19	VeeamBackup&Replication_12.3.1.1139_20250315_update.iso^{MD5: 70E802E77F3FC109E85F8FA859F31950 SHA1: 308E6AE02474208A08418734598CFBA0E7AF82D0}	Initial Release

Swipe to show more of the table

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.

Veeam Support Knowledge Base

The HTTP request was forbidden with client authentication scheme

The HTTP request was forbidden with client authentication scheme

Challenge

Cause

Solution

Part 1: Set the EwsEnabled Flag at the Tenant (Organization) Level

Part 2: Set the EwsEnabled Flag at the User (Mailbox) Level

Part 3: Wait and Verify Results

More Information

Similar Issue from December 2025

Challenge

Cause

Solution

Release Information for Veeam Backup for Microsoft 365 8.5

Release Information for Veeam Backup for Microsoft 365 8.5

Requirements

Release Information

8.5.0.1014

2026-06-30

New Features and Enhancements

Bug Fixes

General

Backup and Backup Copy

Restore

REST APIs

PowerShell and Data Management

Download Information

How to Identify and Repair Files That Cannot Be Opened After Restore

How to Identify and Repair Files That Cannot Be Opened After Restore

Purpose

Solution

Before You Begin

Repair Procedure

Step 1: Run an Integrity Check

Step 2: Review the Results

Step 3: Scan Repository and Flag Affected Items

Step 4: Run Backup Jobs

Step 5: Review Outcome and Identify Unrecoverable Files

More Information

Email item data export from EWS failed

Email item data export from EWS failed

Challenge

Cause

Solution

Potential Issue With Backing up Sharepoint, Onedrive, Teams Files, and List Attachments

Potential Issue With Backing up Sharepoint, Onedrive, Teams Files, and List Attachments

Challenge

Cause

Solution

Veeam Data Cloud for Microsoft 365

Veeam Backup for Microsoft 365

External Client App (ECA) for Veeam Data Cloud — Adapting to New Salesforce Security Requirements

External Client App (ECA) for Veeam Data Cloud — Adapting to New Salesforce Security Requirements

Support Statement

Summary of Changes to Salesforce Security Protocols

Introducing the External Client App (ECA) for Veeam Data Cloud

Existing Veeam Data Cloud for Salesforce Customers

Additional Security Enhancements for Salesforce Connections

Supported Salesforce Editions

ECA Configuration Considerations

Troubleshooting Deployment of External Client App (ECA) for Veeam Data Cloud

Shared Server Compatibility of Veeam Backup for Microsoft 365 and Veeam Backup & Replication

Shared Server Compatibility of Veeam Backup for Microsoft 365 and Veeam Backup & Replication

Purpose

Solution

Build Numbers and Versions of Veeam Backup for Microsoft 365

Build Numbers and Versions of Veeam Backup for Microsoft 365

Related Articles

Veeam Backup for Microsoft 365 Upgrade Paths

Veeam Backup for Microsoft 365 Upgrade Paths

Purpose

Solution

7 to 8.5

Path: 7 (7.0.x) → 8.4 → 8.5

7a to 8.5

Path: 7a (7.1.x) → 8.4 → 8.5

8.0 to 8.5

Path: 8.0 (8.0.x) → 8.5

8.1 to 8.5

Part 1: Set the `EwsEnabled` Flag at the Tenant (Organization) Level

Part 2: Set the `EwsEnabled` Flag at the User (Mailbox) Level

**Veeam Kasten for Kubernetes 8.5.12**

**Veeam Kasten for Kubernetes 8.5.10**

**Veeam Kasten for Kubernetes 8.5.5**

**Veeam Kasten for Kubernetes 8.5.3**

**Veeam Kasten for Kubernetes 8.5.2**

**Veeam Kasten for Kubernetes 8.5.1**

**Veeam Kasten for Kubernetes 8.0.15**

**Veeam Kasten for Kubernetes 8.0.14**

**Veeam Kasten for Kubernetes 8.0.13**

**Veeam Kasten for Kubernetes 8.0.11**

**Veeam Kasten for Kubernetes 8.0.10**

**Veeam Kasten for Kubernetes 8.0.8**

**Veeam Kasten for Kubernetes 8.0.7**

**Veeam Kasten for Kubernetes 8.0.6**

**Veeam Kasten for Kubernetes 8.0.5**

**Veeam Kasten for Kubernetes 8.0.4**

**Veeam Kasten for Kubernetes 8.0.3**

**Veeam Kasten for Kubernetes 8.0.2**

**Veeam Kasten for Kubernetes 8.0.1**

**Veeam Kasten for Kubernetes 8.0.0**

**Veeam Kasten for Kubernetes 7.5.9**

**Veeam Kasten for Kubernetes 7.5.8**

**Veeam Kasten for Kubernetes 7.5.5**

**Veeam Kasten for Kubernetes 7.5.4**

**Veeam Kasten for Kubernetes 7.5.3**

**Veeam Kasten for Kubernetes 7.5.2**

**Veeam Kasten for Kubernetes 7.5.1**

**Veeam Kasten for Kubernetes 7.5.0**

**Veeam Kasten for Kubernetes 7.0.14**

**Veeam Kasten for Kubernetes 7.0.13**

**Veeam Kasten for Kubernetes 7.0.10**

**Veeam Kasten for Kubernetes 7.0.9**

**Veeam Kasten for Kubernetes 7.0.8**