1-800-691-1991 | 9am - 8pm ET

Release Information for Veeam Backup for Microsoft Office 365 5b


Please confirm that you are running one of the following versions of Veeam Backup for Microsoft Office 365 before upgrading to 5b:

  • 3.0 (build
  • 4.0 (build
  • 4a (builds,
  • 4b (builds,
  • 4c (builds,,,
  • 5.0 (builds,
  • 5a (build

You can check this under Help and Support > About in the Veeam Backup for Microsoft Office 365 console. To upgrade from earlier versions, please contact our Customer Support. After upgrading, your build number will change to

  • Upgrade from the beta version of Veeam Backup for Microsoft Office 365 5.0 is not supported.
  • Veeam Backup for Microsoft Office 365 5b (build is NOT applicable to installations on top of:
    • Veeam Backup & Replication 9.5 Update 4, 4a, or 4b
    • Veeam Cloud Connect 9.5 Update 4, 4a, or 4b

Before you apply this update, be sure to review the ‘Upgrading Veeam Backup for Microsoft Office 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 v11 and Veeam Cloud Connect v11. 


  • Guest users are automatically excluded from organization objects enumeration and backup.
  • For backup jobs processing personal sites, email notifications on job results add a link to user’s backed up personal sites.

Resolved Issues


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


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


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


  • 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.
MD5: e9bf0955b9c22ee53d543ca64702e624
SHA-1: 8024f4740790a4919fb3026ddb9c67a45536f5ff
Veeam Backup for Microsoft Office 365 5.0
Last Modified:
Please rate how helpful this article was to you:
3.8 out of 5 based on 8 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.