Loading...
Loading...
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.
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.
When the Integrity Check is performed on an object storage repository, there will be a temporary increase in the number of API calls the storage system handles while previously written files are scanned for inconsistencies. The redownloading of affected files afterward also increases storage usage on that same repository.
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.