- Veeam Support Knowledge Base
- Release Information for Veeam Backup for Microsoft 365 5d
Release Information for Veeam Backup for Microsoft Office 365 5d
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
Oops! Something went wrong.
Please, try again later.
Requirements
Please confirm that you are running one of the following versions of Veeam Backup for Microsoft 365 before upgrading to 5d:
- 3.0 (build 3.0.0.422)
- 4.0 (build 4.0.0.1345)
- 4a (builds 4.0.0.1553, 4.0.0.1580)
- 4b (builds 4.0.0.2516, 4.0.0.2549)
- 4c (builds 4.0.1.519, 4.0.1.531, 4.0.1.545, 4.0.1.612, 4.0.1.625)
- 5.0 (builds 5.0.0.1061, 5.0.0.1063)
- 5a (build 5.0.0.1070)
- 5b (builds 5.0.1.179, 5.0.1.207, 5.0.1.225, 5.0.1.252)
- 5c (builds 5.0.2.22, 5.0.2.42)
You can check this under Help and Support > About in the Veeam Backup for Microsoft 365 console. To upgrade from earlier versions, please contact our Customer Support. After upgrading, your build number will change to 5.0.3.1033.
Before you apply this update, be sure to review the ‘Upgrading Veeam Backup for Microsoft 365’ section of the Release Notes document.
For detailed information about this release, please refer to the Release Notes document.
What’s New
- Support to install on top of Veeam Backup & Replication 11a.
Resolved Issues
Backup
- A retry is not initiated for OneNote and Excel files that have been changed during backup and failed to be processed with “The remote server returned an error: (409) Conflict” warning.
- Under certain conditions, in hybrid organizations, adding some users to a backup job fails with the “An item with the same key has already been added” error.
Restore
- In Veeam Explorer for Microsoft Teams, restore of a single team tab may fail with the “Object reference not set to an instance of an object” error.
- Under certain conditions, in Veeam Explorer for Microsoft Exchange, mounting a standalone Veeam Backup for Microsoft 365 repository database restored from a Veeam Backup & Replication backup may fail.
RESTful API
- Under certain conditions, the (GET) /v5/RestoreSessions/{restoreSessionId}/organization/teams/{teamId}/posts/{postId} request fails with the “Post Not Found” error.
- Saving a SharePoint file as a ZIP archive via REST APIs fails with the “Could not find a part of the path” error, if the length of the file path including the file name exceeds 255 characters.
- If the Microsoft Teams service is enabled for an organization, no data for such an organization can be requested with the REST API calls earlier than v5.
- Restoring and saving Teams files with the (POST) /v5/RestoreSessions/{restoreSessionId}/organization/teams/{teamId}/files/{fileId}/action request completes with code 500, although the files are restored successfully.
- A title of a SharePoint site added to a backup job via REST APIs is empty if such a title has not been explicitly specified.
More information
Please find the latest version of Veeam Backup for Microsoft 365 here:
https://www.veeam.com/backup-microsoft-office-365-download.html
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
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
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.