Veeam Support Knowledge Base

Release Information for Veeam Backup for Microsoft 365 8.4

2026-04-16T00:00:00Z

Release Information for Veeam Backup for Microsoft 365 8.4

KB ID:	4843
Product:	Veeam Backup for Microsoft 365 \| 8.4
Published:	2026-04-16
Last Modified:	2026-04-16

Requirements

This release can be used to:

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

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

Release Information

8.4.0.1457

2026-04-16

Release Notes for Veeam Backup for Microsoft 365 8.4

New Features and Enhancements

Introduced the ability to specify the number of SharePoint file versions to protect. You can choose to protect only the latest versions or the entire file version history when backing up SharePoint sites, OneDrive data, and Teams files. Limiting protection to the latest version reduces throttling risks and improves backup performance. This feature is available via PowerShell and REST APIs. For more details, see KB4816.
The Restore Portal now has an updated look and feel. The interface is cleaner and easier to navigate, with improved visual hierarchy and a more consistent layout throughout. Additionally, the Restore Portal now offers an improved experience for browsing protected user data. Restore operators select the user data to browse and restore—emails, OneDrive, or SharePoint—and choose a restore point to display the data. This flow resolves visibility issues caused by storing different user data types in separate repositories, ensuring a consistent, clear experience.
New built-in data protection reports provide insights into your backed-up OneDrive, SharePoint, and Teams data. All three reports are accessible via REST APIs and available in CSV format.
TLS connections are supported between the Veeam Backup for Microsoft 365 controller, its remote proxies, and PostgreSQL. TLS is enabled by default when you install the product with default settings.
Introduced the ability to specify data locations to protect, addressing legal and compliance requirements of enterprises operating across regions. This functionality is available in the REST APIs at the (GET) and (PUT) /v8/organization/{organizationId}/tenantInformation endpoints.
The ability to add auxiliary backup applications for SharePoint processing is deprecated. For more details, see KB4567 and KB4821.
The (POST) /v8/Organizations/{organizationId}/explore endpoint now accepts the repositoryId parameter to select the repository to read data from.
Log export has been enhanced for improved performance and stability.
Optimized load balancing on proxy pools during restore and export operations.
SharePoint backup performance improved, and throttling risks reduced:
- by optimizing requests to retrieve list properties;
- by fewer requests to SharePoint Online during incremental backups;
- by optimized list processing that improves error handling, affecting change token usage and incremental backups.
Improved SharePoint backup and object storage repository performance by extending asynchronous processing to list content retrieval and file cache operations.
Up to 22% faster saving of Exchange data to object storage during backup.
Introduced a retention retry mechanism to automatically restart retention tasks interrupted by operations such as backup or restore.

Improved performance of the following REST API endpoints:

(GET) v8/RestoreSessions/{sessionId}/organization/sites/{siteId}/lists

(GET) v8/RestoreSessions/{sessionId}/organization/sites/{siteId}/libraries

The "JobCheckItems" parameter has been added to the following REST API endpoints to enable forced skipping of item validation and accelerate execution:

```
(POST) v8/Jobs
```
```
(PUT) v8/Jobs/{jobId}
```
```
(POST) v8/Jobs/{jobId}/SelectedItems
```

(PUT) v8/Jobs/{jobId}/SelectedItems/{itemId}

```
(POST) v8/Jobs/{jobId}/ExcludedItems
```

(PUT) v8/Jobs/{jobId}/ExcludedItems/{itemId}

Added host rollback detection for proxies in a proxy pool to enforce repository synchronization and maintain consistent repository states.

Bug Fixes

General

Some SharePoint, OneDrive, or Teams files or list attachments restored from backups may not open correctly in their associated applications (e.g., Microsoft Word, Excel, PowerPoint, Adobe Acrobat) and display the following common errors:
```
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.
```
For more details, see KB4835
The Veeam Backup for Microsoft 365 console freezes when the user attempts to run the “Support Information” wizard.
Re-attaching an encrypted repository with an incorrect password fails with the error, instead of a clear error message:
```
Sequence contains no elements
```
A proxy service processing SharePoint data with numerous metadata fields can exhaust all CPU and RAM resources and crash.
An object storage repository linked to a proxy pool may unexpectedly enter an Out of sync or Invalid state.
Object storage repository synchronization fails under certain conditions with the error:
```
SqlState: 21000. ON CONFLICT DO UPDATE command cannot affect row a second time.
```
After restarting the Veeam Backup for Microsoft 365 services or upgrading Veeam Backup for Microsoft 365, some proxies may enter an error state with:
```
Padding is invalid and cannot be removed
```
Restore points from a repository may remain available after the repository is deleted.

Backup and Backup Copy

A long-running backup job remains in the "Pending operation" state longer than expected after being stopped.

Teams backup job fails when processing channel posts with errors such as:

Object reference not set to an instance of an object

Exception of type 'System.OutOfMemoryException'

A backup copy job fails with the error:

The given key '{value}' was not present in the dictionary.

Exchange backup job runs longer than expected, displaying the following warning in the product logs:
```
Message was not published due to deduplication
```
Incremental SharePoint backup job runs longer than expected, with these errors in product logs:
```
Failed to backup list: {value}. Cannot access a disposed object.
```
Backup jobs may stay in the Running state without processing objects, displaying the error:
```
Failed executing DbCommand
```
Backup job fails to start with the error:
```
Unable to cancel retention session
```
Some SharePoint, OneDrive, and Teams files back up with empty content, even though their content exists in production, and the backup status shows success.

Restore

SharePoint restore completes with a warning:

Cannot update field MediaServiceDateTaken

and an error:

The attempted operation is not allowed because it exceeds the list view threshold

Restoring a SharePoint site does not preserve the list's hierarchy.
The list version history is restored incorrectly after restoring a SharePoint site.
Under certain conditions, some subfolders in a public folder mailbox do not appear when exploring a mailbox backup.
‘Notebook’ and ‘Site contents’ page links are not updated after restoring a SharePoint site to a different location.

SharePoint restore fails with the error:

The item does not exist. It may have been deleted by another user.

File and folder structure is not preserved after extracting a saved ZIP file with OneDrive on macOS.

Restoring a SharePoint site to a different location triggers the following warning, even when the URL is unique:

The site was restored with a unique suffix in its URL because the specified alias was already assigned to another site

SharePoint library restore appears successful despite an error occurring during the process:
```
Target list {value} type mismatch
```
Browsing individual folders within a backed-up OneDrive fails with the error:
```
Request failed with status code 400.
```
Some mailboxes may not be available for browsing in Veeam Explorer for Microsoft Exchange.
Restoring many large SharePoint files fails with the error:
```
Exception of type 'System.OutOfMemoryException'
```
Restoring multiple large SharePoint lists may fail with the proxy error:
```
Exception of type 'System.OutOfMemoryException' was thrown.
```
OneDrive restore automatically cancels after some processing time.
When a restore operator role manages specific Microsoft 365 groups, changing the scope in the Restore Portal fails with the error:
```
Exception was thrown on the remote side due to serialize method return value: Type
```
When adding a restore operator for an entire organization scope, the user selection dialog shows users and groups from the incorrect organization rather than the one being configured.

OneDrive save operation fails with error:

Database does not exist or was forcibly closed by server.

Restarting the Veeam Backup for Microsoft 365 controller during a restore operation initiated via REST APIs causes the restore session to appear as failed in the UI.

REST APIs

REST API requests to restore session opening exceed expected durations, causing the error:
```
I/O error occurred.
```
The REST API response header lacks the content-length for mailbox folder and item export and save operations.
The (GET) v8/Organizations/{organizationId}/usedRepositories endpoint does not return the used space amount in the repository.
No data restores when using the (POST) v8/RestoreSessions/{sessionId}/organization/mailboxes/restore REST API endpoint with the "recentItemRestorePeriod" parameter.

The "changeditems" and "deleteditems" parameters are ignored when restoring a OneDrive to another location using the following REST API endpoints:

(POST) v8/RestoreSessions/{sessionId}/organization/onedrives/{odId}/copyTo

(POST) v8/RestoreSessions/{sessionId}/organization/onedrives/{odId}/folders/copyTo

(POST) v8/RestoreSessions/{sessionId}/organization/onedrives/{odId}/folders/{odfoldId}/copyTo

Deleted OneDrive items are restored when the "showdeleted" parameter is set to "false" in the (POST) v8/organizations/{orgId}/explore endpoint.

PowerShell and Data Management

Executing the Get-VBOEntityData request fails with the error:
```
An item with the same key has already been added.
```

If the .NET 8 module is missing, running the Export-VboJobLog cmdlet fails with the error:

The term 'Export-VboJobLog' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again

Moving SharePoint backup data to an object storage repository may get stuck.

Download Information

Download VB365 8.4 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 Configure File Version Protection

2026-04-16T00:00:00Z

How to Configure File Version Protection

KB ID:	4816
Product:	Veeam Data Cloud for Microsoft 365 Veeam Backup for Microsoft 365 \| 8.4
Published:	2026-04-01
Last Modified:	2026-04-16

Purpose

This article describes how to configure Veeam Data Cloud for Microsoft 365 and Veeam Backup for Microsoft 365 to protect only the latest version of SharePoint, OneDrive, and Teams files, helping organizations mitigate Microsoft 365 throttling risks, reduce backup processing time, and minimize storage consumption.

Cause

Due to upcoming application throttling enforcement in Microsoft 365 environments (see KB4821), the risk of throttling during SharePoint, OneDrive, and Teams processing is increasing. By default, the earlier versions of Veeam Data Cloud for Microsoft 365 and Veeam Backup for Microsoft 365 protect all available versions of files, which may result in:

Higher processing time per backup job
Increased throttling due to excessive API calls to SharePoint Online

To address this, customers using Veeam Data Cloud for Microsoft 365 and Veeam Backup for Microsoft 365 v8.4 can update their settings to protect only the latest version of each file.

Solution

How File Version Protection Works

Veeam Data Cloud for Microsoft 365 and Veeam Backup for Microsoft 365 8.4 allow for the following options to protect SharePoint, OneDrive, and Teams files:

Latest version [New option] — Only the most recent version of each file is protected.
- If a production file has only major versions, the latest major version is protected.
- If both major and minor versions are present, only the latest version, major or minor, is protected.
- If a production file has only minor versions, the latest minor version is protected.
All versions [Legacy option] — The entire file version history is protected.

Important considerations

When backing up all versions, subsequent jobs process only items that have changed since the last backup. Versions missing from the repository are excluded until that item changes again.
For customers using Veeam Backup for Microsoft 365, after upgrading to v8.4, only the latest file versions will be protected by default for newly added organizations and associated backup jobs. For existing organizations that were protected before the upgrade, the current setting to protect all file versions will remain in place. Veeam strongly recommends changing this setting for those organizations to protect only the latest version.
For customers using Veeam Data Cloud for Microsoft 365, only the latest file versions will be protected by default for newly added tenants and their backup jobs. For existing tenants that were protected before the upgrade, the current setting to protect all file versions will remain. Veeam strongly recommends changing this setting for those organizations to protect only the latest version.

How To Configure Protecting Only The Latest File Version

For Veeam Data Cloud for Microsoft 365

In the tenant management view, navigate to your tenant Settings.
Under Settings, go to Backup Options.
In the Files Protection section, select Latest Version if you want to only protect the latest versions of your SharePoint, OneDrive, and Teams files.

**For Veeam Backup for Microsoft 365 8.4+**

Ensure the environment is running at least Veeam Backup for Microsoft 365 v8.4.

Method 1: Configure version protection mode using the REST API

Use the following to retrieve the current version protection settings:
Replace {organizationId} with your target organization’s GUID.

GET /v8/organizations/{organizationId}/versionBackupOptions
                     
                    

Use the following to set protection to the latest version only:

PUT /v8/organizations/{organizationId}/versionBackupOptions
Content-Type: application/json

{
  "sharePointBackupMode": "Latest"
}
                     
                    

Method 2: Configure version protection mode using PowerShell

The following steps should be performed on the machine where Veeam Backup for Microsoft 365 is installed.

Open and Administrative PowerShell Terminal.
Run the following command to display the current Version Protection mode.
Update the Organization name in quotes at the end of line 1.

$org = Get-VBOOrganization -Name "Your Organization Name"
Get-VBOVersionBackupOptions -Organization $org

Run the following command to set Protection to Latest Version Only:

Set-VBOVersionBackupOptions -Organization $org -SharePointBackupMode Latest
                     
                    

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 Salesforce 3 Cumulative Patches

2026-04-16T00:00:00Z

Release Information for Veeam Backup for Salesforce 3 and Updates

KB ID:	4697
Product:	Veeam Backup for Salesforce \| 3.1.1 \| 3.1.2
Published:	2024-11-27
Last Modified:	2026-04-16

Requirements

Please confirm that you are running Veeam Backup for Salesforce 3 (build 3.1.2.3133) or earlier before upgrading. You can find the currently installed build number in the Configuration > About section.

After the upgrade, the Veeam Backup for Salesforce build number will be 3.2.0.3957.

What's New

Veeam Backup for Salesforce 3.2 (3.2.0.3957)

Release Notes

Improvements

Support for Salesforce API version 66.0.
Data masking template now includes an option to skip masking rules when a field is blank.
Restore enhancement: ability to update Order and OrderItems of an activated order during restore.
Restore UX improvement: enhanced error message for failed automation disablement during restore, including metadata items with the lowest test coverage.
Archival enhancement: archival now continues by skipping root records that were hard-deleted from the target org or missing child records in the backup.
Advanced Configuration: option to fully compare a record with the backup before creating a restore point.
Advanced Configuration: ability to build object hierarchy for restore/archival using text-based keys in addition to standard lookup fields.

Security

Support for new Salesforce security requirements: External Client App is now required to access organizations via API.
Security updates applied to address vulnerabilities identified in third-party libraries.

Resolved Issues

File retention job failure due to Java Heap Space errors when processing millions of ContentVersions simultaneously.
Duplicate value error when restoring PriceBookEntry to another org for non-standard PriceBooks.
Metadata backup failures when backing up picklists with long picklist values.
Inability to re-authorize Salesforce connection after Sandbox refresh.
Record restore failure when using alternative keys containing the “&” character in field values.
Data backup failure with error “reached maximum value of sequence” during metadata change verification (new field detection) before data loading.

Veeam Backup for Salesforce 3.1.2 (3.1.2.3133)

This release includes the following features and improvements:

Support for Salesforce API version 63.0.
PostgreSQL 15.11 is set as the default version during installation.
Support for restoring activated Contract and Order records.
Logic was added to allow the restoration of records with inactive parent BusinessHours.
The case sensitivity of an alternative key configured for record restore is now defined based on the case sensitivity of the corresponding field in Salesforce.
Rules for searching existing records by alternative key have been updated to allow a non-unique “DeveloperName” value for the "RecordType" object.
The default alternative key for User record restore has been changed to the Username field.
Option to deactivate login using local admin credentials if SSO login is enabled.
ContentDocumentLink was not restored during sObject record restore if the corresponding ContentDocument existed in the target org.
Metadata restore: The preview of the Apex class displayed only the “cls-meta.xml” file content, not the “.cls” file.
PriceBookEntry records could be duplicated during restore if several Product2 records of the same Order referenced it.
The product attempted to update the OwnerID of a record with a null value if the User creation failed during restore to another Org.
Access to smtp.office365.com is now allowed for email notification configuration.
An out-of-memory error could occur when upgrading the product with a large git repository from version 2.x to 3.x.
An unmanaged trigger was not deactivated during restoration if a space character was missing between the list of triggering events and the trigger body.
Permissions validation in records restore functionality was not working for the objects "Pricebook2" and "PermissionSetTabSettings".
Backup of Professional Orgs failed due to the required "Author Apex" permission, which is unavailable in such Orgs.

Veeam Backup for Salesforce 3.1.1 (3.1.1.2714)

This release includes the following features and improvements:

Implemented a process to monitor the initiation of jobs, allowing for the termination of any job that fails to start within 5 minutes.
Resolved an issue where the retention job erroneously removed record versions based on the date of the initial backup, rather than the date of subsequent changes. Which resulted in fewer available restore points.
Corrected a problem where the backup job did not display an error message and remained in the "Starting" status when it failed to create a folder in the file storage.
Fixed a failure in metadata backup for Salesforce Professional Edition with the API enabled, which occurred while attempting to back up permissions for a non-existent field.
Addressed an issue where the file backup failed during the attempt to download an embedded image due to a broken link.
Fixed a problem where after adding the missing permissions to read an object, the backup still could not access the object because the metadata was not updated on the product side.
Identified and resolved conflicting indexes caused by migration in the configuration database.
Restore of AccountContactRelation record for organizations that allow a contact to be related to multiple accounts.

Veeam Backup for Salesforce 3.1 P20241210 (3.1.0.2378)

This release includes the following features and improvements:

Ability to run multiple archiving jobs one after another without having to perform backups between them to avoid selecting the same records for archiving.
Updated PostgreSQL version included in the setup by default to 15.10.

Veeam Backup for Salesforce 3.1 (3.1.0.2298)

This release includes the following features and improvements:

Data masking feature that empowers users to safeguard sensitive and personally identifiable information when restoring data to a sandbox
Metadata reload job to start a full backup of metadata
Support of child hierarchy restore for contacts of Salesforce organization with enabled «Person Accounts».
Other improvements in backup, restore, data archival, and usability

Deployment 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.

Build Numbers and Versions of Veeam Backup for Salesforce

2026-04-16T00:00:00Z

Build Numbers and Versions of Veeam Backup for Salesforce

KB ID:	4372
Product:	Veeam Backup for Salesforce \| 1.0 \| 2.0 \| 2.1 \| 3.0 \| 3.1.1 \| 3.1.2
Published:	2022-10-27
Last Modified:	2026-04-16

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

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

Veeam Backup for Salesforce Current Version Download Page

Version	Build Number	Release Date	Release Notes
*Veeam Backup for Salesforce* 3 Releases**
Veeam Backup for Salesforce 3.2	3.2.0.3957	2026-04-16	HTML KB4697
Veeam Backup for Salesforce 3.1.2	3.1.2.3133	2025-07-08	HTML KB4697
Veeam Backup for Salesforce 3.1.1	3.1.1.2714	2025-02-11
Veeam Backup for Salesforce 3.1 P20241210	3.1.0.2378	2024-12-10
Veeam Backup for Salesforce 3.1	3.1.0.2298	2024-11-27
Veeam Backup for Salesforce 3.0	3.0.0.1769	2024-09-18	HTML
*Veeam Backup for Salesforce* 2 Releases**
Veeam Backup for Salesforce 2.1.1	2.1.1.4793	2025-02-11	HTML KB4502
Veeam Backup for Salesforce 2.1	2.1.0.4675	2023-11-27	HTML KB4502
Veeam Backup for Salesforce 2	2.0.0.3955	2023-08-30	HTML
*Veeam Backup for Salesforce* 1 Releases**
Veeam Backup for Salesforce 1 P20230222	1.0.2.1992	2023-02-22	KB4417
Veeam Backup for Salesforce 1	1.0.0.1429	2022-10-27	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.

Build Numbers and Versions of Veeam Backup for Microsoft 365

2026-04-16T00: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 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-04-16

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.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.

How to Deploy Veeam Backup for Salesforce External Client App

2026-04-13T00:00:00Z

How to Deploy Veeam Backup for Salesforce External Client App

KB ID:	4827
Product:	Veeam Backup for Salesforce
Published:	2026-04-13
Last Modified:	2026-04-13

Purpose

This article documents how to create an External Client App (ECA) in Salesforce to integrate with Veeam Backup for Salesforce via Salesforce API. An ECA with proper permissions is required for Veeam Backup for Salesforce to integrate with Salesforce API using the OAuth 2.0 protocol.

Solution

Important Notes

A separate ECA must be created and configured for every Salesforce organization that Veeam Backup for Salesforce connects to.
If a Salesforce sandbox is refreshed, the associated ECA must be recreated.

Create New External Client App

Click Setup in the top-right corner.
Under Apps, expand Apps, and select External Client Apps.
In the External Client App Manager, click New External Client App.

Shown is a shortcut of searching from the first few characters of the page's name, External Client App Manager.

In the New External Client App form that appears, fill in the following:
- Basic Information Section
  - External Client App Name
  - API Name
  - Contact Email
  - Distribution state = Local
- API (Enable OAuth Settings) Section
  - Toggle Enable OAuth Checkbox On
  - App Settings Section
    - Enter Callback URL
      The Callback URL must match the FQDN and/or IP address of the machine where Veeam Backup for Salesforce is installed. Review the Veeam Backup for Salesforce user guide Create External Client App page for more details on identifying what information should be entered into the Callback URL field.
      
      Note: A trailing forward slash must not be included.
    - Add the required OAuth Scopes:
      - Full access (full)
      - Access unique user identifiers (openid)
        ^{This scope is only needed if you use}^{Salesforce as an identity provider}^.
      - Perform requests at any time (refresh_token, offline_access)
Click Create.

Add Callback URL to IP Restriction List

If access to an Organization is controlled using IP restrictions, be sure to add the Callback URL to the list of allowed IP addresses for the users used to connect to Salesforce and execute backup and restore.

Note that enabling those settings for Salesforce might take some time.
While waiting for the settings to become active, review the Salesforce security settings to ensure that the following option is disabled (unchecked):
Security > Session Settings > Lock sessions to the IP address from which they originated

Copy Token Key and Secret

In the Settings > OAuth Settings, click Consumer Key and Secret.

You'll be prompted to Verify Your Identity.
On the page that loads, copy and save the Consumer Key and Consumer Secret to use later within Veeam Backup for Salesforce.
Note: Connection tokens will not work before the process is complete.

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 History for Veeam Service Provider Console 9

2026-04-09T00:00:00Z

Release History for Veeam Service Provider Console 9

KB ID:	4788
Product:	Veeam Service Provider Console \| 9 \| 9.1 \| 9.2
Published:	2025-10-21
Last Modified:	2026-04-16

Veeam Service Provider Console 9 Builds

9.2.0.33215 (9.2 GA)

Release Information

9.1.0.30713

New Features and Enhancements

General

Veeam Backup & Replication Integration

File-level restore wizards are now available directly in the Veeam Service Provider Console, enabling a seamless user experience and improving operational efficiency.

Scalability and Optimizations

The data collection and processing procedures for managed Veeam Backup & Replication servers have been optimized, improving overall scalability and stability of the backup portal.
The parallel processing of management agent requests to the backup portal has been optimized, improving the overall scalability of the solution.
The Veeam Software Appliance HA handling procedure has been optimized to avoid management agent connection issues.
The management agent database is now automatically compacted when it reaches a certain threshold of free pages, allowing for more efficient use of disk space on the machine where the management agent is installed.

Security

The reset user password functionality has been optimized to further minimize the possibility of user data hijacking.

Alarms

The minimal threshold for PRO-based alarms has been set to 15 minutes to avoid misconfigurations and false-positive occurrences.

Resolved Issues

General

Veeam Cloud Connect servers may be unregistered from the backup portal when multiple data collection errors occur.
Under certain conditions, Veeam Backup Enterprise Managers running on Linux OS cannot be registered in the backup portal.
Under certain conditions, the error "Unexpected error has occurred. Contact the technical support team for assistance." appears when refreshing any page in the VSPC UI.

Security

When logging into the web PowerShell console in the backup portal, the session always runs under the account used by the management agent service (e.g., Local System), not the actual user’s credentials who started the PowerShell session. This allows privilege escalation for any authenticated user.

Deployment

Veeam Service Provider Console cannot be installed on Microsoft Windows 10 22H2.

Upgrade

Under certain conditions, customer job mappings configured for hosted Veeam Backup & Replication servers might be reset after upgrading from VSPC v8.x.
The backup portal malfunctions after upgrade when duplicate records are detected in the stored backup data.
Under certain conditions, after upgrading to VSPC v9.1, the backup portal web UI may be unable to connect to the server.

Alarms

In some situations, RPO-based alarms may be triggered even when there is no actual issue, resulting in false positives.

Management Agent

The The Veeam.AC.Agent.JobManager.exe process consumes CPU resources inefficiently on managed Veeam Backup & Replication servers, resulting in spikes in CPU usage.

Backup Agent

Under certain conditions, backup policies with Cloud Connect repositories fail to be assigned to Veeam Agent for Linux.
After upgrading Veeam Agent for Mac running on a physical machine to v13.0.1 via the backup portal, the agent stops working.
The checkbox "Back up directly from live file system" works inversely in the backup portal for Veeam Agent for Mac backup jobs.
Backup jobs for Veeam Agent for Linux v13.0.1 cannot be edited when the object storage repository is used as the destination target and retention is set to use the number of restore points to keep instead of days.
Under certain conditions, backup policies with Cloud Connect repository can only be targeted to a default repository assigned to a tenant.

Veeam Backup & Replication Integration

Under certain conditions, redirection of backup job creation and restore wizards to managed backup servers fails.
Under certain conditions, patching Veeam Backup & Replication servers v13 fails.
Manual triggering of a full recollection cycle for managed backup servers is not possible.

Veeam Cloud Connect Integration

Under certain conditions, after upgrade, Veeam Cloud Connect tenants may be unmapped from VSPC companies.

Veeam Backup for Public Cloud Integration

Under certain conditions, the procedure for adding existing backup appliances to the backup portal fails when parsing the appliance's security certificate.

Veeam ONE Integration

After upgrading the VSPC server to v9.1, the Alarms Data Collection toggle for managed Veeam ONE servers is switched off.

Notifications

After upgrading to v9.1, incorrect locale settings are used in the date format for email notifications.

Reporting

Orphaned backups from upgraded Veeam Cloud Connect servers are not displayed on the Protected Data page.

Plugins

ConnectWise Manage and Veeam Agent File-Level Restore Portal Web UIs cannot start with:
```
Decoded string is not a valid IDN name. (Parameter 'unicode')
```

REST API

An incorrect value is returned for the parameter "blockSize" in the method: /infrastructure/backupAgents/linux/{backupAgentUid}/jobs/configuration.
REST API v3.4 was reinstated after being removed from the product specification in v9.1; however, this API version is now marked as deprecated, and customers are advised to plan to switch to a higher version of the VSPC REST API.

9.1.0.30636 (9.1 GA)

Release Information

9.1.0.30345 (9.1 RTM)

Release Information

9.0.0.29860

This repack of build 9.0.0.29555 addresses potential upgrade issues and includes most critical fixes discovered at the early availability stage.

Resolved Issues

Upgrade

Under certain conditions, the upgrade process may fail with this error message:
```
The system cannot find the file specified.
```

Data Collection

Under certain conditions, the management agent fails to process data from managed Veeam Backup & Replication servers. This results in high memory consumption by the agent and delays in showing actual data in the Veeam Service Provider Console UI

Licensing

After upgrading to version 9, the backup portal stops pushing the license attribute to managed backup agents.

9.0.0.29555

Release Information

Download Information

Deployment Guidance

New Deployments
Please use the v9.2 ISO.
Upgrading existing VSPC v9.1 Deployments
Please upgrade using the v9.2 ISO.

For 8.1 and 9.0 deployments, please review the notes in the upgrade section of the product user guide.

Deployment ISO

DOWNLOAD latest 9.2 ISO

See the 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.

Build Numbers and Versions of Veeam Service Provider Console

2026-04-09T00:00:00Z

Build Numbers and Versions of Veeam Service Provider Console

KB ID:	4464
Product:	Veeam Service Provider Console \| 4.0 \| 5.0 \| 6.0 \| 7.0 \| 8.0 \| 8.1 \| 9 \| 9.1 \| 9.2 Veeam Availability Console \| 2.0 \| 2.0_U1 \| 3.0
Published:	2023-06-16
Last Modified:	2026-04-09

This KB article lists all versions of Veeam Service Provider Console and their respective build numbers.

For more information on downloading the latest version of Veeam Service Provider Console, visit:

^{Note: Prior to version 4, the product was known as Veeam Availability Console.

Note: Prior to version 2, the product was known as Veeam Managed Backup Portal.}

Version	Build Number	Release Date	Release Notes	Product Guides
Veeam Service Provider Console 9 Releases
Veeam Service Provider Console 9.2	9.2.0.33215	2026-04-09	HTML
Veeam Service Provider Console 9.1 Patch 1	9.1.0.30713	2025-12-05	KB4788
Veeam Service Provider Console 9.1 GA	9.1.0.30636	2025-11-19	HTML
Veeam Service Provider Console 9.1 RTM	9.1.0.30345	2025-11-07	KB4788
Veeam Service Provider Console 9 CP1	9.0.0.29860	2025-10-21	KB4788
Veeam Service Provider Console 9	9.0.0.29555	2025-09-03	HTML	HTML
Veeam Service Provider Console 8 Releases
Veeam Service Provider Console 8.1 CP1	8.1.0.21999	2024-12-03	KB4651	HTML
Veeam Service Provider Console 8.1	8.1.0.21377	2024-08-28	HTML KB4651	HTML
Veeam Service Provider Console 8 CP2	8.0.0.19552	2024-05-28	KB4509	HTML
~~Veeam Service Provider Console 8 CP2~~ (Note)This build was retracted and rereleased as build 8.0.0.19552. For more information review KB4509.	~~8.0.0.19236~~	2024-05-06
Veeam Service Provider Console 8 CP1	8.0.0.18054	2024-03-04
Veeam Service Provider Console 8	8.0.0.16877	2023-12-05	PDF	ZIP
Veeam Service Provider Console 7 Releases
Veeam Service Provider Console 7 P20240516	7.0.0.19551	2024-05-28	KB4441	-
Veeam Service Provider Console 7 P20240412	7.0.0.18899	2024-05-06
Veeam Service Provider Console 7 P20230531	7.0.0.14271	2023-06-05
Veeam Service Provider Console 7 P20230321	7.0.0.13157	2023-03-21
Veeam Service Provider Console 7 GA	7.0.0.12777	2023-01-30	PDF	-
Veeam Service Provider Console 6 Releases
Veeam Service Provider Console 6 Patch 1	6.0.0.8787	2022-02-02	KB4277	-
Veeam Service Provider Console 6 GA	6.0.0.7739	2021-09-27	PDF KB4212	-
Veeam Service Provider Console 5 Releases
Veeam Service Provider Console 5 Patch 4	5.0.0.7151	2021-10-12	KB4223	-
Veeam Service Provider Console 5 Patch 3	5.0.0.6959	2021-05-22	KB4163	-
Veeam Service Provider Console 5 Patch 2	5.0.0.6883	2021-03-25	KB4127	-
Veeam Service Provider Console 5 Patch 1	5.0.0.6838	2021-03-03	KB4116	-
Veeam Service Provider Console 5 GA	5.0.0.6726	2021-02-24	PDF KB4111	-
Veeam Service Provider Console 4 Releases
Veeam Service Provider Console 4 Patch 2	4.0.0.4914	2020-07-23	KB3237	-
Veeam Service Provider Console 4 Patch 1	4.0.0.4911	2020-07-03	KB3211	-
Veeam Service Provider Console 4 GA	4.0.0.4877	2020-03-31	PDF KB3040	-
Veeam Availability Console 3 Releases
Veeam Availability Console 3 Patch 4	3.0.0.2795	2020-01-23	KB3036	-
Veeam Availability Console 3 Patch 3	3.0.0.2762	2019-09-20	KB3003	-
Veeam Availability Console 3 Patch 2	3.0.0.2725	2019-06-17	KB2960	-
Veeam Availability Console 3 Patch 1	3.0.0.2703	2019-04-11	KB2934	-
Veeam Availability Console 3 GA	3.0.0.2647	2019-03-28	PDF	-
Veeam Availability Console 2 Update 1 Releases
Veeam Availability Console 2 U1 Patch 1913	2.0.2.1913	2018-12-21	KB2835	-
Veeam Availability Console 2 U1 Patch 1850	2.0.2.1850	2018-11-15	KB2795	-
Veeam Availability Console 2 U1 Patch 1824	2.0.2.1824	2018-10-05	KB2781	-
Veeam Availability Console 2 U1 Patch 1817	2.0.2.1817	2018-08-30	KB2715	-
Veeam Availability Console 2 U1 Patch 1807	2.0.2.1807	2018-07-30	KB2694	-
Veeam Availability Console 2 U1 GA	2.0.2.1750	2018-06-19	PDF	-
Veeam Availability Console 2 Releases
Veeam Availability Console 2 Cumulative Patch 1376	2.0.1.1376	2017-12-21	KB2418	-
Veeam Availability Console 2 GA	2.0.1.1319	2017-11-14	PDF	-
Veeam Managed Backup Portal 1 Releases
Veeam Managed Backup Portal 1	1.0.0.295	2016-03-24	-	-

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 Configure krb5.conf for Cross-Domain Hyper-V Cluster Management

2026-04-01T00:00:00Z

How to Configure krb5.conf for Cross-Domain Hyper-V Cluster Management

KB ID:	4841
Product:	Veeam Backup & Replication \| 13
Published:	2026-04-01
Last Modified:	2026-04-01

Purpose

This article documents how to configure the /etc/krb5.conf file on the Veeam Software Appliance (VSA) to enable Kerberos authentication when managing a Microsoft Hyper-V cluster whose nodes belong to a different Active Directory domain than the backup server.

As noted in the VBR 13 User Guide — Before You Begin (Hyper-V):

[For Linux-based backup servers] Both the Hyper-V nodes and the backup server must be joined to the same Active Directory domain. If they are not joined to the same Active Directory domain, additional manual configuration of the krb5.conf file is required.

Cause

Linux uses /etc/krb5.conf to determine which Key Distribution Center (KDC) to contact when requesting Kerberos tickets. If the VSA and Hyper-V cluster nodes are in different AD domains and the [realms] section of krb5.conf does not contain entries for those domains, Kerberos authentication will fail when Veeam Backup & Replication attempts to connect to the cluster.

For more information, please reference the krb5.conf documentation.

Solution

Export the existing /etc/krb5.conf file using the Host Configuration file manager.
Edit the downloaded krb.conf file and update the [realms] section to include an entry for each AD domain containing Hyper-V cluster nodes:

Example

[realms]
 EXAMPLE1.COM = {
     kdc = kerberos.example1.com
 }
 EXAMPLE2.COM = {
     kdc = kerberos.example2.com
 }
                     
                    

Replace the following placeholders:

EXAMPLE1.COM, EXAMPLE2.COM — the fully qualified domain names (in uppercase) of the AD domains containing the Hyper-V cluster nodes.
kerberos.example1.com, kerberos.example2.com — the DNS-resolvable hostnames or IP addresses of the KDC servers for the respective domains. By default, the KDC is the domain controller.

Review krb5.conf documentation to determine if the [domain_realm] section or the default_realm option need configured for your environment.
Once the krb5.conf file is updated, use the Import button in the Host Configuration file manager to import it into the VSA.

Note: If the Security Officer role is enabled, the import will require veeamso approval.

More Information

An additional factor that can contribute to KDC lookup failures is that Linux DNS resolution queries only the first three DNS servers listed in /etc/resolv.conf. Critically, Linux falls over to the next DNS server only if the previous one times out or returns a hard failure. DNS server failover will not occur if the DNS lookup returns an NXDOMAIN ("host does not exist") response. If the primary DNS server returns NXDOMAIN for a KDC hostname, the query fails even when other DNS servers could resolve it.

To test DNS resolution, enable SSH on the VSA via the Host Management Console, then SSH into the VSA and test the resolution of each realm's KDC server.

nslookup kerberos.example1.com
nslookup kerberos.example2.com

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.

The HTTP request was forbidden with client authentication scheme

2026-04-01T00: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-04-08

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 level:

Review the EWS enablement status at both the Organization and Mailbox level using the following PowerShell commands:

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

#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

If the output results for either org or mailbox are anything other than an explicit True, access via EWS must be enabled using the following commands:

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

#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

If preferred, mailboxes may be individually modified using the following command:

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

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

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 Fsas ETERNUS Plug-In for Veeam Backup & Replication

2026-04-01T00:00:00Z

Release Information for Fsas ETERNUS Plug-In for Veeam Backup & Replication

KB ID:	4043
Product:	Veeam Backup & Replication \| 12.3 \| 12.3.1 \| 12.3.2 \| 13
Published:	2020-11-06
Last Modified:	2026-04-02

This plug-in leverages the Veeam Universal Storage API, which enables storage OEMs to allow Veeam Backup & Replication integration to the arrays for backup and replication jobs.

Requirements

Before installing Fsas ETERNUS Plug-In v1.3, ensure that you are running Veeam Backup & Replication 12.3.0.310 or higher. You can check the installed build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

ETERNUS Plug-In v1.3 supports integration with the following storage systems:

ETERNUS AF S2 and DX S4 series (except DX8900 S4): V10L88-1000 or later
ETERNUS AF S3 and DX S5 series, DX8900 S4: V11L30-5000 or later
ETERNUS DX S6 series: V12L10-0000 or later

Additional Requirements and Considerations

For Fsas ETERNUS storage systems, a Veeam Storage Integration license must be installed on the storage system. The Veeam Storage Integration license is available free of charge from the Fsas website.
The ETERNUS storage plug-in will not work when the FIPS policy is enabled on the Veeam Backup Server.

What's New

This update is a rebranded version of the Fujitsu Plug-In for Veeam Backup & Replication.

Download Information

DOWNLOAD ETERNUS Plug-In

^{Updated: 2026-04-01}

MD5: C1E25DF14A4D207723A1BCBB43CEA84E
SHA1: 92A180AA590ABBD39D2C3DD31BE6508BDD49BAF7

Previous Versions

Fujitsu Plug-In for Veeam Backup & Replication [1.2.2] 2025-12-02

Updated setup package to enable installation on Veeam Backup & Replication v13.0.1.
Please also install this version if you are unable to remove the earlier plug-in version after upgrading to v13.0.1.

Fujitsu Plug-In for Veeam Backup & Replication [1.1.3] 2024-01-29

This update resolves the most common Storage Cluster configuration support issues.

Fujitsu Plug-In for Veeam Backup & Replication [1.1.3] 2023-02-28

Added support for snapshots on replicated volumes.
Added support for multiple VLAN's.
This update also resolves the most common support issues.

Fujitsu Plug-In for Veeam Backup & Replication [1.0.10] 2019-05-14

Initial plug-in version

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-03-31T00: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-04-16

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 will be automatically updated to the latest version, fixing the issue.

Veeam Backup for Microsoft 365

The issue described in this article was resolved starting in Veeam Backup for Microsoft 365 v8.4 (build 8.4.0.1457). All Veeam Backup for Microsoft 365 customers are advised to upgrade as soon as possible.

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.

Guest processing fails for Nutanix AHV, Proxmox VE, Scale Computing HyperCore

2026-03-31T00:00:00Z

Guest processing fails for Nutanix AHV, Proxmox VE, Scale Computing HyperCore

KB ID:	4842
Product:	Veeam Backup & Replication \| 13 Veeam Backup for Nutanix AHV \| 9 Veeam Plug-In for Proxmox VE \| 3
Published:	2026-03-31
Last Modified:	2026-04-06

Challenge

When running backup or replication jobs for Windows virtual machines hosted on Nutanix AHV, Proxmox VE, or Scale Computing HyperCore with Veeam Backup & Replication 13.0.1 Patch 2, guest processing fails with one of the following errors:

Failed to install guest processing components for [VM name]. Error: Failed to connect to the guest OS.

Failed to prepare guest for hot backup. Error: Cannot start service. Machine: [IP address]. Service: [VeeamGuestHelper]. Cannot start service. Win32 error: The service did not respond to the start or control request in a timely fashion. Code: 1053

Cause

This issue occurs due to an in-guest processing component that may be assigned an invalid port value, preventing it from initializing.

Solution

Potential Conflict with Existing Private Hotfixes

If you have already installed another private hotfix, contact Veeam Support before installing this hotfix to confirm there are no conflicts.

Private hotfixes replace core product files (e.g., .dll and .exe). If multiple private hotfixes modify the same file, installing one can overwrite changes from another and cause unexpected behavior.

For Windows-based Veeam Backup & Replication Deployment

Install the private fix provided below.

Note: This fix applies only to Veeam Backup & Replication build 13.0.1.2067. Verify your build number under Help > About before proceeding.

Ensure no backup, replication, or restore sessions are currently running.
Close Veeam Backup & Replication Console on all machines where it is open.
On the Veeam Backup & Replication server, execute the private fix file as an Administrator.
Follow the on-screen prompts to complete the installation.
Reopen the console and confirm that guest processing completes successfully for the affected VMs.

Download Private Fix

^{Filename: KB4842_20260331_VBR_13.0.1.2067_PF1309581.zip}

MD5: 6CD1901BA27D3AEA60A2D7CA979912DA
SHA1: 1393D67F506D6ABADE2314263A4288109B04205F
SHA256: 6EE196110E96EF50E6F4B7C53A31AC87826272589DADE166F501C9C33A1DB241

For Veeam Software Appliance

Install the private fix provided below.

Note: This fix applies only to Veeam Backup & Replication build 13.0.1.2067. Verify your build number under Help > About before proceeding.

Ensure no backup, replication, or restore sessions are currently running.
Install the private hotfix.
(See Install Private Hotfixes for more information.)
Confirm that guest processing completes successfully for the affected VMs.

Download VSA Private Hotfix

^{Filename: vbr-pf-bundle-1309581-1616154.zip}

MD5: D278805D915E1ACA7E4DAEB6B5FA96F8
SHA1: D2ECE4E443988AE9E586568F1CD559CDEAEE205A
SHA256: 98D649584D01F3215755CA7AA768700D58FDAA049BB245E0E1AB538AADFE1401

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.

Malware and Ransomware Detection in M365

2026-03-31T00:00:00Z

Malware and Ransomware Detection in M365

KB ID:	4838
Product:	Veeam Data Cloud for Microsoft 365
Published:	2026-03-31
Last Modified:	2026-03-31

Availability Requirement

Threat Detection is available to Veeam Data Cloud for Microsoft 365 customers with Premium or Advanced plans. Customers must opt in to AI settings to enable this feature. Contact your Veeam account team or see your plan details to confirm availability.

Supported Workloads

This feature currently supports Microsoft 365 workloads only.

Purpose

This article describes how to locate, review, and interpret Malware and Ransomware threat detections surfaced by Veeam Data Cloud (VDC) Advanced Threat Detection for Microsoft 365 workloads.

When Veeam Data Cloud backs up Microsoft 365 data, it automatically analyzes each backup for security threats. It then flags infected files (malware) and suspicious encryption patterns (ransomware). Detected threats are surfaced in the Threats section of the Microsoft 365 workload view in the VDC portal.

How Threat Detection Works

VDC Advanced Threat Detection runs automatically after each backup job completes. It does not scan file content directly, and detection is based entirely on file metadata, behavioral signals, and machine learning analysis of backup statistics.

Threat Type	Detection Method	Data Source	What Is Detected
Malware	Deterministic ^(rule-based)	Microsoft's built-in malware detection	Known malware signatures in OneDrive, Teams, and SharePoint files flagged during a backup session.
Ransomware	Machine Learning ^{(Random Cut Forest)}	Backup file statistics (entropy, extension changes, modification patterns)	Anomalous encryption patterns, unusual file extension changes, and entropy spikes deviating from the established baseline per workload.

Swipe to show more of the table

Privacy-Preserving Architecture

VDC Threat Detection analyzes metadata only. File content is never accessed, transmitted, or stored outside your backup environment. All data remains within your deployment region.

Solution

Navigate to the Threats View

In the Veeam Data Cloud (VDC) portal, select Microsoft 365 from the left navigation panel, and in the Management section, click Threats.

The threats page contains two tabs:

Malware Threats — A list of users whose OneDrive, Teams, or SharePoint files were flagged as containing malware during a backup session.
Ransomware Threats — A list of resources where anomalous encryption activity was detected.

The lists are sorted by most recent occurrence by default. Use the All Time date filter to scope results to a specific time range.

Investigate a Malware Threat

Click on any row in the Malware Threats tab, click the ⋯ action menu, then select View Details to open the Malware Threat Details panel.

Understanding the Malware Threat Fields

Entity Name: The Microsoft 365 object name of the infected files.
Resource Type: The Microsoft 365 resource type where the threat was found (e.g., OneDrive, SharePoint).
Number of Impacted Objects: Total count of files flagged as malware within the backup session.
Status: The current lifecycle state of the threat, which could be Active or Resolved.
Resolved By: The user who resolved the threat in the Veeam Data Cloud platform. Keep in mind, the resolution of a threat happens off-platform.
Date of Occurrence: The timestamp of the backup session during which infected files were detected.
Note: This represents the date of detection, not the date of actual infection.
Resolved Date: The timestamp when the user clicked "Resolved" in the Veeam Data Cloud platform.

Understanding the Malware Threat Details Fields

Explanation: A plain-language summary of the detection event.
File Name: Name of the infected file.
File Location: Full URL to the file.
File Created Date: Timestamp of when the file was created.
File Updated At: Timestamp for when the file was last modified.
Resolve Button: Updates the status of the threat in the Veeam Data Cloud platform to "Resolved".

Detection Source

Malware detection for Microsoft 365 is powered by deterministic signals from Microsoft's built-in malware detection. This means detection accuracy is consistent with Microsoft's own malware protection layer.

Investigate a Ransomware Threat

Click the Ransomware Threats tab to see detections based on anomalous backup behavior. Ransomware detections are scoped at the site or resource level rather than the individual user level.

Understanding the Ransomware Threat Fields

Entity Name: The Microsoft 365 object name of the infected files.
Resource Type: The Microsoft 365 resource type where the threat was found (e.g., SITE).
Number of Impacted Objects: Total count of files flagged as malware within the backup session.
Status: The current lifecycle state of the threat, which could be Active or Resolved.
Resolved By: The user who resolved the threat in the Veeam Data Cloud platform. Keep in mind, the resolution of a threat happens off-platform.
Date of Occurrence: The timestamp of the backup session during which infected files were detected.
Note: This represents the date of detection, not the date of actual infection.
Resolved Date: The timestamp when the user clicked "Resolved" in the Veeam Data Cloud platform.

Understanding the Ransomware Threat Details Fields

Explanation: A plain-language summary of the detection event.
File Name: Name of the infected file.
File Location: Full URL to the file.
File Created Date: Timestamp of when the file was created.
File Updated At: Timestamp for when the file was last modified.
Resolve Button: Updates the status of the threat in the Veeam Data Cloud platform to "Resolved".

Ransomware Requires a Baseline Period

The machine learning model (Random Cut Forest) requires approximately 45 days of backup history per workload to establish a reliable behavioral baseline before anomaly detection becomes fully effective. During this period, detection may be limited. New workloads or newly protected tenants will automatically build their baselines during this window.

More Information

Considerations and Limitations

Opt-in required: Threat Detection must be explicitly enabled per tenant. It is not active by default due to customer consent requirements for AI-powered features.
Microsoft 365 workloads only (current release): Threat Detection currently supports Microsoft 365 (i.e., OneDrive, Teams, and SharePoint).
Malware detection relies on Microsoft's built-in malware detection signals: If Microsoft does not flag a file as malware, the Veeam Data Cloud platform will not independently detect it.
Ransomware detection requires a 45-day baseline: New workloads or tenants will not have full anomaly detection until the machine learning (ML) model has established a behavioral baseline. During the ramp-up period, low-confidence anomalies may not be surfaced.
Ransomware detection is probabilistic: The Random Cut Forest ML model flags statistically anomalous patterns. All detections are labelled as "Potential ransomware activity" and are reviewed by Veeam operators before being marked Active.
File content is never accessed: Both malware and ransomware detection operate exclusively on metadata and behavioral statistics. Backup file content is never read, transmitted, or analyzed by the threat detection service.
False positives may occur: Legitimate bulk file operations (e.g., large migrations, mass rename events, encryption of files by authorized software) may occasionally trigger a ransomware detection. Veeam operators review these events before escalating to Active status.
Data residency: All threat detection data, including file metadata and detection results, is stored in the same Azure region as your Veeam Data Cloud deployment. No data crosses regional boundaries unless explicitly requested by the customer.

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-03-30T00: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-04-15

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 in February 2026. 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.

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.}

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.

Support Statement — Exchange Web Services (EWS) Deprecation

2026-03-25T00: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-03-26

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. Veeam software will be updated to ensure continued compatibility and data protection capabilities.

Solution

Veeam product features that currently use EWS will be transitioned to the Microsoft Graph API, ensuring as smooth a migration as possible before the phase-out date.

Users do not need to take any action at this time.

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.

Most Common Issues with Salesforce Connected App in Veeam Data Cloud for Salesforce

2026-03-25T00:00:00Z

Most Common Issues with Salesforce Connected App in Veeam Data Cloud for Salesforce

KB ID:	4810
Product:	Veeam Data Cloud for Salesforce
Published:	2026-01-23
Last Modified:	2026-03-25

Purpose

This article documents the changes to Connected App usage in Veeam Data Cloud for Salesforce resulting from Salesforce’s restriction of uninstalled connected apps, effective Autumn 2025. It provides guidance on authorization requirements, common connection errors, and necessary permissions for successful integration.

Solution

As of Autumn 2025, Salesforce has restricted the use of uninstalled connected apps (see Salesforce article). Due to these changes, customers may encounter errors when connecting a Salesforce organization to Veeam Data Cloud for Salesforce.

When authorizing Veeam Data Cloud in a Salesforce organization, Salesforce automatically creates the Connected App “VDC Salesforce Backup.” The user authorizing the connection must have the “Approve Uninstalled Connected Apps” permission. Without this permission, Salesforce will deny the connection.

Below are common errors that may occur during authorization or re-authorization, with steps to resolve them.

Connected App is not installed

Salesforce error code:

OAUTH_APPROVAL_ERROR_GENERIC

Resolution

Ensure the user authorizing the connection has the “Approve Uninstalled Connected AppsFrom Salesforce Documentation: This new user permission is automatically assigned to the System Administrator standard profile. Custom profiles aren’t automatically updated, including those previously cloned from the System Administrator standard profile. After the connected app usage restriction is enforced in September 2025, this user permission grants access to use uninstalled connected apps, bypassing the new usage restriction. It should only be assigned to highly trusted users, such as administrators and those involved in managing or testing connected app integrations. Salesforce recommend using care when assigning this user permission. For example, only grant to admin users and to users who manage connected app integrations and need to test the apps before installing on the org for access by other end users.” permission, then retry the authorization.
After the initial authorization attempt, Salesforce will create a connected app named VDC Salesforce Backup. Proceed to the Connected Apps OAuth Usage" page and click Install for the connected app in Salesforce. Then, try to authorize the Salesforce connection once again
If this error occurs when connecting a sandbox organization, run “Match Production Licenses to Sandbox without Refresh.”

Connected App is not installed or is blocked

Salesforce error code:

OAUTH_APP_ACCESS_BLOCKED

Resolution

In Salesforce, go to Setup, search for "Connected Apps," and select "Connected Apps OAuth Usage."
Unblock or Install the “VDC Salesforce Backup” Connected App as needed.

User authorizing the connection is not approved to use the Connected App

Salesforce error code:

OAUTH_APP_ACCESS_DENIED

This error occurs if the Connected App is configured to allow only admin-approved users.

Resolution

Create a custom permission set that grants access to the “VDC Salesforce Backup” Connected App.
Assign this permission set to the user who will authorize the connection.

"VDC Salesforce Backup" is not allowed to connect to your organization

Salesforce error code:

BAD_REQUEST

This error occurs if "API Access Control" is enabled for the organization.

Resolution

Ensure that the VDC Salesforce Connected app is installed.
Ensure that the connected app is added to the list of allowed applications under: Setup > API Access Control

More Information

Additional Information About Authorization Errors

For more information about OAuth 2.0 Authorization errors, please review the Salesforce Help documentation:

Salesforce Help > OAuth 2.0 Authorization Errors

Regarding the Future of Connected Apps

Starting with the Salesforce Winter '26 release, Salesforce will begin transitioning from Connected Apps to External Client Apps. For more information, please review this Salesforce article:

New connected apps can no longer be created in Spring '26

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.

Search Best Practices in Veeam Data Cloud for Microsoft 365

2026-03-25T00:00:00Z

Search Best Practices in Veeam Data Cloud for Microsoft 365

KB ID:	4730
Product:	Veeam Data Cloud for Microsoft 365
Published:	2025-06-26
Last Modified:	2026-04-01

New Search Experience for Veeam Data Cloud for Microsoft 365

We are excited to announce the initial rollout of our new search feature, designed to significantly improve the speed and efficiency of your search experience. The new search supports deleted item recovery and restore point search without the overhead of mounting restore points. For details on what's new, see KB4839: New Search Experience for Veeam Data Cloud for Microsoft 365.

Note: The best practices in this article continue to apply to OneDrive and SharePoint search while the new experience is being rolled out to those workloads.

Purpose

This article offers guidance on choosing the best search method in Veeam Data Cloud for Microsoft 365 based on various scenarios.

Solution

Best Practice Summary

Start with Basic Search for fast, focused results when you know the relevant keyword and property.
Browse Backups when you know where to look or want to manually locate items within a specific backup or restore point.
Use Advanced Search as a last resort, for very broad or complex queries, or when you lack enough details for a targeted search.

How to Access Search

Log in to the Veeam Data Cloud for Microsoft 365 portal.
Navigate to the Search section on the dashboard.
Learn more about search.

Search Options

Basic Search (Recommended)

Basic Search is optimised for speed and simplicity, and best used when you know what you’re looking for.

Basic Search is the fastest and most user-friendly way to find information in your Microsoft 365 backups. Use this option for most scenarios:

Outlook: Searches keywords in email subjects.
SharePoint: Searches keywords in site names or documents within a site.
Teams: Searches keywords in channel chat messages (posts).
OneDrive: Searches keywords in file names.

Veeam Data Cloud for Microsoft 365 User Guide: Performing Basic Search

Browsing Backups (Manual Search)

Browsing is effective for targeted restores or when you want to verify backup contents without performing a search.

A technical alternative is to browse through your backups manually. This method lets you directly explore backup content (mailboxes, sites, files, etc.) without using the search interface.

How it works: You can open a specific backup or restore point and navigate through its structure (folders, mailboxes, documents, etc.) to find the needed data.
When to use: If you know the likely location of the item (e.g., a specific folder or user mailbox), browsing can often be faster and more precise than running a broad advanced search.
Benefits: This method avoids the overhead of mounting large restore points or running resource-intensive queries.

Veeam Data Cloud for Microsoft 365 User Guide: Performing Restore

Advanced Search (For Complex or Broad Queries)

Advanced Search allows for complex, organisation-wide, or less-specific queries using advanced filters.

Use cases: When Basic Search and browsing do not return the needed results, or when you need to search on specific metadata or content across large datasets.
Resource note: Advanced Search requires mounting restore points and can take significant time, especially with broad criteria or large backups.

Important: To minimise wait times and system load, use Basic Search or browse backups whenever possible. Reserve Advanced Search for scenarios where other methods are not sufficient.

Veeam Data Cloud for Microsoft 365 User Guide: Performing Advanced Search

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.

New Search Experience for Veeam Data Cloud for Microsoft 365

2026-03-24T00:00:00Z

New Search Experience for Veeam Data Cloud for Microsoft 365

KB ID:	4839
Product:	Veeam Data Cloud for Microsoft 365
Published:	2026-03-24
Last Modified:	2026-04-10

Purpose

We are excited to announce the initial rollout of our new search feature, designed to significantly improve the speed and efficiency of your search experience. Below are the details and important limitations to be aware of during this phased rollout.

What's New

Faster Search Experience:
Our upgraded search engine delivers results much more quickly, ensuring you can find what you need with minimal wait time.
Expanded Search for Deleted Items:
You can now search for deleted items—a capability previously available only in the browse experience.
Important limitation:
- You’ll be able to search for deleted items only from one month prior to the feature’s release date. Any items deleted before that will not appear in search results.
- Going forward, all deleted items will be searchable from the time of deletion.
Restore Point Search:
The new search feature allows searching by restore points.
Important limitation:
- Only restore points from up to one month before the initial release will be available in search.
- All future restore points, created after the rollout, will be fully searchable.
Scope of Search (Initial Phase):
- The first rollout includes email (Exchange) search only.
- OneDrive and SharePoint search capabilities will be added in the next phase.
Email Body Content Search (Initial Limitation):
- At launch, searching within email body content will not be available. This capability may be added in future updates.

More Information

Frequently Asked Questions

Will I be able to see deleted items in Search?

How to Safely Perform Snapshot Rollback of Veeam Backup for Microsoft 365

2026-03-24T00:00:00Z

How to Safely Perform Snapshot Rollback of Veeam Backup for Microsoft 365

KB ID:	4837
Product:	Veeam Backup for Microsoft 365 \| 8 \| 8.1 \| 8.2 \| 8.3
Published:	2026-03-24
Last Modified:	2026-03-25

Purpose

This article provides step-by-step guidance for performing a snapshot rollback of a Veeam Backup for Microsoft 365 deployment in the event of a disaster.

Critical Warning

Rolling back to a snapshot is a complex and highly risky process that should only be performed in rare disaster situations. This action is reserved for exceptional cases and must not be used as a standard recovery or troubleshooting step in production environments. Incorrect use can lead to serious data, configuration, or repository corruption, or make the system unrecoverable. Always consult Veeam Support before taking this action.

Solution

Supported Versions and Limitations

Snapshot Rollback is only supported when used to roll back Veeam Backup for Microsoft 365 between patches within the same major and minor release (e.g., 8.0.2.x to 8.0.2.y).
Snapshot Rollback is not supported to rollback between major (e.g., 8.x back to 7.x) or minor versions (e.g., 8.3.0.x back to 8.2.0.x).

Prerequisites and Restrictions

Before reverting the snapshot:
- All jobs and restore tasks must be fully stopped and disabled.
- All NATS streams must be removed/cleaned to avoid metadata conflicts.
- All Veeam Backup for Microsoft 365 components (controller, proxies, PostgreSQL, and NATS) must be fully shut down.
Never connect a PostgreSQL database used with a higher Veeam Backup for Microsoft 365 version to a lower Veeam Backup for Microsoft 365 version — this can cause repository corruption and schema mismatches.

Step-by-Step Rollback Procedure

Part 1: Preparation and Shutdown

Stop all Veeam Backup for Microsoft 365 components:
- Controller service (Veeam.Archiver.Service)
- All proxy servers (Veeam.Archiver.Proxy)
- REST service (Veeam.Archiver.REST.Service)
- Update service (Veeam.Archiver.Update.Service)
- PostgreSQL server
- NATS server

Part 2: Environment Drain and NATS Stream Cleanup

Stop and disable all jobs, and ensure all restore tasks have stopped.
Remove or clean all NATS streams.

For example, delete the contents of the folder:
C:\ProgramData\Veeam\Backup365\nats\jetstream\$G

Part 3: Snapshot Reversion

Revert the environment to the snapshot created prior to the update.

Tip: If you are reading this article before creating the original snapshot, Veeam recommends stopping all Veeam Backup for Microsoft 365 services before creating that original snapshot.

Part 4: Post-Rollback Startup Sequence (Strict Order)

Start the PostgreSQL server.
Start the NATS server (ensure all streams are cleaned up).
Start the Veeam Backup for Microsoft 365 controller service (it will recreate all required NATS streams).
Start the Veeam Backup for Microsoft 365 proxy servers.

The proxies will perform repository synchronization checks. If any repository contains backups or blobs newer than the reverted metadata, the proxies will detect that repository as out-of-sync.

More Information

Veeam encourages all customers to consult Veeam Support before performing any snapshot rollback of a Veeam Backup for Microsoft 365 server.

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

Release Information for Veeam Backup for Microsoft 365 8.4

Release Information for Veeam Backup for Microsoft 365 8.4

Requirements

Release Information

8.4.0.1457

2026-04-16

New Features and Enhancements

Bug Fixes

General

Backup and Backup Copy

Restore

REST APIs

PowerShell and Data Management

Download Information

How to Configure File Version Protection

How to Configure File Version Protection

Purpose

Cause

Solution

How File Version Protection Works

Important considerations

How To Configure Protecting Only The Latest File Version

For Veeam Data Cloud for Microsoft 365

For Veeam Backup for Microsoft 365 8.4+

Release Information for Veeam Backup for Salesforce 3 Cumulative Patches

Release Information for Veeam Backup for Salesforce 3 and Updates

Requirements

What's New

Veeam Backup for Salesforce 3.2 (3.2.0.3957)

Release Notes

Improvements

Security

Resolved Issues

Veeam Backup for Salesforce 3.1.2 (3.1.2.3133)

Veeam Backup for Salesforce 3.1.1 (3.1.1.2714)

Veeam Backup for Salesforce 3.1 P20241210 (3.1.0.2378)

Veeam Backup for Salesforce 3.1 (3.1.0.2298)

Deployment Information

Build Numbers and Versions of Veeam Backup for Salesforce

Build Numbers and Versions of Veeam Backup for Salesforce

Related Articles

Build Numbers and Versions of Veeam Backup for Microsoft 365

Build Numbers and Versions of Veeam Backup for Microsoft 365

Related Articles

How to Deploy Veeam Backup for Salesforce External Client App

How to Deploy Veeam Backup for Salesforce External Client App

Purpose

Solution

Create New External Client App

Copy Token Key and Secret

Release History for Veeam Service Provider Console 9

Release History for Veeam Service Provider Console 9

Veeam Service Provider Console 9 Builds

9.2.0.33215 (9.2 GA)

Release Information

9.1.0.30713

New Features and Enhancements

General

Resolved Issues

9.1.0.30636 (9.1 GA)

Release Information

9.1.0.30345 (9.1 RTM)

Release Information

9.0.0.29860

Resolved Issues

Upgrade

Data Collection

Licensing

9.0.0.29555

Release Information

Download Information

Deployment Guidance

Deployment ISO

Build Numbers and Versions of Veeam Service Provider Console

Build Numbers and Versions of Veeam Service Provider Console

Related Articles

How to Configure krb5.conf for Cross-Domain Hyper-V Cluster Management

How to Configure krb5.conf for Cross-Domain Hyper-V Cluster Management

Purpose

**For Veeam Backup for Microsoft 365 8.4+**