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-03-31
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

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

error icon

Oops! Something went wrong.

Please, try again later.

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.

Mitigation

Veeam is working expeditiously to resolve this issue with an upcoming release; until that time, all customers are advised to review the following with their technical and governance teams:

  • Avoid deleting and overwriting critical files, and list attachments in the production environment.
  • Temporarily adjust the Microsoft 365 retention and lifecycle policies (e.g., retention labels/policies, auto-expiration, scheduled cleanup) to prevent the removal or permanent deletion of such content, so that it remains in production.

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

Veeam is working on a new product version that fixes the root cause of this issue. We will notify you when it becomes available. 

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

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

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

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

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

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.