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

SharePoint

Active
CMS & Content Latest Version: 16.0.19127.20518 Latest Release: Feb 10, 2026

Microsoft SharePoint is a web-based collaboration platform for document management and intranet portals.

Versions

6

Latest Version

16.0.19127.20518

Active Support

1

EOL

3

Lifecycle Timeline

Today
subscription
subscription
2019
2019
2016
2016
2013
2013
2010
2010
2007
2007
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
subscriptionNov 2, 2021YesNo16.0.19127.20518No
Active
2019Oct 22, 2018Jan 9, 2024Jul 14, 202616.0.10417.20097No
Security
2016May 1, 2016Jul 13, 2021Jul 14, 202616.0.5539.1002No
Security
2013Jan 9, 2013Apr 10, 2018Apr 11, 202315.0.5545.1000No
EOL
2010Jul 5, 2010Oct 13, 2015Apr 13, 202114.0.7268.5000No
EOL
2007Jan 27, 2007Oct 9, 2012Oct 10, 201712.0.6690.5000No
EOL

Frequently Asked Questions

Which versions of SharePoint have reached end of life?
The following SharePoint versions have reached end of life and no longer receive security updates: 2013, 2010, 2007. It is recommended to upgrade to a supported version.
Is it safe to continue using SharePoint 2013?
SharePoint 2013 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 SharePoint?
The latest version of SharePoint is 16.0.19127.20518, released in the subscription release cycle.
How many versions of SharePoint are currently supported?
SharePoint currently has 3 actively supported version(s): subscription, 2019, 2016.
When does SharePoint subscription reach end of life?
SharePoint subscription does not have a specific end-of-life date announced yet.
What should I do when SharePoint reaches end of life?
When a SharePoint 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.