Release Information for Veeam Backup for Microsoft 365 5b

General

• Under certain conditions retention policy mistakenly cleans actual Exchange backup data from Jet-based repositories set with snapshot-based retention of less than 2 years. This issue applies to Veeam Backup for Microsoft Office versions 3.0 – 4c. 

Backup

• SharePoint and OneDrive backup may fail with “(500) Internal Server error” or “(400) Bad Request” error.
• Under certain conditions, Teams backup may fail with the “Object reference not set to an instance of an object” error.
• OneDrive backup may fail with the “Index (zero-based) must be greater than or equal to zero and less than the size of the argument list” error.
• SharePoint backup may fail with the following warning: “Failed to request item versions for list: %name% (list ID: %ID%). The operation has timed out”.
• SharePoint backup may fail with the “Invalid MIME content-length header encountered on read” error.
• Archive mailbox backup may fail with the “Failed to access archived message folder root. SOAP header Action was not understood” error.

Restore

• Teams restore with an application and app certificate fails with the “Error in validating credentials: Account does not have a valid Microsoft Teams license”.
• OneDrive restores may fail with the “The attempted operation is prohibited because it exceeds the list view threshold enforced by the administrator" error.
• Under certain conditions, some of the site folders may not be displayed when browsing SharePoint or OneDrive for Business backups.
  

RESTful API

• In the (GET) /v5/JobSessions/{jobSessionsId}/LogItems and (GET) /v5/JobSessions/{jobSessionsId}/LogItems/{logItemId} REST API calls responses, the “creationTime” and “endTime” values are provided in the backup server local time instead of the UTC.General.
• The “Last backup” parameter is displayed in the job sessions history while should be hidden from the job results.