How to stay ahead of deprecations and avoid surprises in your Microsoft 365 environment
SharePoint has come a long way from its early days as an on-premises document repository. Today, it’s a dynamic, cloud-first collaboration platform at the heart of Microsoft 365, supporting everything from intranets to automated workflows and AI-powered productivity tools like Copilot.
But progress comes with a price.
To keep the platform moving forward, Microsoft regularly retires legacy SharePoint features that no longer align with the needs of a modern digital workplace. Staying on top of these deprecations is essential – particularly for organisations still relying on older tools (which is often the case after migrating from on-premises environments or when using legacy site templates).
Failing to transition away from unsupported features in time can lead to unexpected disruptions, from broken business processes to security vulnerabilities and reduced productivity.
In this article, we’ll walk through what’s currently being retired, why it matters, and how to prepare effectively so you can minimise disruption and make the most of modern SharePoint.
What’s on the chopping block?
Microsoft is retiring several legacy SharePoint features over the coming months and years. While many of these have modern alternatives available, plenty of organisations have yet to make the transition.
Here’s a quick overview of what’s being retired, when, and the modern alternatives to plan for:
| Feature | Retirement Date | Why It’s Being Retired | Modern Alternative |
|---|---|---|---|
| SharePoint Alerts | July 2026 | Legacy notification method; overlaps with modern tools like Power Automate and Teams | Power Automate, SharePoint Rules, Teams notifications |
| SharePoint Add-ins (App Model) | April 2, 2026 | Security concerns, limited scalability, and incompatibility with modern SharePoint Online | SharePoint Framework (SPFx), Power Apps |
| SPFx Domain-Isolated Web Parts | April 2, 2026 | Security architecture improvements remove need for domain isolation | SPFx with updated security patterns, Microsoft Graph |
| InfoPath Forms | July 2026 | Deprecated, no longer receiving updates or security patches | Power Apps, Microsoft Forms |
| SharePoint Designer | 2026 (no official date confirmed) | No longer compatible with SharePoint Online; not supported in modern experiences | Power Automate, SharePoint site designs |
| SharePoint 2010 Workflows | Removed from SharePoint Online in 2020 | Unsupported, legacy automation with no future updates | Power Automate |
Some of these features are already deprecated or unsupported, while others are set to lose functionality completely by mid-2026. Either way, continued reliance on them increases the risk of disruption, making proactive planning essential.
SharePoint Alerts
- What they are:
- A legacy feature that sends email or SMS notifications when changes occur in lists, libraries, or documents.
- Why they’re going:
- Modern tools like Power Automate and Teams offer richer, more flexible notification options. Alerts also rely on outdated infrastructure.
- Retirement date:
- New tenants: blocked from July 2025
- All tenants: blocked from September 2025
- Fully retired: July 2026
- What to do:
- Review where Alerts are still active
- Replace with Power Automate flows or Teams notifications
- Support users through the transition
SharePoint Add-ins (App Model)
- What they are:
- Custom or third-party apps used to extend SharePoint functionality – often used in older deployments to tailor site behaviour.
- Why they’re going:
- The add-in model is outdated, less secure, and not designed for modern SharePoint Online. Microsoft is shifting to more integrated, scalable alternatives.
- Retirement date:
- April 2, 2026
- What to do:
- Identify any active add-ins in your environment
- Migrate functionality to the SharePoint Framework (SPFx), Power Apps, or Power Automate
- Plan time for redevelopment and user testing
SPFx Domain-Isolated Web Parts
- What they are:
- A specific type of SharePoint Framework (SPFx) component designed to run in isolated domains for added security.
- Why they’re going:
- Improvements in SPFx’s security model have made domain isolation unnecessary. Microsoft is simplifying deployment and reducing complexity.
- Retirement date:
- April 2, 2026
- What to do:
- Review any domain-isolated web parts in use
- Refactor to standard SPFx components using updated security patterns
- Leverage Microsoft Graph where appropriate
InfoPath Forms
- What they are:
- A legacy tool used to create custom forms in SharePoint for data entry, approvals, and workflow input – once widely adopted, especially in on-prem environments.
- Why they’re going:
- InfoPath has been deprecated for years and is no longer receiving updates or security patches. It doesn’t align with Microsoft’s modern cloud-first platform.
- Retirement date:
- July 2026
- What to do:
- Identify any active InfoPath forms, especially in older site collections
- Migrate to Power Apps for custom forms, or Microsoft Forms for simpler use cases
- Plan for form redesign, data migration, and user training
SharePoint Designer
- What it is:
- A legacy tool used to customise SharePoint sites and build workflows, commonly used before modern tools like Power Automate and site templates took over.
- Why it’s going:
- Designer is no longer compatible with SharePoint Online and hasn’t received updates in years. It doesn’t support modern experiences and poses security and stability risks.
- Retirement date:
- Expected in mid-2026 (exact date TBC)
- What to do:
- Phase out any workflows or customisations built in Designer
- Replace with Power Automate for workflows and modern SharePoint site designs for branding/customisation
- Review legacy sites for hidden dependencies
SharePoint 2010 Workflows
- What they are:
- Classic workflows used for automating approvals, routing, and business logic in earlier versions of SharePoint.
- Why they’re going:
- Removed from SharePoint Online in 2020 and no longer supported. Continuing to use them – especially in on-prem environments – introduces serious risks.
- Retirement date:
- Removed from SharePoint Online in 2020
- On-prem support expected to end post-July 2026
- What to do:
- Audit and document any 2010 workflows still in use
- Prioritise high-impact workflows for migration to Power Automate
- Involve business owners in testing redesigned processes
What does this mean for your organisation?
Feature retirements might sound technical, but the real impact is operational. If these changes go unaddressed, the consequences can be far-reaching – especially for organisations still running legacy sites or processes that haven’t been fully modernised.
Key risks to be aware of:
- Business disruption – Broken workflows, missing notifications, or inaccessible forms can interrupt daily operations
- Security vulnerabilities – Unsupported features often rely on outdated infrastructure that may expose sensitive data
- Compliance gaps – Retired tools may no longer meet regulatory requirements, putting data governance at risk
- User confusion – Sudden changes can create frustration and reduce productivity if alternatives aren’t in place
How to prepare:
- Identify what’s in use – Audit legacy features across your SharePoint environment
- Engage stakeholders – Understand who relies on what, and why
- Assess business impact – Prioritise critical dependencies and high-risk workflows
- Use Microsoft tools – Leverage SharePoint Admin Centre reports or Microsoft assessment tools to support discovery
- Document everything – Keep track of where, how, and why each legacy feature is being replaced or retired
Cloud Essentials’ recommendations
Microsoft’s retirement roadmap isn’t just a housekeeping exercise. It’s a chance to rethink your organisation’s Enterprise Content Management (ECM) strategy with a stronger emphasis on security, governance, and long-term value.
Here’s how we recommend approaching it:
Reframe this as a strategic ECM opportunity
Rather than replacing features like-for-like, step back and ask: What should our SharePoint and Microsoft 365 environment be doing for us?
This is the moment to modernise your content lifecycle, from creation and collaboration through to retention, protection, and disposal.
Align your governance and security from the ground up
Legacy features often operated in silos with inconsistent policies. Replacing them gives you the chance to build a more centralised, secure, and policy-driven environment, supported by tools like Microsoft Purview and Power Platform.
Use the right tools to work smarter
Modern solutions like Power Automate and Power Apps aren’t just newer, they’re more integrated, secure, and scalable. And when deployed strategically, they streamline processes and reduce risk.
Lean on expert guidance
At Cloud Essentials, we specialise in helping organisations:
- Take control of enterprise content with a governance-first approach
- Align ECM strategy with business goals and compliance obligations
- Migrate, redesign, and modernise legacy tools safely and efficiently
- Build strong foundations for productivity, automation, and secure collaboration
Whether you’re planning a targeted retirement or a broader transformation, now is the time to strengthen your content management foundations. With the right strategy and support, you can simplify governance, reduce risk, and unlock greater value from your Microsoft 365 investment.
Make the most of the moment
Retiring legacy SharePoint features might feel like just another item on the IT to-do list, but with the right mindset, it can be a meaningful step toward a more secure, efficient, and future-ready digital workplace.
The key is acting early. By identifying what’s at risk, engaging the right people, and taking a strategic approach to modernisation, you can avoid disruption and create space for better tools, stronger governance, and more streamlined collaboration.
Need help getting started, or just want to sanity check your roadmap? We’re here to support you with practical guidance, technical expertise, and a clear path forward.
Let’s modernise with purpose. Get in touch.