SharePoint Feature Retirements and Deprecations: Everything Ending by 2026
Microsoft is accelerating its modernization of SharePoint and Microsoft 365 by retiring legacy technologies that were once central to classic SharePoint environments. Between 2025 and 2026, multiple long-standing features will reach end of support or be fully removed from Microsoft 365 and SharePoint Online.
The most significant retirements include:
-
InfoPath Forms Services and the InfoPath 2013 client (end July 14 2026), ending browser-based form support.
-
SharePoint Add-Ins and SharePoint 2013 workflows (April 2 2026), replaced by Power Automate and SharePoint Framework (SPFx).
-
SharePoint Alerts (classic “Alert Me”), Secure Store Service, and Power BI list integration, all phased out by late 2025–mid 2026.
-
On-premises products—SharePoint Server 2016/2019, Designer 2013, and Office Online Server—will also reach end of extended support by mid-to-late 2026.
These changes reflect Microsoft’s focus on modern, cloud-based, and low-code technologies: modern pages, Power Platform tools, and SPFx-based customizations.
The next few months mark a crucial transition period for organizations still relying on legacy SharePoint features. While many classic components will continue to function temporarily, Microsoft’s roadmap makes it clear that modernization is no longer optional — it’s essential for compatibility, security, and long-term sustainability.
To prepare:
-
Inventory all classic pages, InfoPath forms, workflows, and add-ins.
-
Prioritize migrations based on confirmed end dates (especially anything ending by mid-2026).
-
Adopt Power Apps, Power Automate, and SPFx for modern replacements.
-
Communicate and train users early, so change is smoother when retirements take effect.
By planning now, organizations can ensure a controlled, strategic modernization rather than a last-minute rush as these legacy services go dark in 2026.
Timeline (now → end of 2026)
2026-01 (rolling)
SharePoint Alerts (“Alert Me”)
What happens: Creation of new alerts turned off for all tenants.
Replacement: Use Power Automate / SharePoint rules / Teams notifications.
Reference: TECHCOMMUNITY.MICROSOFT.COM+1
2026-04-02
SharePoint 2013 Workflows (SharePoint Online)
What happens: Removed from existing tenants (already off for new tenants since 2024-04-02).
Replacement: Power Automate.
Reference: Microsoft Support+1
2026-06-30
SPFx Field Customizers (specific scenarios)
What happens: Microsoft signaled retirement by June 2026.
Replacement: Prefer Column JSON formatting / Power Apps.
Reference: voitanos.io
2026-07-14
InfoPath Forms Services (SharePoint Online)
What happens: Removed from SharePoint Online; InfoPath browser forms stop working.
Replacement: Power Apps / other modern form solutions.
Reference: TECHCOMMUNITY.MICROSOFT.COM
2026-07-14
InfoPath 2013 client
What happens: Product reaches end of extended support.
Reference: Microsoft Learn
2026-07-14
SharePoint Server 2016 (on-prem)
What happens: End of support (no updates/support).
Replacement: Migrate to SPSE / M365.
Reference: Microsoft Learn
2026-07-14
SharePoint Server 2019 (on-prem)
What happens: End of extended support (Mainstream ended 2024-01-09).
Replacement: Migrate to SPSE / M365.
Reference: Microsoft Learn
2026-07-14
SharePoint 2010 workflows (SP Server SE note)
What happens: SP2010 workflows no longer supported in SPSE after this date.
Replacement: 2013 workflows / Power Automate (per scenario).
Reference: Microsoft Learn
2026-07-14
SharePoint Designer 2013
What happens: End of extended support.
Replacement: Use Power Automate/Power Apps; Designer is legacy.
Reference: Microsoft Learn
2026-07 (Month)
SharePoint Alerts (classic)
What happens: Microsoft removes ability to use Alerts; existing alerts stop working.
Replacement: Power Automate / SharePoint rules.
Reference: Microsoft Support+1
No comments:
Post a Comment