Every year someone declares that SharePoint is dead. It never was, and it is not now. But 2026 is the year in which several real parts of it reached the end, close together, and that deserves a clear map rather than the usual noise. On 2 April 2026 SharePoint Add-ins retired in SharePoint Online. That retirement does not retire Server Add-ins deployed through an on-premises app catalog. On 14 July 2026, days before this was written, SharePoint Server 2016 and 2019, InfoPath 2013 and SharePoint Designer 2013 all left support on the same day. Meanwhile SharePoint itself remains one of the pillars of Microsoft 365, and its on-premises edition has committed support into the next decade.
The useful distinction is between product support, feature retirement and application compatibility. A date about one platform does not establish the behavior of the other.
Two SharePoints, one name
Most of the confusion comes from treating SharePoint as one thing. It is two product lines that share a name: SharePoint Online, the evergreen service inside Microsoft 365, and SharePoint Server, the on-premises product you run yourself. The cloud line is Microsoft's primary platform and moves continuously. The server line is where the version numbers people argue about live, and where the July 2026 dates have just landed.
| Version | Status in July 2026 |
|---|---|
| SharePoint 2007 / 2010 / 2013 | Long out of support |
| SharePoint Server 2016 | End of support, 14 July 2026 |
| SharePoint Server 2019 | End of support, 14 July 2026 |
| SharePoint Server Subscription Edition | Current, supported through at least 2035 |
| SharePoint Online | Microsoft's primary platform, evergreen |
What actually ended
Nothing about the word SharePoint died. Specific technologies did, and most of them had been dead on their feet for years:
| Technology | Boundary to establish before replacement |
|---|---|
| InfoPath 2013 | Support ended on 14 July 2026; evaluate the form, workflow, data and hosting requirements before selecting a replacement |
| SharePoint Designer 2013 | The tool's support ended on 14 July 2026; inventory workflow engines and platform-specific dependencies separately |
| Farm and full-trust solutions | Server-side code, not universally retired; validate SE compatibility and the authorization boundary. SPFx does not replace timer jobs or server-side execution |
| Sandbox solutions | Identify code-based versus declarative functionality and the target platform before selecting a migration path |
| JSLink, ribbon actions and master pages | Establish the page experience and supported extension point; formatting and SPFx extensions solve particular UI needs |
| SharePoint Online Add-ins and Azure ACS for SharePoint Online | Retired on 2 April 2026; review remote application identity separately from UI customization |
| Server Add-ins in an on-premises app catalog | Excluded from the Online Add-in retirement; check each dependency, including any authentication service it uses |
The Online Add-in retirement notice explicitly distinguishes these platforms. The Subscription Edition removal list is a different contract. Neither supports calling every older customization retired or treating SPFx as a universal replacement.
A replacement also needs a deployment and licensing assessment. A cloud workflow or forms service is not automatically an equivalent solution for a disconnected farm, a privileged operation or a transaction spanning several systems.
Why Subscription Edition exists
For years, staying on SharePoint Server meant a major upgrade every few years and a wait for the next box: 2016, then 2019, then whatever came next. Subscription Edition ends that rhythm. It follows the Modern Lifecycle Policy: features arrive continuously, and support continues for as long as the farm is kept current, with no planned end before 31 December 2035 at the earliest (Microsoft Lifecycle). That is Microsoft 365's model, not Windows Server's: its long-term releases keep fixed end dates (Windows Server 2022). That is why there is no "SharePoint 2022" to wait for.
Subscription Edition or SharePoint Online?
If you are staying on-premises, Subscription Edition is the destination. But the first question is whether to stay on-premises at all. The two are not the same product with a different bill attached.
| Aspect | Subscription Edition | SharePoint Online |
|---|---|---|
| Where it runs | Your servers | Microsoft's cloud |
| Who operates it | You | Microsoft |
| Updates | You install them | Automatic, continuous |
| Control | Maximum | Less, more innovation |
| Where data sits | Your datacentre | Microsoft 365 |
| Best fit | Regulation, data sovereignty | Most other organisations |
Extensibility depends on the platform
SPFx is a client-side extension model, not a universal replacement for server-side business logic. SharePoint Online and SharePoint Server support different SPFx versions and capabilities. The compatibility reference must be read for the target platform.
For SE, inventory farm solutions, event receivers, timer jobs and external integrations separately. A supported database upgrade does not establish that their assumptions, identity paths or permissions survive. For Online, evaluate the documented client-side and remote-application alternatives. The Add-in retirement notice explicitly excludes Server Add-ins deployed through an on-premises app catalog and does not retire REST, CSOM or JSOM.
What the dates ask of every estate
The dates above provide concrete inventory questions:
- Which workflows still require the unsupported SharePoint Designer authoring tool?
- Which farm solutions run on unsupported Server 2016 or 2019 builds, and what must be validated for SE?
- Which classic pages have dependencies that need a separate modernisation path?
- Which Online integrations depend on the retired Azure ACS service?
- Which unsupported farms have no tested migration or containment plan?
A feature continuing to run does not establish vendor support. Operational failures and support status must be checked separately. Moving off them is a project in its own right, and any interruption it causes has to be chosen, estimated and demonstrated in rehearsal; migrating SharePoint without stopping the business looks at how that is done on each destination.
What to build on today
There is no single answer, but there is a clear default for each situation:
Not sure where your own environment stands? The SharePoint Compass turns these facts into a read on your estate in a couple of minutes: recommended destination, risk profile and next steps. It is free, and it runs entirely in your browser, so nothing is sent anywhere.
None of this stands alone, either. The same fleet running these workspaces is the one leaving Windows 10 behind this year, and the identity, management and security decisions taken there are the same ones that govern who reaches your SharePoint, as we covered in Windows 10 has ended, Windows 11 is the minimum.
SharePoint did not die, it moved
The honest version of "SharePoint is dead" is narrower and more useful: a set of specific technologies died, on real dates, and building on them now is a decision to take on debt. The platform underneath is more capable, more extensible and better secured than the one those technologies belonged to. Organisations that treat 2026 as a map rather than a headline are the ones that come out of it on a platform with a future rather than a countdown.
Sources and scope, reviewed 31 October 2026
- Products reaching end of support in 2026
- SE lifecycle
- Additional support commitment
- SE removed and deprecated features
Deployment choice also depends on residency, integrations, operations and application requirements. Organisation size or regulation alone is not a decision rule. Use the edition comparison for a more detailed discussion.
Support independent engineering knowledge
Knowledge, Analysis, the Field Guide and the tools are free to read and use, and they stay that way. If this article saved you time, you can support the research and writing behind it. Support is voluntary and unlocks nothing.
Buy me a coffee (opens in a new tab)João Lívio's page on buymeacoffee.com