EOL.Wiki EOL.Wiki
← ← Back to all products

Veeam Backup for Microsoft 365

Active
Cloud & Platforms Latest Version: 8.3.0.2201 Latest Release: Dec 18, 2025

Veeam Backup for Microsoft 365 protects Exchange Online, SharePoint, OneDrive, and Teams data.

Versions

7

Latest Version

8.3.0.2201

Active Support

1

EOL

5

Lifecycle Timeline

Today
8
8
7
7
6
6
5
5
4
4
3
3
2
2
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
8Sep 3, 2024YesSep 3, 20268.3.0.2201No
Active
7Feb 28, 2023Dec 28, 2023Jun 28, 20267.1.0.2031No
Security
6Mar 9, 2022Feb 28, 2023Mar 9, 20246.1.0.1015No
EOL
5Dec 3, 2020Mar 9, 2022Dec 2, 20235.0.3.1063No
EOL
4Nov 26, 2019Dec 3, 2020Nov 26, 20224.0.1.625No
EOL
3Apr 2, 2019Nov 26, 2019Apr 2, 20223.0.0.422No
EOL
2Jul 24, 2018Apr 2, 2019Jul 24, 20212.0.0.814No
EOL

Frequently Asked Questions

Which versions of Veeam Backup for Microsoft 365 have reached end of life?
The following Veeam Backup for Microsoft 365 versions have reached end of life and no longer receive security updates: 6, 5, 4, 3, 2. It is recommended to upgrade to a supported version.
Is it safe to continue using Veeam Backup for Microsoft 365 6?
Veeam Backup for Microsoft 365 6 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Veeam Backup for Microsoft 365?
The latest version of Veeam Backup for Microsoft 365 is 8.3.0.2201, released in the 8 release cycle.
How many versions of Veeam Backup for Microsoft 365 are currently supported?
Veeam Backup for Microsoft 365 currently has 2 actively supported version(s): 8, 7.
When does Veeam Backup for Microsoft 365 8 reach end of life?
Veeam Backup for Microsoft 365 8 is scheduled to reach end of life on Sep 3, 2026.
What should I do when Veeam Backup for Microsoft 365 reaches end of life?
When a Veeam Backup for Microsoft 365 version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.