The SharePoint Server end of support deadline finally arrived on July 14, 2026, and the aftermath is now hitting IT teams across the globe. Microsoft officially retired SharePoint Server 2016 and SharePoint Server 2019 that day, along with related Project Server components. Consequently, any farm still running these versions is now unsupported production software. Moreover, Microsoft has confirmed there is no paid Extended Security Update program to lean on. Therefore, admins have exactly three legitimate paths forward, and each one carries its own trade-offs.
This guide breaks down what actually changed on July 15, 2026, why the risk profile shifts overnight, and how to plan your next move. In addition, we cover how Copilot and the modern SharePoint experience fit into the migration story. If your organization is still running on-premises SharePoint, keep reading — the next 90 days matter more than the last 90 did.
What Actually Happened on July 14, 2026
SharePoint Server 2016 and SharePoint Server 2019 both reached the end of extended support on July 14, 2026. In short, Microsoft will not release security patches, cumulative updates, or feature fixes for either platform. Furthermore, Microsoft Premier, Unified, and Pay-Per-Incident support cannot open break-fix tickets against these versions. If your farm crashes at 2:00 AM on a Saturday, you now escalate to your ISV or your internal team — not to Redmond.
InfoPath Forms Services was also removed from SharePoint Online after July 14, 2026. As a result, any lingering InfoPath forms that survived the cloud transition need immediate replacement, typically with Power Apps or third-party alternatives. Meanwhile, Project Server 2016 and Project Server 2019 hit the same cliff, so hybrid Project Online scenarios that leaned on the on-prem side are now equally exposed.
Why SharePoint Server End of Support Is Different This Time
Microsoft historically offered Extended Security Updates for retired server products such as Windows Server 2012 and SQL Server 2012. However, no ESU program exists for SharePoint Server 2016 or 2019. Therefore, there is no paid escape hatch. Additionally, the modern lifecycle policy governing SharePoint Server Subscription Edition means there is no fixed retirement date for that path — a first for the product family.
Compliance teams are already reacting. For example, running unsupported software commonly triggers findings under HIPAA, SOC 2, PCI DSS, FedRAMP, and GDPR audits. Moreover, cyber insurance carriers have started excluding ransomware claims tied to unsupported platforms. Consequently, the business case for delaying migration weakens every quarter.
The Three Migration Paths After SharePoint Server End of Support
Every admin now weighing options has three practical paths. Each one answers a different question about cost, control, and cloud readiness. Below is a plain-English summary of the choices most organizations are considering right now.
- SharePoint Online (SPO) — the recommended path for most tenants. It is included with existing Microsoft 365 licenses and receives new features first, including SharePoint Copilot Apps and the modernized OneDrive experience.
- SharePoint Server Subscription Edition (SPSE) — the on-premises continuation path. It supports in-place upgrades from SharePoint Server 2019 at the latest CU level and preserves legacy dependencies such as SharePoint 2013 workflows.
- Hybrid deployment — a mix of SPO and SPSE. This path helps organizations with data sovereignty, regulatory, or air-gapped workloads that cannot go fully cloud.
Notably, Microsoft positions SPO as the priority destination, and many next-generation features may never ship to SPSE. However, SPSE still matters for regulated industries, sovereign clouds, and workloads that need modern auth without a full cloud jump.
How SharePoint Server End of Support Affects Third-Party Tools
The blast radius extends beyond Microsoft. ShareGate, AvePoint, Quest, Nintex, K2, DocuSign, and other ISVs actively maintain compatibility only with supported Microsoft versions. Consequently, expect a wave of public end-of-support announcements from ISV connectors within six months of July 14, 2026. In addition, Nintex Workflow and Forms for SharePoint reach their own end of life in 2026, which compounds the pressure on organizations still running SP2019-based workflow estates.
Meanwhile, backup vendors, DLP add-ons, and eDiscovery integrations all face similar compatibility risk. Therefore, an ISV inventory should sit at the top of every migration readiness checklist. Otherwise, migration teams often finish the SharePoint move only to discover a critical add-on cannot follow.
Choosing Between SharePoint Online and SPSE After End of Support
Most admins already know SharePoint Online is the strategic destination. However, the choice between SPO and SPSE hinges on several practical factors. For example, teams still relying on legacy workflows or line-of-business full-trust code often need SPSE as a bridge. On the other hand, teams ready to consume AI-first features benefit from moving straight to SPO.
- Choose SharePoint Online if: you want native Microsoft 365 Copilot integration, SharePoint Copilot Apps, Microsoft 365 Archive, and the July 2026 modernized OneDrive experience.
- Choose SharePoint Server Subscription Edition if: you need data residency guarantees, run classified or sovereign workloads, or need to preserve SharePoint 2013 workflow compatibility while you refactor.
- Choose a hybrid model if: you have mixed workloads, are staged for a multi-year cloud transition, or have regulated content that must remain on-premises for now.
In addition, remember that a typical enterprise-scale SharePoint migration takes six to eighteen months depending on data volume and complexity. Therefore, teams starting today are already behind the ideal timeline, and the risk window keeps widening.
Copilot, AI, and the SharePoint Server End of Support Story
The end-of-support cliff coincides with Microsoft’s broader repositioning of SharePoint as the content backbone for AI. Notably, SharePoint Copilot Apps entered public preview in July 2026, with general availability targeted later this year. Consequently, sites migrated to SharePoint Online can host rich, interactive Copilot components built with SPFx — a capability that will not land in SPSE any time soon.
In addition, Microsoft 365 Copilot Cowork reached general availability on June 16, 2026. Cowork plans and executes long-running, multi-tool tasks end-to-end, including content generation and site actions. As a result, organizations that migrate SharePoint content to SPO also unlock Copilot Cowork automations that touch that content directly. Furthermore, the recent addition of Anthropic’s Claude as a selectable model inside Microsoft 365 Copilot gives admins more flexibility for enterprise-grade document reasoning.
Compliance and Cyber Insurance Implications
Compliance risk is now the loudest business case. For instance, auditors evaluating HIPAA, SOC 2, PCI DSS, FedRAMP, ISO 27001, or GDPR programs treat unpatched platforms as an unacceptable risk to data confidentiality and integrity. Additionally, insurance carriers have started denying or excluding ransomware claims where the underlying platform was unsupported at the time of the breach. Therefore, executive teams that treat end-of-support as a technical detail miss the bigger financial exposure.
Furthermore, running unsupported SharePoint farms increases the chance of a successful attack. Legacy authentication, older TLS configurations, and unpatched CVEs open doors that modern threat actors already know how to walk through. Consequently, security teams are moving migration timelines earlier, often ahead of business milestones.
Your Next 90 Days: A Practical Migration Checklist
If your farm is still on SharePoint Server 2016 or 2019 today, the following plan gives you a realistic starting point. Furthermore, it lines up with what most migration partners are actually recommending right now.
- Inventory every farm, database, and customization. Include SPFx solutions, full-trust code, workflows, InfoPath forms, and third-party connectors.
- Classify content by risk and business value. Highly regulated data usually moves last, while inactive content can be archived or retired.
- Map your ISV dependencies. Confirm whether ShareGate, AvePoint, Quest, Nintex, or other vendors support your target destination.
- Pick a destination per workload. SPO for modern collaboration and AI, SPSE for regulated or specialized workloads, hybrid for phased plans.
- Stand up modern authentication and Entra ID. Retire NTLM and legacy auth wherever possible before cutover.
- Pilot Copilot readiness. Confirm sensitivity labels, permissions, and Restricted SharePoint Search are configured before Copilot lights up on migrated content.
- Communicate the risk clearly to leadership. Cite compliance, insurance, and support gaps in business terms, not just technical language.
- Set a hard cutover deadline. Nine to twelve months is realistic for most enterprises; longer creates unacceptable exposure.
Common Mistakes to Avoid Post-Deadline
Some organizations are still tempted to delay, patch informally, or lift-and-shift without cleanup. However, each of these shortcuts creates future pain. For example, in-place upgrades to SPSE without content cleanup carry legacy permissions, orphaned sites, and stale workflows into the new environment. Meanwhile, “migrate and forget” moves to SPO ignore the Copilot governance layer that now matters just as much as file paths.
Additionally, teams often underestimate identity work. Modern authentication, conditional access, and sensitivity labels are the fabric that lets Copilot behave safely in the new home. Therefore, treat identity, DLP, and labeling as first-class migration workstreams — not afterthoughts.
What Comes Next for SharePoint in 2026
Looking forward, the SharePoint roadmap is decisively AI-led. For instance, the July 2026 SPFx roadmap update reframes the developer story as “AI-connected Microsoft 365 extensibility” rather than “modern SharePoint extensibility.” Moreover, SharePoint Server Subscription Edition Version 26H1 introduced new controls such as excluding the “Everyone” claim from People Picker, along with security and lifecycle improvements. Consequently, admins now have a modern feature story on both sides of the fence.
Meanwhile, Microsoft 365 Archive is launching in July 2026, allowing individual files to move to a lower-cost storage tier without archiving the entire site. In addition, refreshed filtering, a new Libraries view, and Markdown co-authoring bring SharePoint Online closer to a modern content platform than ever before. Therefore, the migration story is not just about surviving end of support — it is about unlocking capabilities that on-prem SharePoint simply cannot deliver.
Final Word on SharePoint Server End of Support
The SharePoint Server end of support milestone was one of the most anticipated Microsoft deadlines in years. Now that it has passed, the work shifts from planning to execution. Furthermore, the compliance and insurance risk of doing nothing keeps rising each week. Consequently, the safest move is to pick a destination, publish a timeline, and start executing this quarter.
Explore more SharePoint, Microsoft 365, and Copilot guidance across SharePoint Monkey to keep your modernization moving. In addition, subscribe or bookmark the blog for weekly deep dives into Copilot, Azure AI, and the modern SharePoint experience.
Sources
- Stefan Goßner — SharePoint End of Support: What Changed on July 15, 2026
- SharePoint Support — 2016 and 2019 End of Support Countdown
- Microsoft Learn — SharePoint Server Subscription Edition 26H1
- Microsoft 365 Developer Blog — SPFx Roadmap Update July 2026
- Microsoft 365 Blog — Copilot Cowork Generally Available
- Level Up M365 — Microsoft 365 Roadmap Updates July 2026
- SharePoint Library — SharePoint in 2026: What’s Changed
- Channel Insider — SharePoint On-Prem End of Life Migration Guide
Discover more from SharePoint Monkey
Subscribe to get the latest posts sent to your email.